DevKit Overview
HyperRoute DevKit is a production-grade CLI for GraphQL federation management. It composes, validates, packages, and deploys supergraph bundles to HyperRoute routers.
Key Capabilities
- Multi-protocol federation — Compose GraphQL, REST, and gRPC backends into a single supergraph
- Schema governance — Approval-gated deployments with breaking change detection
- Immutable bundles — Content-addressed artifacts with deterministic snapshot IDs (UUIDv5)
- CI/CD native — Exit codes, JSON output, and concurrency-safe registry locking
- Local development — Full offline workflow with hot-reload to local router
Design Principles
| Principle | Description |
|---|---|
| Immutability | All artifacts are content-addressed and append-only |
| Deterministic IDs | Same schema content → same snapshot_id |
| DevKit composes, Router executes | Routerd never composes or reads registries |
| Registry is source of truth | DevKit reads/writes; routerd only receives bundles |
| Concurrency safe | Registry-backed locking prevents race conditions |
How It Fits Together
Developer / CI Pipeline
│
├─▶ hyperroute push (compose + validate + deploy)
├─▶ hyperroute compose (composition only)
├─▶ hyperroute deploy (deploy existing bundle)
└─▶ hyperroute approve (governance workflow)
│
┌────────┼────────────┐
▼ ▼ ▼
Registry Platform Router
(S3/R2) (Governance) (Routerd)
DevKit is the control plane CLI — it owns composition, validation, and deployment. The router never composes schemas or reads from registries directly. This separation ensures that your deployment artifacts are always immutable and auditable.
Next Steps
- Install DevKit — Get up and running in 30 seconds
- Quick Start — Push your first subgraph in 5 minutes
- Core Concepts — Understand bundles, snapshots, and environments