Hive Router
Compatibility
This page describes which Federation features are supported by Hive Router, along with the current implementation status of each.
Hive Router targets the Federation v2 specification. Federation features are shipped over time as part of the Federation specification versions, so each feature below is mapped to the version that introduced it.
Federation v1
Hive Router supports Federation v2 only. Federation v1 supergraphs are not supported - compose your subgraphs with Federation v2 composition tools, or a schema registry, before running them through the router.
Status Legend
| Icon | Meaning |
|---|---|
| ✅ | Fully supported |
| ⏳ | Planned / In progress |
Feature Support
| Feature | Status | Notes | Federation Version |
|---|---|---|---|
Federation v2 base (@key, @external, @requires, @provides, @shareable foundations) | ✅ | Base specification supported by Hive Router | v2.0 |
Custom directives (@composeDirective) | ✅ | Fully supported | v2.1 |
@shareable | ✅ | Fully supported | v2.2 |
@interfaceObject | ✅ | Fully supported | v2.3 |
| Subscriptions | ✅ | Fully supported. See Subscriptions. | v2.4 |
Authentication directives (@authenticated, @requiresScopes, JWT) | ✅ | Fully supported. See JWT Authentication. | v2.5 |
Authorization (@policy) | ⏳ | Planned | v2.6 |
Progressive @override | ✅ | Fully supported | v2.7 |
Contextual arguments (@context / @fromContext) | ⏳ | Planned | v2.8 |
Demand control (@cost / @listSize) | ⏳ | Planned | v2.9 |
| Apollo Connectors (REST connectors) | ⏳ | Not supported at the moment | v2.10, v2.10, v2.11, v2.13 |
Response caching (@cacheTag) | ⏳ | Not supported yet | v2.12 |
We continuously run the Federation Gateway Audit to verify Hive Router's compliance with the federation ecosystem, including every day use-case and edge-cases that our users encounter.