Kurkik is the messaging-infrastructure side of a self-maintaining API. It reads your on-premise or cloud brokers, writes what it finds as AsyncAPI, and catches drift between your documents and what actually runs - then proposes the fix.
Guards against API drift between your AsyncAPI documents and the brokers that actually run.
Keeps APIs self-maintaining export, compare and fix, all from one AsyncAPI document.
Makes setups repeatable apply one document to dev, staging and prod, with a plan you approve.
# what prod holds$ kurkik topology prod --consumers# staging, written down as AsyncAPI$ kurkik export stagingwrote staging-kafka.yaml# and what prod does not agree with$ kurkik diff staging-kafka.yaml prod; echo exit $?exit 2 # drift$
kurkik - terminal UI
$ kurkik# preview a Kafka, a Pulsar, an SNS and an SQS connection# every topic setting and where it comes from, partitions, schema, who reads it# walk a diff of staging against prod, as a tree# add a connection in a form, export with a choice$
agent
$ claude mcp add kurkik -- kurkik mcp> Orders stopped reaching the billing service on prod. Compare prod with staging and tell me what drifted.asyncapi_connections asyncapi_topology prod asyncapi_compare staging prodThe evidence: the topic and its consumers, side by side, read-only.$
A self-maintaining API finds drift as soon as it appears and gives you the tools to find the reason, prepare a patch and apply it. Kurkik covers the messaging systems; the AsyncAPI plugin for JetBrains IDEs covers your source code.
Features
Everything between your document and your brokers
Read-only by default. The only writes are syncs, and those show you the plan first.
kurkik topology
$ kurkik topology prod --consumers$ kurkik topology queues-prod# or all of it, browsable$ kurkik$
Yes. Kurkik writes the first document for you from what is already running. To read, validate and visualise AsyncAPI documents, see the tools at asyncapi.pavelon.dev.
Which messaging systems are supported?
Apache Kafka, Apache Pulsar, Amazon SNS and Amazon SQS. RabbitMQ is next. Schemas are read from Confluent-compatible registries: Confluent, Karapace, Redpanda and Apicurio.
My system isn’t on the list - NATS, MQTT, Solace…
Tell us what you run through the form below. Custom integrations are on the table.
How does Kurkik work with AI agents?
Through its MCP server or a skill. The agent forms a first hypothesis, collects topology and compares environments with Kurkik’s read-only tools, then uses that evidence to refine or reject the hypothesis.
Is Kurkik safe to use in production?
Kurkik only reads - except for kafka sync and pulsar sync. Those show a dry-run plan, ask before they write, take a snapshot first and can be reverted. Credentials are never stored in plain text, and the MCP tools only read.
How is Kurkik different from Confluent CLI, Solace Event Portal or Gravitee?
Kurkik is vendor-neutral: it is not tied to one broker vendor or platform. It speaks one recognisable format, AsyncAPI, so the documents it produces can also configure API gateways or feed docs in EventCatalog.
When can I try it?
Early access opens soon. Leave your details and you will get a personal email when it does.
Early access
Be first to try Kurkik
Leave your details and you will get one personal email when early access opens. No newsletter, and nothing shared or sold.
Kept with our form provider, Netlify - no mailing tool
Used only to write to you about Kurkik
Deleted whenever you ask
May we use Google Analytics cookies to count visits and see which countries Kurkik reaches? Nothing is loaded until you say yes. Details