Federation lets consumers see one graph while teams build separate services. But the way teams practice Federation is backwards. Most teams start from the subgraph: write schema in code, push to the registry, then chase alignment in meetings, tickets, and Slack. The people who use the API come last. You get siloed ownership, unclear who owns what, and frontend developers blocked on questions they can’t answer. Schema registries help after you build. They don’t help you decide what to build, who builds it, or whether it meets the bar.Documentation Index
Fetch the complete documentation index at: https://hub-docs.wundergraph.com/llms.txt
Use this file to discover all available pages before exploring further.
Start from what consumers need and work down. Define the query. Hub checks the graph, finds the gaps, and sends the work to the right teams—with clear ownership and automated governance built in.
- Explore the full supergraph — Every type, every field, every subgraph, and who owns it.
- Design from what consumers need — Define the query you need; Hub shows what’s missing.
- Propose changes through clear steps — Checks, review by the right owners, and breaking-change checks before you build.
- Coordinate with a full record — Track every proposal, review, and decision.
Schema First
Design the API in Hub first, then sync to your codebase
Code First
Generate schemas from code and bring changes into Hub for governance
Quickstart
Get up and running in minutes
Guides
Step by step guides for working in Hub