Skip to content
SPECIFICTION
Get listed

Apicurio Registry

apicur.io

WebWindowsmacOSLinuxAPISelf-hosted
Visit apicur.io
Spec score 8.0 #11 of 26 in Schema Registry Software

What it is

Apicurio Registry is an open-source runtime server for storing API designs and schemas as artifacts. Users can add, update, and remove artifacts through a remote REST API. For API discovery, teams can register designs such as OpenAPI, AsyncAPI, and GraphQL so consumers can search and browse APIs, see details, and read generated documentation. For messaging and event streaming, it provides a central place to track schemas and manage data-format evolution. Supported artifact types include OpenAPI, AsyncAPI, GraphQL, Apache Avro, Protocol Buffers, JSON Schema, Kafka Connect schema, WSDL, XML Schema, and ODCS v3.1. Configurable rules can check validity, compatibility, and integrity as artifacts change. Listed storage backends include Apache Kafka, PostgreSQL, and Microsoft SQL Server. Management options include a web console, REST API, command line, Maven plug-in, and Java client. Kafka serializers and deserializers can enforce schemas in producer and consumer applications. The documentation covers self-hosted deployment, including Kubernetes. The quick-start in-memory server is non-persistent and is not intended for production.

Spec sheet

Purpose
Apicurio Registry is a runtime server that stores artifacts and lets users add, update, and remove them through a remote REST API.Read 5 Oct 2026 · apicur.io
Product
Apicurio Registry is a runtime server that stores API designs and schemas and lets users add, update, and remove artifacts through a REST API.Read 5 Oct 2026 · apicur.io
Deployment
The getting-started guide runs the server and UI as separate Docker images and also names Podman as a prerequisite option.Read 5 Oct 2026 · apicur.io
Integrations
The documentation describes Kafka client serializers and deserializers for Avro, Protobuf, and JSON Schema, and integration with Kafka Connect.Read 5 Oct 2026 · apicur.io
Support
The documentation directs users to the GitHub projects and issue tracker for help, suggestions, and problem reports.Read 5 Oct 2026 · apicur.io
API registry use
It can register API designs such as OpenAPI and AsyncAPI so consumers can browse and search APIs, view details, and read generated documentation.Read 5 Oct 2026 · apicur.io
Artifact formats
Supported artifact types include OpenAPI, AsyncAPI, GraphQL, Apache Avro, Protocol Buffers, JSON Schema, Kafka Connect schema, WSDL, and XSD.Read 5 Oct 2026 · apicur.io
Artifact types
Supported artifact types listed on the product page include OpenAPI, AsyncAPI, GraphQL, Avro, Protobuf, JSON Schema, Kafka Connect schema, WSDL, and XSD.Read 5 Oct 2026 · apicur.io
Authentication
Documented authentication options include OpenID Connect, HTTP basic, proxy header, and Kubernetes-native authentication; authentication and authorization options are disabled by default.Read 5 Oct 2026 · apicurio.io
Authorization
Authorization options include default admin, write, and read-only roles, plus content-based controls that can restrict artifact updates or deletion to its owner.Read 5 Oct 2026 · apicurio.io
CLI authentication
The CLI supports basic authentication and OAuth2 client credentials, and stores secrets in the operating system keychain or credential manager where available.Read 5 Oct 2026 · apicur.io
Client access
The documentation describes management through the web console, REST API, Maven plug-in, and Java client.Read 5 Oct 2026 · apicur.io
Command line
A native Apicurio Registry CLI is available for Linux x86_64, macOS Apple Silicon, and Windows x86_64, and is marked dev-preview and unstable.Read 5 Oct 2026 · apicur.io
Content rules
Configurable content rules can check validity, compatibility, and integrity as artifacts evolve.Read 5 Oct 2026 · apicur.io
Kafka integration
The documentation describes Kafka client serializers and deserializers for enforcing schemas in producer and consumer applications.Read 5 Oct 2026 · apicur.io
Management interfaces
The documentation lists a web console, REST API, command line, Maven plug-in, and language SDKs for content management.Read 5 Oct 2026 · apicur.io
Non-persistent mode
The quick-start in-memory server is non-persistent and the guide says not to use it for production.Read 5 Oct 2026 · apicur.io
Roles
When role-based authorization is enabled, the CLI supports ADMIN, DEVELOPER, and READ_ONLY role mappings.Read 5 Oct 2026 · apicur.io
Schema registry use
For messaging and event streaming, it provides a central place to track schemas and manage data format and schema evolution.Read 5 Oct 2026 · apicur.io
Storage
The product page lists Apache Kafka, PostgreSQL, and Microsoft SQL Server as backend storage options.Read 5 Oct 2026 · apicur.io
Storage backends
The product page lists Apache Kafka, PostgreSQL, and Microsoft SQL Server as configurable backend storage options.Read 5 Oct 2026 · apicur.io
Use cases
It supports API discovery and documentation, as well as centralized storage and evolution control for schemas used in messaging and event streaming.Read 5 Oct 2026 · apicur.io
Version status
The product page lists version 3.3.3 and says the 2.x line is deprecated.Read 5 Oct 2026 · apicur.io

Strong points and limits

Strong points

  • Supports API discovery and schema management.
  • Includes configurable validity and compatibility rules.
  • Offers several listed storage backends.
  • Documents web, API, CLI, and client access.
  • Open source and self-hostable.

Limits

  • Quick-start in-memory mode is non-persistent.
  • The in-memory guide says not to use it for production.
  • Authentication and authorization are disabled by default.

Who it suits

Apicurio Registry suits teams managing API designs or schemas for messaging and event streaming. It is relevant to teams that want self-hosted deployment, configurable storage, and Kafka client integration.

Verdict

Apicurio Registry covers both API cataloging and schema evolution, with multiple artifact types, interfaces, and storage options. Configure persistence and security for the intended deployment rather than relying on the in-memory quick start.

Where Specifiction places it

Alternatives to Apicurio RegistryAll alternatives →