Skip to main content
Snakream is a real-time message stream service. Giving every document, every session, every task its own append-only “chat log”, data can only be added, never lost, and anyone can replay from the beginning or subscribe for live updates at any time. Under the hood it runs a multi-node cluster for high availability. Write latency is under 5ms. Reads support SSE push. The API is plain HTTP REST, you can use it with curl. Illustration of the Snakream theme Snakream is a made-up word from snake and stream. In a normal stream, data passes through. In Snakream, each append becomes part of the log itself, like a snake extending its body. The head is the current write point facing new input, and the body is the committed sequence that grows over time.

​
Why you need this

​
Activity feeds / audit logs

Order state changes, user actions, system events, append them to a stream. Any consumer gets the full history in one request or subscribes for live updates. Naturally ordered, push-based, and replayable from any point in time.

​
Collaborative editing

Online document editors need every user’s changes to reach every other user in real time. Each edit is appended to a stream, other clients subscribe via SSE. On reconnect, clients resume from their last offset, no gaps, no duplicates, no WebSocket server to build.

​
AI agent execution visibility

AI coding assistants let users watch an agent work step by step instead of staring at a spinner. The agent appends each step to a stream, the frontend subscribes via EventSource. If the agent process crashes, a new one picks up from the stream, progress lives in the stream, not in process memory.

​
Why not existing alternatives

​
Durable and fast: not a trade-off

Object-storage-backed stream stores persist every write to S3 before acknowledgment. This forces a choice: S3 Standard gives multi-AZ durability at 400ms per write, S3 Express cuts that to 40ms but drops to a single availability zone. Snakream doesn’t make you choose. Writes are acknowledged after a majority of nodes fsync to local disk — under 5ms P99. Data then flushes asynchronously to S3 Standard, retaining full multi-AZ, multi-region durability. Fast writes and global durability, not one or the other.

​
Built for multi-writer scenarios

Database sync layers push table changes to clients — unidirectional, tied to a specific database. Snakream is bidirectional: any client can write, any client can read. The stream is the source of truth, with protocol-level support for snapshot recovery, binary SSE, and exactly-once writes.