Rivet is an open-source actor runtime for stateful AI-agent and realtime workloads, self-hostable as an alternative to Cloudflare Durable Objects.
Yes, Rivet is open source under the Apache-2.0 license.
Rivet has a free tier plus paid plans. The open-source version can be self-hosted with no license cost; you pay only for your own infrastructure.
Yes, Rivet can be self-hosted (the source is available under the Apache-2.0 license).
Rivet is an open-source actor runtime for stateful workloads: AI agents, collaborative apps, and durable execution. Its pitch is the stateful-actor primitive (state, storage, and compute co-located per actor) running on infrastructure you own, positioned as a self-hostable alternative to Cloudflare Durable Objects. Open source: yes (Apache-2.0); self-hostable; free OSS core with an optional paid managed cloud. It has ~6.2k stars, dates back to 2023, and is actively maintained (pushed 2026-10-04).
Rivet gives you "actors" as the unit of stateful work: each actor holds its own state and storage and runs close to it, which suits agent sessions, realtime collaboration, and durable, resumable workflows. You run the same open-source control plane yourself, as a Rust binary or a container, on your own infrastructure, or use Bring Your Own Cloud where the control plane runs inside your VPC. The project positions itself explicitly against Cloudflare Durable Objects: it states no 128 MB per-actor memory cap, no 10 GB SQLite limit, no random eviction of actors, and that it runs on vanilla Node.js or Bun rather than a custom runtime. Open source: yes (Apache-2.0); self-hostable.
As GTM teams start building their own agents (prospecting, enrichment, support, research), those agents need somewhere to hold state between steps and survive restarts. That stateful backbone is usually rented from a managed platform, and Cloudflare Durable Objects is a common default that locks the workload to one vendor's runtime and its caps. Rivet's bet is that the same actor primitive can run on infrastructure you own, under a permissive licence, so the stateful layer of your agent stack is not a per-vendor dependency. The honest read: the headline latency and memory figures are the maker's own and are not benchmarked here, operating your own control plane is real work that a managed Durable Objects user is choosing to avoid, and the free path is the self-hosted one (the managed Rivet Cloud is paid). For a team that already prefers to own its runtime, it is a credible open alternative worth a trial.