Event pipelines · since 2023
Send one event. Read it back.
Conduit is streaming pipelines for product engineers: named streams, polite schemas, and replays that never touch the live path. The terminal beside this paragraph is the quickstart, verbatim.
$ conduit streams create orders --retention 7d Created stream orders (retention 7d, region bom) $ conduit publish orders '{"id": 1042, "total": 1899}' Accepted 1 event (key auto, offset 881203) $ conduit consume orders --from earliest --limit 1 {"id": 1042, "total": 1899, "_offset": 881203} $
Fleet uptime, 90 days
99.99%
Publish p99, worst region
38ms
Sandbox
Free
Docs that respect your time
All 3 guides01 · 5 min
Quickstart: first event in ninety seconds
Create a stream, publish one event, read it back. No card, no cluster.
02 · 8 min
Schemas that reject politely
Register a JSON schema per stream and watch bad events bounce with reasons.
03 · 6 min
Replay without begging the producer
Rewind any consumer to any offset and rebuild state from the log.
Pricing
Calculator and tiersSandbox
Free/ month
One million events a month, free forever. Three streams, seven-day retention.
Most teams
Team
₹4,200/ month
Fifty million events, then ninety rupees a million. Schemas and replays included.
Scale
₹38,000/ month
A billion events with dedicated throughput and a human on call.