Deploy GraphQL Hive Console
Self-hosted GraphQL Hive: schema registry + usage analytics. Zero inputs.
Just deployed
Just deployed
/var/lib/clickhouse
Just deployed
migrations
Just deployed
workflows
Just deployed
Just deployed
Just deployed
/bitnami/redis/data
usage-ingestor
Just deployed
Just deployed
/var/lib/postgresql/data
Just deployed
Just deployed
/var/lib/redpanda/data
Just deployed
/srv
Just deployed
/keys
Just deployed
Deploy and Host GraphQL Hive Console on Railway
After your first sign-up, set
DISABLE_SIGNUP=1on theedgeservice and redeploy it. Hive has no sign-up switch and no instance owner: anyone who can open the console can register and create an organization (graphql-hive/console#8039). The switch returns 403 for email+password registration; sign-in, password reset and social/OIDC login are unaffected. Details: https://github.com/kolebjak/railway-hive#closing-sign-up
GraphQL Hive Console is the open-source schema registry for GraphQL: it stores every published schema, runs breaking-change checks in CI, composes federated supergraphs, serves them to gateways over a CDN endpoint, and shows field-level usage analytics collected from your gateway or server. This template is the self-hosted console pinned to hive@14.1.0.
About Hosting GraphQL Hive Console
Hive Console is thirteen containers: the web app, the GraphQL API server, the schema and policy services, the workflows worker, the usage endpoint and its ingestor, a one-shot migrations job, PostgreSQL, ClickHouse, Redis, a Redpanda (Kafka API) broker and an S3-compatible store. This template maps them one-to-one onto Railway services wired over the private network, generates every secret with Railway template functions, attaches volumes to Postgres, ClickHouse, Redis, Redpanda, S3 and the server key store, and adds one Caddy service, edge, that owns the single public domain: the console at /, the GraphQL API at /graphql, CDN artifacts at /artifacts/v1/... and usage reporting at /usage. One origin means login works on the generated Railway domain, no custom domain needed. Nothing is required at deploy time.
Common Use Cases
- Schema registry with breaking-change checks in CI for a single GraphQL API
- Federation supergraph composition served to Hive Gateway, Hive Router or Apollo Router
- Field-level usage analytics to find unused fields before removing them
Dependencies for GraphQL Hive Console Hosting
- PostgreSQL 16, ClickHouse 26, Redis 7, Redpanda v23, versitygw (S3) and Caddy are all included in the template
- A gateway or SDK in your own project that reports usage and pulls the supergraph from the edge domain
- Optional: SMTP or Postmark credentials on the workflows service to send invite and alert emails
- Optional: a custom domain on
edge
Implementation Details
After deploy: open the edge domain, sign up, set DISABLE_SIGNUP=1 on edge, create an organization, a project and a target. Create a registry token (schema:publish + usage:report) and a CDN token. Configure your gateway with the CDN URL https://EDGE_DOMAIN/artifacts/v1/TARGET_ID, the CDN key, the registry token and the usage endpoint https://EDGE_DOMAIN/usage. Source, local compose check and upgrade notes: https://github.com/kolebjak/railway-hive
Why Deploy GraphQL Hive Console on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying GraphQL Hive Console on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
migrations
ghcr.io/graphql-hive/storage:14.1.0usage-ingestor
ghcr.io/graphql-hive/usage-ingestor:14.1.0
