Quick Start

Local Development (No Cloud Required)

1. Push a GraphQL subgraph

hyperroute push --local \
  --name products \
  --schema ./products/schema.graphql \
  --url http://localhost:4001/graphql

2. Push a REST subgraph

hyperroute push --local \
  --name users \
  --schema ./users/schema.graphql \
  --url http://localhost:4002 \
  --subgraph-type rest

3. Push a gRPC subgraph

hyperroute push --local \
  --name inventory \
  --schema ./inventory/schema.graphql \
  --url grpc://localhost:50051 \
  --subgraph-type grpc \
  --grpc-service inventory.v1.ProductService

4. Query through the router

curl -X POST http://localhost:4000/graphql \
  -H "Content-Type: application/json" \
  -d '{"query": "{ user(id: \"1\") { name email } }"}'

All three backends are now federated behind a single GraphQL endpoint. The router automatically routes each field to the correct backend using the appropriate protocol.

---

Production Deployment

# Push with governance (auto-detects breaking changes)
hyperroute push --env production \
  --name products \
  --schema dist/schema.graphql \
  --url http://products:4001/graphql

In production mode, DevKit connects to the Platform API for governance. Breaking changes create a proposal that requires human approval before deployment proceeds.

---

Next Steps

• Core Concepts — Understand bundles, snapshots, and environments
• Routing Directives — How @rest and @grpc work
• Push & Governance — Deep dive into the push workflow