Guides

Why actors eliminate complexity instead of managing it, and how merging state and compute removes the biggest source of latency in modern applications.

Build an AI agent backend with persistent memory: one Rivet Actor per conversation, queued message handling, and streaming LLM responses as realtime events.

Build a realtime chat room backend with Rivet Actors: one actor per room, SQLite-backed message history, and WebSocket broadcast to every connected client.

Build a collaborative text editor backend with Yjs CRDTs and Rivet Actors: per-document actors relay sync and awareness updates and persist snapshots.

Patterns for durable one-shot, calendar, and fixed-interval work on Rivet Actors.

Multi-tenant data isolation with one Rivet Actor per tenant: the actor key is the tenant id, so each tenant gets its own isolated dataset and migrations.

Live cursors and multiplayer presence with Rivet Actors: per-connection cursor state, realtime updates over events or raw WebSockets, and throttling.

Pragmatic patterns for building multiplayer games: matchmaking, tick loops, realtime state, interest management, and validation.

Give each coding session a sandbox, a filesystem, and durable memory on Rivet Actors.

Ship a backend per user the moment the agent generates one, on Rivet Actors.

Run agents against internal data, inside your own network, on Rivet Actors.