Introduction to Hive

Hive is a schema registry for GraphQL. With Hive you manage and collaborate on all your GraphQL schemas and GraphQL workflows, regardless of the underlying strategy, engine or framework you’re using: this includes Schema Stitching, Apollo Federation, or just a traditional monolith approach.

Hive as a schema registry serves the main purpose of preventing breaking changes. This ensures that your GraphQL API stays up-to-date and running smoothly. This allows you to plan ahead and make the necessary modifications to your schema in a timely manner.

However, it is important to note that determining what constitutes a breaking change can be a complex task. It requires a thorough understanding of your GraphQL API, consumers and real-world traffic patterns. Hive provides a set of tools to help you with this task.

In addition to a basic schema registry functionality, Hive offers a set of tools to assist you in managing and collaborating on your GraphQL projects:

  • Observability for operation performance, end-user consumption, and operation success rate
  • Conditional Breaking Changes based on actual usage collected from your GraphQL gateway
  • Alerts and notifications
  • Schema diffing and validations
  • Schema history and versioning
  • Schema policies and best-practices validation

Hive and all of its components are developed and managed as an MIT open-source project.

You can use it in our Hive Cloud service or run it as a self-hosted solution: