Moves
- the gateway
- the schema registry
- CI checks
- observability wiring
GraphQL federation
Open GraphQL federation, built around your graph.
Open source, running in your cloud, built on GraphQL Hive by The Guild. The same schema, the same checks and the same audit trail for humans, apps and agents.
Talk to an engineerThe scope
What moves, and what doesn't.
Stays
- your subgraphs
- your resolvers
- your clients
- your queries
- your auth provider
The starting point
Registry-first or gateway-first.
| Stage | What moves |
|---|---|
| Registry first | Registry first when your pain is schema governance, breaking changes, or contract sprawl - lowest risk, no traffic moves. |
| Gateway first | Gateway first when your pain is cost, performance, or self-hosting - bigger win, needs a traffic plan. |
Most teams go registry first.
Rollback and risk
Rollback and risk.
Every stage is reversible. Traffic shifts behind your own flags. Both gateways can run in parallel during cutover.
Team certification
Team certification.
Weeks 11–12: your engineers run a migration step themselves with ours watching. You leave able to operate it.
| Weeks | Stage | What moves |
|---|---|---|
| 1–2 | Graph audit | Inventory of subgraphs, consumers, breaking-change risk, agent surface. Nothing changes in production. |
| 3–4 | Registry and checks | Hive schema registry live, checks wired into CI. Still no traffic moved. |
| 5–10 | Gateway migration | Subgraph by subgraph, behind your flags, with rollback at every step. |
| 11–12 | Agents and handover | MCP skills declared and governed. Your team certified to run it without us. |
Scope and exit criteria
Scope and exit criteria.
Scope agreed before anything moves, with published exit criteria. Commercial terms are direct with The Guild.
Federation FAQ
Can we adopt Hive incrementally, or is it a big bang?
Incrementally. The registry and the gateway are separable concerns, so most teams move one first and run both side by side. Subgraphs themselves generally need no rewrite - they are spec-compliant either way.
Do we have to rewrite our subgraphs?
In the normal case, no. The work sits at the gateway and registry layer.
Bring us your graph.
One call, an engineer on it, and a straight answer about whether this is worth doing for you.