One binary, zero YAML
danube is the broker, the CLI, the MCP server and the console backend. Grow from one node to a Raft cluster with flags, not config files.
# 1. Start a local node on 127.0.0.1:6650danube up standalone
# 2. Create a durable topic by saying what it is fordanube topic create /default/events --intent event_stream
# 3. Start a reader, then send from another terminaldanube consume /default/eventsdanube produce /default/events -m 'hello'That’s the whole setup. No config files, no ZooKeeper, no separate schema registry.
One binary, zero YAML
danube is the broker, the CLI, the MCP server and the console backend. Grow from one node to a Raft cluster with flags, not config files.
Say what a topic is for
Pick an intent (realtime, event_stream, task_queue, audit_log) and Danube sets delivery, durability, retries and dead-letter queues for you.
Ready for AI agents
Task queues with leases and checkpoints, request/reply, audit logs, topic branching for replay, and an MCP server so agents can run the cluster.
Cheap durability
Fast local WAL, with segments tiered to S3, GCS, Azure or a shared filesystem. Built-in schema registry on the same port.