All 248 Dependencies
Every package Rivet depends on, ranked by repo health score.
Rivet Actors are long-running, lightweight processes that combine in-memory state, automatic persistence, real-time WebSockets, durable queues, and scheduling into a single unified primitive. Instead of stitching together Redis, a message broker, a cron system, and a database, you define an actor once and the runtime handles state co-location, hibernation when idle, and global edge routing near your users.
The architecture is built for the workloads that break traditional serverless: AI agents that need persistent context across calls, collaborative documents where every edit must reach all connected clients instantly, per-tenant databases with zero-latency reads, and sandbox orchestration where lifecycle management is non-trivial. Each actor is its own isolated process — one per agent, per session, or per user — so state never bleeds between tenants.
Rivet ships as three deployment tiers. RivetKit is an npm library you install and run locally with no infrastructure. The self-hosted Rust engine (or Docker container) adds Postgres, FoundationDB, or filesystem persistence and scales horizontally by adding nodes. Rivet Cloud provides the fully managed global edge network with automatic regional routing, ~20ms cold starts, and $0 idle cost. All three tiers share the same TypeScript API, so local development and production behave identically.
Under the hood, the engine consists of Pegboard (actor orchestration and networking), Gasoline (durable workflow execution with full replay semantics), Guard (traffic routing proxy), and Epoxy (an EPaxos-based multi-region KV store). The built-in Inspector dashboard provides a SQLite viewer, workflow visualizer, event monitor, and interactive REPL for debugging actors in both development and production.
