Karapace
karapace.io
- Free plan
- API
- Self-hosted
What Karapace is
Karapace is a free, open-source implementation of the Kafka Schema Registry and Kafka REST Proxy. Its registry stores Avro, JSON Schema and Protobuf schemas centrally, keeps version histories and checks compatibility between versions. The REST Proxy exposes HTTP APIs for producing and consuming Kafka events and carrying out administrative operations. Karapace implements the Confluent Schema Registry API and Confluent REST Proxy API versions 1 and 2, using version 2 by default. A leader-and-replica architecture supports high availability and load balancing across instances. Prometheus-native metrics and OpenTelemetry integration provide monitoring, while Sentry reporting can be enabled. Schema Registry authentication accepts HTTP basic authentication and OAuth2/OIDC bearer-token validation. The REST Proxy forwards OAuth2 tokens to Kafka and the Schema Registry rather than validating them itself. Karapace is self-hosted, requires Python 3.12 or newer, and can be installed from Docker images or source. Default Docker endpoints use ports 8081 and 8082. Avro references are supported from version 6.1.0; JSON Schema references are not supported in the documented table, and normalization is limited to Protobuf.
Who it suits
Karapace suits teams running Kafka that want a self-hosted registry and REST interface. It is useful where Confluent API compatibility, schema formats and observability integrations matter.
Good to know, and what to watch
- Free and open-source deployment
- Supports Avro, JSON Schema and Protobuf
- Confluent API compatibility
- Leader-replica high availability design
- Prometheus and OpenTelemetry integrations
- Requires Python 3.12 or newer
- Self-hosted installation is required
- JSON Schema references are unsupported
- Normalization is limited to Protobuf
Plans
Every plan and priceFree and Open Source
Free plan
The verdict
Karapace provides Kafka schema management and REST access without a license fee. Its compatibility and deployment choices suit technical teams, but version requirements and documented schema limitations need planning.
What the maker publishes
- Authentication
- Schema Registry authentication supports HTTP basic authentication and OAuth2/OIDC bearer-token validation. source
- Founded
- 2020 source
- Headquarters
- Helsinki, Finland source
- High availability
- A leader/replica architecture provides high availability and load balancing across instances. source
- Installation
- Karapace requires Python 3.12 or newer and can be installed from Docker images or source. source
- Kafka compatibility
- Karapace implements the Confluent Schema Registry API and Confluent REST Proxy API v1 and v2, with v2 as the default. source
- Maker relationship
- Aiven describes Karapace as an Aiven-built open-source Schema Registry and REST Proxy for Aiven for Apache Kafka. source
- Monitoring integration
- Sentry error reporting can be enabled with the sentry configuration key or the SENTRY_DSN environment variable. source
- Normalization limit
- Schema normalization is currently supported for Protobuf only, and Karapace does not implement every Confluent Schema Registry normalization feature. source
- OAuth token handling
- The REST Proxy forwards OAuth2 tokens to Kafka and the Schema Registry instead of validating them itself. source
- Observability
- Karapace exposes Prometheus-native metrics and integrates with OpenTelemetry for traces and metrics. source
- Purpose
- Karapace is a free and open-source implementation of the Kafka Schema Registry and Kafka REST Proxy. source
- REST proxy
- The REST Proxy provides HTTP APIs for producing and consuming Kafka events and performing administrative operations. source
- Schema formats
- Karapace supports Avro, JSON Schema, and Protobuf schemas. source
- Schema references
- Avro schema references are supported from Karapace version 6.1.0 onward, while JSON Schema does not support references in the documented table. source
- Schema registry
- Its Schema Registry stores schemas centrally, maintains version histories, and checks compatibility between versions. source
- Service endpoints
- The Docker setup exposes the Schema Registry on port 8081 and the REST Proxy on port 8082 by default. source
Checked against the maker's pages on 30 Sept 2026.