Apicurio Registry

Free plan APILinuxMacSelf-hostedWebWindows

What Apicurio Registry is

Apicurio Registry is an open-source runtime server for storing API designs and data schemas as artifacts. Users can add, update, and remove artifacts through a REST API. For API discovery, teams can register designs such as OpenAPI and AsyncAPI; consumers can then browse and search APIs, view details, and read generated documentation. For messaging and event streaming, the registry gives teams a central place to track schemas and manage changes to data formats over time.

Its supported formats include OpenAPI, AsyncAPI, GraphQL, Apache Avro, Google Protobuf, JSON Schema, Kafka Connect schema, WSDL, XML Schema, and ODCS v3.1. Configurable content rules can check artifact validity, compatibility, and integrity as content evolves. The listed storage backends are Apache Kafka, PostgreSQL, and Microsoft SQL Server. Management interfaces include a web console, REST API, command line, Maven plug-in, and client libraries; the documentation also describes a Java client. Kafka serializers and deserializers can enforce schemas in producer and consumer applications, and Kafka Connect integration is documented. Apicurio Registry supports self-hosting, with deployment guidance for Kubernetes. The product page lists version 3.3.3 and marks the 2.x line deprecated.

Who it suits

Apicurio Registry suits teams that need a shared catalog for API definitions or schemas used in messaging and event streaming. It may also fit teams that want to manage artifact changes through configurable rules and connect schema handling to Kafka applications.

What it does well

Stores API designs and schemas through a REST API.
Supports API discovery for OpenAPI and AsyncAPI.
Covers multiple schema and contract formats.
Content rules can check validity, compatibility, and integrity.
Offers Kafka serializers, deserializers, and Kafka Connect integration.
Can be self-hosted, including with Kubernetes deployment guidance.

What to know first

Authentication and authorization options are disabled by default.
The quick-start in-memory server is non-persistent and not for production.
The native CLI is marked dev-preview and unstable.

Getting started

Visit the Apicurio Registry website.
Choose a deployment approach; self-hosted deployment is supported.
For Kubernetes deployment, follow the operator guidance.
Select a listed storage backend: Apache Kafka, PostgreSQL, or Microsoft SQL Server.
Manage artifacts through the web console, REST API, Maven plug-in, Java client, or command line.

Verdict

Choose Apicurio Registry if you need an open-source registry for API designs and evolving data schemas, with Kafka integration and configurable storage. Teams should account for enabling authentication and authorization where needed, and should not use the in-memory quick-start server for production.

Questions

Is Apicurio Registry free?

Yes. It is listed as free and open source.

Can it be self-hosted?

Yes. Self-hosted deployment is supported, and the documentation covers Kubernetes deployment with an operator.

Which formats does it support?

Listed formats include OpenAPI, AsyncAPI, GraphQL, Apache Avro, Google Protobuf, JSON Schema, Kafka Connect schema, WSDL, XML Schema, and ODCS v3.1.

Does it integrate with Kafka?

The documentation describes Kafka client serializers and deserializers for Avro, Protobuf, and JSON Schema, as well as Kafka Connect integration.

Which storage backends are available?

The listed options are Apache Kafka, PostgreSQL, and Microsoft SQL Server.

What management interfaces are available?

The documentation lists a web console, REST API, command line, Maven plug-in, and language SDKs; it also describes a Java client.

Facts from Apicurio Registry's own pages

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

Where Apicurio Registry stands on Freedom251

Contract Testing Tools#2 of 22
Schema Registry Software#4 of 26