Kurkik

Status: announced, coming soon. Kurkik is not released yet and has no public download.

Kurkik is the broker side of keeping an API self-maintaining: it catches drift between your AsyncAPI document and the messaging system that actually runs, and proposes the fix. Together with the JetBrains plugin, which covers the source-code side, the declaration and the implementation stay in step. It is named after Kurkik Jalali, the fiery horse of the Armenian epic Daredevils of Sasun, who bridges worlds, shows what is really there, and is fast.

What it will do

• Document what exists. Point it at an Apache Kafka, Apache Pulsar, Amazon SNS or Amazon SQS estate and get an AsyncAPI 3.0 document: topics or queues, their settings, brokers, consumer groups and, optionally, the real message schemas from your schema registry.
• Be honest about gaps. When it cannot read something, the document says so. It never invents who publishes to a topic, because a broker cannot know.
• Find drift. Compare an AsyncAPI document with the live system: matching, changed, missing, or extra.
• Change with review. Apply a document to the system as a plan someone approves first. It creates and alters but never deletes, and risky changes stay out of the default approval.
• Fit secured environments. Works with TLS, SASL and cloud identity options. Secrets never end up in documents or error messages.

Who is it for

Platform and data engineers, architects and governance teams who need accurate AsyncAPI documentation for systems that already run.

Want it sooner?

Tell me what your estate looks like: open a discussion or sponsor the work. In the meantime, the AsyncAPI plugin for JetBrains IDEs generates AsyncAPI from Spring Messaging code.