Application state often ends up split across process memory, custom recovery code, and one-off real-time plumbing. When a worker crashes or a client reconnects, replay and recovery get harder than they should be. Snakream provides durable, replayable streams for application state. Give each document, session, task, or run its own stream for recovery, replay, and live updates over plain HTTP.Documentation Index
Fetch the complete documentation index at: https://docs.snakream.tonbo.dev/llms.txt
Use this file to discover all available pages before exploring further.

What you get
Crash recovery. Replay an object’s stream and resume from a known state after a restart. Live updates over HTTP. Read from the beginning, catch up, or tail live with long-poll or SSE.curl and EventSource work out of the box.
Automatic lifecycle. Keep recent data hot, archive older data automatically, and expire finished streams with TTL when they no longer matter.
Try it now
Learn more
- Quick Start — step-by-step walkthrough
- Why Snakream — where it fits, and where it doesn’t
- Concepts — streams, buckets, offsets, read modes, snapshots
- Architecture — how the cluster works
- API Reference — full HTTP API surface
- Protocol Spec — the Durable Streams Protocol and extensions

