Rivet

Rivet Actors are long-running, lightweight processes for stateful workloads. State lives in memory beside the compute and persists automatically, which removes the usual routine of loading a session out of a database and writing it back on every single request.

You create one actor per agent, per session, per document or per tenant, and each one arrives with the plumbing already attached: WebSockets for real-time streaming, workflows with automatic retries, durable queues, and its own timers and cron jobs. Actors run indefinitely while active and hibernate when idle, scaling down to zero.

Observability is built in, from local development through to production.

• SQLite viewer: browse and query an actor's own database while it runs.
• Workflow state: inspect progress, steps and retries as they execute.
• Event monitoring: track every state change and action as it happens.
• REPL: call actions, subscribe to events and interact with your code directly.
• Agent skills: a published skill set gives coding assistants what they need to add Rivet to a project.

RivetKit is a library first, so installing the package runs actors inside your own process during development. Production has three routes: a self-hosted Rust binary or Docker container backed by Postgres, the file system or FoundationDB, or the managed Rivet Cloud edge network. Clients exist for Node.js, Bun, Deno, React and Next.js, with examples for Hono, Express, Elysia and tRPC.