Start with a requirement
Every schema change starts with a consumer needing data that does not exist. Capture the requirement on the canvas so everyone sees what is expected.

WunderGraph Hub
Product, frontend, and backend aligned on your supergraph — in real time. No more API sprawl. No more schema chaos.
“Ownership, checks, and cross-team negotiations have become one of our biggest velocity bottlenecks. Having a single dashboard, clearly traceable from beginning to end, is gonna be amazing.”
Alexander Bandarchuk
Sr. Director Architect, eBay
Start with the requirement. Design the API your product needs.
Hub handles composition for you.
Traditional
With Hub
Hub enables you to focus on evolving your graph to meet the needs of your organization.
Hub automates the complexities of Federation while ensuring everything remains fully composable.
Why Hub exists
Enable backend teams to ship what the frontend engineers need. Establish a single source of truth and say goodbye to meetings and endless rework.
Immediately understand who owns which part of the schema. Automatically involve the right people to ship with confidence.
Catch potentially breaking changes in time and never break a client again. Deployments become predictable and safe, no matter how complex the graph.
Stay on top of your supergraph as microservices and subgraphs multiply. Hub makes it easy to get a clear picture of your graph regardless of complexity.
One platform
Built for enterprises running GraphQL federation with many teams.
Align frontend, backend, and product on one visual canvas. No more contracts built in the dark. Hub turns UI mocks and dream queries into a shared schema so everyone works from the same source of truth.
Validate changes against real traffic. Enforce deprecation with grace periods. Catch regressions before they merge. Deploy with confidence.
Proposals, required reviewers, and discussions on the schema. Governance is built in, not bolted on. Hub adds the right owners as reviewers automatically.
Explore, own, and organize your GraphQL ecosystem in one place. See who owns what. Tame sprawl as you scale without latency creep.
How it works
Start from a UI requirement, design the query your consumer needs, propose the schema change, and ship it.
Every schema change starts with a consumer needing data that does not exist. Capture the requirement on the canvas so everyone sees what is expected.

Model the missing fields directly in Hub. The proposal becomes the single source of truth for what will change.

Comments live in the workflow, not in Slack. The right owners are pulled in automatically.

Type and field owners sign off inside the workflow. No separate review meetings.

Approved proposals sync to your schema registry. Implementation teams ship against an agreed contract.

Collaboration built-in
Product, frontend, and backend work on one canvas. Proposals and reviews keep the graph safe without slowing anyone down.

Go deeper into the solutions Hub provides for federated teams.
Automate graph protection, ownership, and deprecations.
Read moreOptimize query plans and latency before production.
Read moreTraffic-aware validation and safe deprecation.
Read moreOne visual workspace for your entire graph.
Read moreJoin teams already using Hub to design, govern, and ship their federated APIs. Start free—no credit card required.