WunderGraph

Tesler's Law of Conservation of Complexity: every application has an inherent amount of irreducible complexity. The question is who will have to deal with it. Not if. Who? wundergraph.com/blog/rest-vs-g…

Tesler's Law of Conservation of Complexity: every application has an inherent amount of irreducible complexity. The question is who will have to deal with it. Not if. Who? wundergraph.com/blog/rest-vs-g…

MCP with one broad OAuth scope breaks least privilege. Scopes should be enforced per tool, derived from the schema, not flattened at the server. wundergraph.com/blog/mcp-per-t…

Federation composes subgraphs into a supergraph. Fission flips it. You design the supergraph first, assign fields to subgraphs, and the system derives the required schemas and dependencies. Learn more: wundergraph.com/blog/fission-a…

Agents don’t integrate APIs like humans. They can’t read docs or SDKs. They have to discover capabilities. This post touches on why we believe GraphQL is the layer Agents need. wundergraph.com/blog/graphql-a…

Excited to announce that WunderGraph is partnering with Creators Corner for their upcoming Hackathon in San Francisco on April 23rd! 🚀 Register now! luma.com/shiptoprod

We’re collecting info on how teams adopt, operate, and scale federation in production. It takes 5–10 minutes to complete, you get early access to the full report, and we’ll donate $30 to UNICEF for every valid response. The goal is to build a clear, vendor-neutral view of what’s working, what’s breaking, and how AI is changing the shape of these systems. Take the survey: 8bxwlo3ot55.typeform.com/to/zIJKRQUe

Their graph composed fine, but days of implementation work stretched into weeks, because ownership was unclear and coordination required multiple meetings Read about how Hub changed their approach. wundergraph.com/blog/graphql-f…

Federation's core operation is composition: take many subgraph schemas, merge them into one supergraph. Many to one Fission does the inverse: take one supergraph design, decompose it into subgraph responsibilities. One to many wundergraph.com/blog/fission-a…

Agents need to discover capabilities, navigate structure, and execute within tight context limits. Our argument: GraphQL’s typed, navigable schema and a federated supergraph match that model. wundergraph.com/blog/graphql-a…

Cosmo Router Cost Control estimates query cost at planning time and can block expensive requests before execution. Measuring Mode records estimated cost without rejecting. Enforcing Mode rejects over-limit queries before execution. wundergraph.com/blog/cost-cont…

GraphQL Federation doesn’t remove coupling. It makes it explicit. @requires won’t fix temporal dependency, the router still needs upstream services. But instead of hidden HTTP calls, dependencies live in the schema, visible in query plans and validated at build time. wundergraph.com/blog/microserv…

WunderGraph Hub from the CTO's POV (Live Discussion) x.com/i/broadcasts/1…

Hub is the missing coordination layer for GraphQL Federation, built for high-velocity teams scaling in the age of AI.

Building Hub with our Customers (Live Discussion) x.com/i/broadcasts/1…

Welcome to WunderGraph Hub (Live Discussion) x.com/i/broadcasts/1…

Automation can improve efficiency, but it can’t replace empathy. In our latest post, Viola shares why true customer success starts with human curiosity, not scripts. Read more: wundergraph.com/blog/customer-…

Why WunderGraph is ALL IN on Federation x.com/i/broadcasts/1…

New on the WunderGraph blog: Vincent Vermersch on combining CQRS, GraphQL Federation, and Event-Driven Subscriptions for a smoother developer experience. Read it here 👉 wundergraph.com/blog/vincent-v…

Most teams think Federation has two versions — V1 and V2. But there’s a hidden layer in between: V1.5. V1.5 subgraphs compose under V2 routers but fail under strict V1 rules. They combine V2’s flexibility with V1’s constraints, often causing confusion during migrations or compatibility checks. Read more on our blog: wundergraph.com/blog/understan…