Hive (Hive Console) is an MIT-licensed, open-source schema registry and analytics platform for GraphQL federation and other GraphQL APIs, built by The Guild for teams that publish, guard, and observe GraphQL schemas — either on the managed Hive Cloud or on their own infrastructure.

What it is

Hive Console is part of the Hive GraphQL platform. It is a schema registry and analytics service for GraphQL federation and for other GraphQL APIs, and it is written primarily in TypeScript, with Rust and Node.js also appearing in its topic list. The code lives in a pnpm/Turborepo monorepo that contains the web console, GraphQL services, the CLI, workers, migrations, and integration tests. The project's stated objectives are to help GraphQL developers understand their own APIs through schema registry, performance monitoring, alerts, and integrations; to support every kind of GraphQL API, from Federation and Stitching to standalone schemas; and to remain fully open-source and built in public with the community.

The concrete problem it solves is the gap between shipping a GraphQL schema and knowing what that change does to production traffic. Hive Console addresses this by running a set of checks on schema changes and notifying the team through Slack, GitHub, or the application itself, by defining "breaking change" in a data-driven way from Operations Monitoring rather than from a static rule set, and by keeping the full history of changes even on a complex composed schema. On the other side of the same problem, it answers how a deployed schema is actually used: error rates and distribution, latency, request volume, operation counts, and the population of active GraphQL clients.

Key capabilities

• Schema Registry checks that prevent breaking changes and notify the team via Slack, GitHub, or in-app, with "breaking change" defined from Operations Monitoring data.
• Full history of schema changes, including on composed schemas produced by Federation or Stitching.
• High-availability, multi-zone schema registry CDN service based on Cloudflare.
• Monitoring of error rates and distribution, global and per-operation performance with latency and request volume, operation counts, and active GraphQL clients.
• OpenTelemetry tracing that captures spans, HTTP and client metadata, operation status, and federation subgraph activity for diagnosing production requests.
• App Deployments for versioned persisted-document artifacts: publish, activate or retire deployments, and serve approved operations through the CDN.
• Integrations with Slack and GitHub, alerting through Slack, Microsoft Teams, or custom webhooks, plus organization OIDC and audit-log exports; the Hive CLI works with any CI/CD system, and the GitHub app adds status checks to pull requests.

Who uses it and how

• Federation and Stitching teams that need composition-aware checks and change history across subgraphs rather than on a single schema file.
• Teams gating schema changes in CI with the Hive CLI for publishing and checks, on any CI/CD system, with the GitHub app surfacing status checks directly on pull requests.
• Organizations that require centralized access management and governance, using organization OIDC and audit-log exports.
• Platform and on-call teams routing schema and metric alerts into Slack, Microsoft Teams, or custom webhooks alongside OpenTelemetry trace inspection.
• Client-facing API teams publishing versioned persisted documents as App Deployments and serving only approved operations through the CDN.

Getting started

Use managed Hive Cloud, or self-host with the community Docker Compose configuration documented in the self-hosting guide. Local development requires Node.js 24.18.0 or later, pnpm 10.33.2 or later, and Docker 26.1.1 or later, then runs pnpm install, pnpm local:setup, pnpm generate, and pnpm dev:hive.

How it compares

The provided facts name no competing tools and no paid products that Hive Console replaces, so no comparison against named alternatives can be made here. On the evidence available, it stands alone in this registry.

When to use it — and when not to

Self-hosting means operating the full stack yourself: the monorepo ships the web console, GraphQL services, workers, and migrations, and the community Docker Compose configuration is the documented entry point, so a team without the appetite to run and upgrade that infrastructure should take the managed Hive Cloud option instead. A developer or small team that only needs to publish a single schema with no interest in monitoring, alerts, or governance would be carrying a lot of machinery for little return. The repository also carries 260 open issues, which is worth weighing against the project's active development before committing to it as a critical dependency.

pnpm install
pnpm local:setup
pnpm generate
pnpm dev:hive