#7777th of 118 in Agent frameworks and SDKs

rivet

Stateful Actor runtime with SQLite and WebSockets for durable agents and realtime apps

Stars
6.9k
License
Apache-2.0
Last commit
Nov 2026
Last release
Nov 2026
Language
Rust
Stars, last 29 weeks+1,430
20 Apr 2026: 5,421 stars27 Apr 2026: 5,434 stars4 May 2026: 5,449 stars11 May 2026: 5,486 stars18 May 2026: 5,507 stars25 May 2026: 5,519 stars1 Jun 2026: 5,525 stars8 Jun 2026: 5,533 stars15 Jun 2026: 5,548 stars22 Jun 2026: 5,591 stars29 Jun 2026: 5,628 stars6 Jul 2026: 5,659 stars13 Jul 2026: 5,673 stars20 Jul 2026: 5,707 stars27 Jul 2026: 5,736 stars3 Aug 2026: 5,797 stars10 Aug 2026: 5,994 stars17 Aug 2026: 6,053 stars24 Aug 2026: 6,079 stars31 Aug 2026: 6,094 stars7 Sept 2026: 6,115 stars14 Sept 2026: 6,133 stars21 Sept 2026: 6,156 stars28 Sept 2026: 6,206 stars5 Oct 2026: 6,256 stars12 Oct 2026: 6,295 stars19 Oct 2026: 6,335 stars26 Oct 2026: 6,384 stars2 Nov 2026: 6,581 stars9 Nov 2026: 6,851 stars

5,421 on 20 Apr 20266,851 on 9 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

Rivet runs long-lived Actors with in-memory state, a per-Actor SQLite database, WebSockets and scheduling, one per agent, user or session. A Rust control plane schedules and persists them, using an S3-compatible bucket as the only dependency. Actors are written with the RivetKit TypeScript library (Rust SDK also available) on plain Node.js or Bun, and the project pitches them as a lighter place to run agent loops than per-agent sandboxes.

Who it is for: Backend engineers building durable agents or stateful realtime services

Strengths

  • Only external dependency is an S3-compatible bucket; no Postgres, NATS or FoundationDB
  • Runs on stock Node.js or Bun, not a custom runtime
  • Per-Actor SQLite, hibernation, cron scheduling and Actor-to-Actor calls built in
  • Self-host on Docker Compose, Kubernetes, VMs, or use Rivet Cloud or BYOC

Weaknesses

  • General actor platform; agent features come from optional libraries, not core
  • Headline latency and memory figures are vendor benchmarks against E2B and Durable Objects
  • Python and Swift clients are experimental; Dynamic Apps is in preview
  • Running the control plane adds operational work compared with an in-process library

What it needs

  • no GPU
  • Docker
  • Needs S3-compatible object storage (S3, GCS, Azure Blob, MinIO, R2); local filesystem backend for single-machine trials
  • Models: Vercel AI SDK (README example uses OpenAI)

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Quick answers

Is rivet open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Can you run rivet with Docker?

Yes. Its repository has a Docker setup: a Dockerfile, a Compose file or a published image.

Does rivet need a GPU?

No, it runs without one.

Also in Agent frameworks and SDKs

See all 118
Also in Agent frameworks and SDKs
RankProjectScore
1ppt-masterAgent skill that turns documents into natively editable PowerPoint decks Live demo ↗ (opens in a new tab)75.9k stars+15,456 (+26%) in 30 daysMIT95 out of 100
2openai-agents-pythonPython SDK for multi-agent workflows with handoffs, guardrails and tracing30.6k stars+689 (+2.3%) in 30 daysMIT91 out of 100
3mastraTypeScript framework for building AI agents, workflows and MCP servers29.5k stars+792 (+2.8%) in 30 dayscustom license91 out of 100
#4browser-usePython library that lets an LLM agent control a web browser Live demo ↗ (opens in a new tab)120.7k stars+3,290 (+2.8%) in 30 daysMIT90 out of 100
#5copilotkitSDK for adding agent chat, generative UI and shared state to apps38.6k stars+760 (+2.0%) in 30 daysMIT90 out of 100