GraphQL Hive

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

GraphQL Hive is an open-source schema registry and observability platform for GraphQL APIs, distributed under the MIT licence, and a self-hostable alternative to hosted registries. It stores every version of your GraphQL schema, checks proposed changes for breaking changes before they ship, and composes federated or stitched schemas from many services into one supergraph. Teams publish schemas from CI with a small command-line client, gate merges on schema checks, and browse the full history, composition results and usage of every type and field through a web console. Because it also ingests usage data from your gateway, it can show which fields are actually queried, flag unused parts of the graph, and make breaking-change checks smarter by warning only when a change touches something clients really use.

This image delivers the whole GraphQL Hive stack pre-installed and pre-wired as its complete official Docker Compose stack, fronted by nginx, so the console, the registry and authentication server, and the schema, policy, token, workflow and usage services are all operational within minutes of launch, with no compose files to assemble by hand. Their datastores (PostgreSQL, ClickHouse, Redis, a Kafka-compatible broker and an object store) are set up and tuned alongside them.

Unlike a bare deployment, this image ships the stack hardened and secure by default. The upstream project ships example passwords and signing keys for its datastores and sessions, and cloudimg bakes none of them: on the first boot of every instance a fresh set of database, cache, object-store, encryption and session secrets is generated. Hive Community has no default login, so first boot also registers a single owner account with a unique, randomly generated password and writes it to a root-only file, meaning no two instances share a login and no upstream default ever governs a running console. The datastores stay bound to the instance on a private Docker network and are never exposed; only the web console (port 80) and the registry API (port 8082, used by the browser console and the hive CLI) reach the network. The registry data lives on a dedicated data volume captured into the image, the base is fully patched with unattended security upgrades enabled, and Docker and systemd manage the services for automatic restarts and clean logging.

Capabilities include a versioned schema registry with full history, breaking-change detection that gates schema changes in CI, a federation and stitching composition gateway, per-target registry and CDN access tokens, and usage analytics that reveal which parts of your graph clients actually query. 24/7 cloudimg support is included. GraphQL Hive and all other product and company names are trademarks or registered trademarks of their respective holders; use of them does not imply any affiliation with or endorsement by them.