HyperRoute is a high-performance GraphQL federation platform consisting of three components: Core (a Rust-based router built for maximum throughput), DevKit (CLI for safe schema deployments), and Platform (enterprise control plane with dashboards and approval workflows).

How fast is HyperRoute compared to other GraphQL routers?

HyperRoute Core is built from scratch in Rust for maximum performance — no garbage collection pauses, minimal memory footprint, and ultra-low latency. It is designed to significantly outperform JVM and Node.js-based GraphQL routers.

Does HyperRoute support Apollo Federation?

Yes, HyperRoute fully supports Apollo Federation v2 directives including @key, @shareable, @override, entity batching, and cross-subgraph references. You can migrate from Apollo Router without changing your subgraphs.

What security features does HyperRoute include?

HyperRoute includes comprehensive security at no extra cost: query validation (depth, complexity, alias limits), injection detection (SQL, NoSQL, command injection), DDoS protection, adaptive rate limiting with IP reputation scoring, and cryptographic audit trails.

What storage backends does HyperRoute support for schema registry?

HyperRoute supports bring-your-own-storage including AWS S3, Cloudflare R2, Google Cloud Storage, Azure Blob Storage, MinIO, and any S3-compatible API. There is no vendor lock-in.

Yes, HyperRoute Core and DevKit are completely free to use. The Platform requires a commercial license — contact sales@hyperroute.dev for pricing and trial access.

CLI Reference

Global Options

These flags are available on every command:

Flag	Description
`-v, --verbose`	Enable verbose output. Shows internal steps, API calls, and timing
`--format <FORMAT>`	Output format: `human` (default) or `json`. Use `json` for CI/CD pipelines
`-h, --help`	Print help for the command
`-V, --version`	Print the DevKit version

Command Overview

Category	Commands	Description
Schema Management	`push`, `compose`, `diff`, `subgraph`	Push, compose, compare, and manage schemas
Bundle Lifecycle	`pack`, `bundle`, `validate`, `deploy`, `activate`, `rollback`	Create, validate, deploy, and manage bundles
Governance	`approve`, `governance`, `policy`, `contract`	Approval workflows, policy checks, contract testing
Registry	`publish`, `registry`, `snapshot`, `promote`	Manage schema registries and promotions
Observability	`observe`, `explain`, `visualize`, `replay`	Monitoring, tracing, query visualization
Operations	`release`, `audit`, `retention`, `verify`, `sign`	Release management, audit logs, retention policies
Development	`init`, `doctor`, `compat`, `version`, `migrate-to-directives`	Setup, diagnostics, compatibility, migration
Planning	`planner`	Query cost analysis, regression testing

`hyperroute init`

Initialize a new devkit.yaml configuration file in the current directory.

hyperroute init

`hyperroute compose`

Compose a supergraph from subgraph schemas defined in devkit.yaml or the local registry.

hyperroute compose --env <ENV> [OPTIONS]

Flag	Description
`-e, --env <ENV>`	Required. Environment to compose for
`-s, --schema <SCHEMAS>`	Subgraph schema files. Format: `name=path` or `name=path@url`
`-c, --config <PATH>`	Path to `devkit.yaml`
`-o, --out <PATH>`	Output directory for the composed bundle
`--from-registry`	Read subgraph schemas from the local registry
`--visualize`	Print a visual representation of the composition result
`--diff <PATH>`	Compare against a previous bundle directory
`--base <PATH_OR_URL>`	Base bundle for version lineage tracking
`--wait`	Wait for registry lock instead of failing
`--max-wait-seconds <N>`	Maximum lock wait time (default: 300s)
`--lock-ttl <N>`	Lock time-to-live (default: 600s)
`--no-lock`	Skip locking entirely (use with caution)

# Compose from devkit.yaml
hyperroute compose --env dev

# Compose specific schemas
hyperroute compose --env dev \
  -s users=./users/schema.graphql \
  -s products=./products/schema.graphql@http://products:4001/graphql

# Compose from registry with diff
hyperroute compose --env staging --from-registry --diff ./previous-bundle

`hyperroute doctor`

Run diagnostic checks on the local environment, router connectivity, and bundle integrity.

hyperroute doctor [OPTIONS]

Flag	Description
`--bundle <PATH>`	Path to a bundle directory to validate
`--routerd <PATH>`	Path to the routerd binary to check
`--url <URL>`	URL of a running router to health-check
`--skip-upstream`	Skip upstream connectivity checks

`hyperroute deploy`

Deploy a bundle to a running router.

hyperroute deploy --url <ROUTER_URL> [OPTIONS]

Flag	Description
`--url <URL>`	Required. Router URL
`-b, --bundle <PATH>`	Bundle directory or `.tar.gz` archive
`--bundle-id <ID>`	Bundle ID to fetch from registry
`--snapshot-id <ID>`	Snapshot ID to compose and deploy
`-e, --env <ENV>`	Deploy latest bundle for environment
`--dry-run`	Validate without deploying
`--wait-healthy`	Poll router health after deploying
`--timeout <SECS>`	Health check timeout (default: 30s)
`--auto-rollback`	Auto-rollback if activation fails

# Deploy from a local bundle directory
hyperroute deploy --url http://localhost:4000 --bundle .hyperroute

# Deploy a specific bundle from the registry
hyperroute deploy --url http://router:4000 --bundle-id bundle-abc123 -c devkit.yaml

# Deploy latest for an environment
hyperroute deploy --url http://router:4000 --env production -c devkit.yaml

`hyperroute activate`

Activate a specific bundle on a running router (assumes bundle is already uploaded).

hyperroute activate --bundle-id <ID> --router-url <URL>

Flag	Description
`-b, --bundle-id <ID>`	Required. Bundle ID to activate
`--router-url <URL>`	Required. Router URL
`--wait-healthy`	Wait for router to report healthy
`--timeout <SECS>`	Health check timeout (default: 30s)

`hyperroute rollback`

Rollback to the previous bundle on a running router.

hyperroute rollback --router-url <URL>

Flag	Description
`--router-url <URL>`	Required. Router URL
`--wait-healthy`	Wait for router to report healthy
`--timeout <SECS>`	Health check timeout (default: 30s)

`hyperroute validate`

Validate a bundle directory for correctness.

hyperroute validate [PATH]

Flag	Description
`[PATH]`	Path to the bundle directory (default: `.hyperroute`)
`--previous <PATH>`	Previous bundle for breaking change detection

`hyperroute pack`

Pack a bundle directory into a compressed .tar.gz archive.

hyperroute pack --source <PATH> [OPTIONS]

Flag	Description
`-s, --source <PATH>`	Required. Path to the bundle directory
`-o, --output <PATH>`	Output path for the archive
`--validate`	Validate before packing
`--checksums`	Generate a checksums file

`hyperroute publish`

Publish a bundle to the artifact registry (S3, R2, GCS, or Azure Blob).

hyperroute publish [OPTIONS]

Flag	Description
`-b, --bundle <PATH>`	Bundle directory or `.tar.gz` archive
`-e, --env <ENV>`	Target environment
`-t, --tenant <TENANT>`	Tenant name
`--version <VERSION>`	Version string (auto-generated if not specified)
`--reload-router`	Trigger router reload after publishing
`--dry-run`	Validate without publishing

`hyperroute promote`

Promote a bundle from one environment to another.

hyperroute promote --from <ENV> --to <ENV> [OPTIONS]

Flag	Description
`--from <ENV>`	Required. Source environment
`--to <ENV>`	Required. Target environment
`--source <PATH>`	Source bundle directory
`--target <PATH>`	Target bundle directory
`--promoted-by <ID>`	Identity for audit trail

`hyperroute diff`

Compare schemas, bundles, or compose reports.

hyperroute diff bundles <PATH_A> <PATH_B>   # Compare two bundles
hyperroute diff reports <PATH_A> <PATH_B>   # Compare two compose reports
hyperroute diff current --env <ENV>          # Compare against current environment
hyperroute diff schema <FILE_A> <FILE_B>    # Compare two GraphQL SDL files

`hyperroute subgraph`

Manage subgraph schemas in the registry.

Subcommand	Description
`subgraph add`	Add a new subgraph to the registry
`subgraph update`	Update an existing subgraph's URL or configuration
`subgraph list`	List all subgraphs in an environment
`subgraph remove`	Remove a subgraph (requires confirmation)
`subgraph publish`	Publish a subgraph schema to the registry
`subgraph check`	Check a schema for breaking changes before pushing
`subgraph show`	Show subgraph details and version history

`hyperroute approve`

Manage the schema approval workflow.

Subcommand	Description
`approve request`	Create a new approval request from a schema diff
`approve status`	Check the status of an approval request
`approve approve`	Approve a pending request
`approve reject`	Reject a pending request
`approve emergency`	Emergency approve with bypass (audit-logged)
`approve list`	List all pending approval requests
`approve analyze`	Analyze a schema diff

`hyperroute governance`

Governance tooling for policy authoring and enforcement.

Subcommand	Description
`governance init`	Initialize governance configuration
`governance dry-run`	Run a dry-run enforcement check
`governance report`	Generate a governance report
`governance diff`	Compare two governance configurations
`governance validate`	Validate governance configuration
`governance list`	List all policies
`governance rollback`	Rollback to a previous governance version

`hyperroute sign` / `hyperroute verify`

Sign and verify bundles for integrity and provenance.

# Sign a bundle
hyperroute sign --bundle .hyperroute --backend builtin --private-key key.pem

# Verify a bundle
hyperroute verify --bundle .hyperroute --key public-key.pem

Sign Flag	Description
`-b, --bundle <PATH>`	Required. Bundle directory
`--backend <TYPE>`	`builtin` (SHA256), `minisign`, or `cosign` (sigstore)
`--private-key <PATH>`	Private key file

Verify Flag	Description
`-b, --bundle <PATH>`	Required. Bundle directory or `.tar.gz`
`-k, --key <PATH>`	Public key file
`--key-hex <HEX>`	Public key as hex string
`--skip-checksums`	Only verify signature, skip checksum verification

`hyperroute migrate-to-directives`

Migrate from legacy mappings.json to schema-embedded @rest and @grpc directives.

hyperroute migrate-to-directives [BUNDLE_PATH] [OPTIONS]

Flag	Description
`[BUNDLE_PATH]`	Bundle directory containing `mappings.json` (default: `.`)
`--dry-run`	Preview changes without applying
`--output <PATH>`	Write migrated schema to a different file
`--backup`	Backup original files before migration

Other Commands

Command	Description
`hyperroute compat`	Check compatibility between DevKit, routerd, and bundle versions
`hyperroute snapshot`	Manage immutable subgraph version sets (`create`, `list`, `show`, `compose`, `versions`)
`hyperroute bundle`	Low-level bundle management (`upload`, `download`, `list`, `show`, `deploy`, `rollback`, `promote`)
`hyperroute audit`	View and verify the append-only audit log (`list`, `show`, `verify`)
`hyperroute retention`	Manage artifact retention policies (`show`, `evaluate`, `apply`, `init`)
`hyperroute registry`	Test registry connectivity, list bundles, show config (`test`, `ls`, `config`)
`hyperroute observe`	Observability tooling (`doctor`, `generate`, `dashboards`)
`hyperroute explain`	Explain query routing (`execution`, `plan`, `query`)
`hyperroute visualize`	Generate visual execution graphs (`execution-graph`)
`hyperroute planner`	Query plan analysis (`cost`, `regression`, `mapping`, `explorer`)
`hyperroute replay`	Replay execution traces (`list`, `show`, `export`, `timeline`, `import`)
`hyperroute release`	Release operations (`provenance`, `workflow`, `compliance`, `chain`, `verify`)
`hyperroute policy`	Policy operations (`lint`, `diff`, `explain`)
`hyperroute contract`	Contract stability (`diff`, `validate`, `gate`, `show`)

CLI Reference

Global Options

Command Overview

hyperroute init

hyperroute compose

hyperroute doctor

hyperroute deploy

hyperroute activate

hyperroute rollback

hyperroute validate

hyperroute pack

hyperroute publish

hyperroute promote

hyperroute diff

hyperroute subgraph

hyperroute approve

hyperroute governance

hyperroute sign / hyperroute verify

hyperroute migrate-to-directives