Features

Browse every subject in your registries. View schema content, field structure, format (Avro, JSON Schema), and all versions at a glance.

Side-by-side, field-level comparison between any two versions. LCS-based algorithm highlights additions, removals, and modifications.

Interactive dependency graph between schemas. Spot orphans, shared components, and high-impact schemas that many others depend on.

At-a-glance metrics: subject count, AsyncAPI coverage, channel coverage, enrichment progress, governance score distribution, and data layer breakdown.

View and monitor the compatibility mode of each subject (BACKWARD, FORWARD, FULL, NONE). Detect drift between policy and configuration.

Tags, ownership, descriptions, data layers, and classification — stored in event7, not your registry. Provider-agnostic: survives registry migrations.

Routes schemas based on registry type during import. Apicurio accepts all formats. Confluent-like registries only receive Kafka schemas — others are skipped with a warning.

Generate AsyncAPI 3.0 specs with Kafka bindings (partitions, replication, Magic Byte), key schema separation, Avro-to-JSON-Schema conversion. Stores hash for drift detection.

Import a v3 spec to create channels, bindings, enrichments, and register schemas — all in one operation. Two-phase: preview then apply. 9 broker protocols supported.

Export governance data to EventCatalog — scores, rules, channels, teams, AsyncAPI specs. First governance-aware generator. Domain mapping by prefix or tag.

Connect Confluent Cloud (API Key), Confluent Platform (LDAP/RBAC), or Apicurio v3. Adapter pattern — one Python file per provider. Karapace and Redpanda work out of the box.

Terminal-style interface with 6 context commands (/health, /schemas, /drift, /catalog, /refs, /asyncapi) and 3 write actions (enrich, generate, delete). BYOM — Ollama, OpenAI, or any compatible API.