Skip to main content
Sign In

The orchestrator for
agentic workloads.

A fast, high-density and scalable orchestrator for every workload an agent needs.Open-source and self-hostable.

Start Building
Give this to your coding agent
Introducing Rivet 3.0 Preview

Whatever the workload, there’s an Actor for it.

Actors

Long-lived processes with state, realtime, and scheduling built in

Agents

A durable process per agent, with memory that survives restarts

Workflows

Multi-step operations that replay instead of starting over

agentOS

A filesystem, shell, and network for code you did not write

Durable Streams

Real-time streams with history readers replay from any offset

Explore more Actors
  • Durable Streams
  • Vercel Eve
  • Vercel Workflow SDK
  • Flue

Built for everything agents need.

Run 7,242× more workloads per server.

An Actor lives inside a worker process you already run, not in its own container or VM. A server that held hundreds of sandboxes holds hundreds of thousands of Actors.

72.4 KBper running ActorRSS increase per running Actor. Measured with the Rust rivetkit SDK. The sandbox figure is a provider's documented default allocation as of November 4, 2026, not measured memory use. See the baseline.

Rivet Actors
0 × 72.4 KB

Sandboxes
0 × 512 MiB

Start in milliseconds, not seconds.

A cold start includes scheduling the Actor, loading its state, and serving the first request. No sandbox to boot.

4.99 msp99 cold startRound trip from sending a request to the first reply from a newly created Rivet Actor: 4.99 ms p99, on a three-zone cluster. The sandbox figure is a p99 from a third-party sandbox benchmark run on October 30, 2026. See the benchmark.

Rivet Actor
4.99 ms

Sandbox
1.70 s

Built for scale.

Actors are scheduled independently, so adding capacity means adding machines. The same control plane runs a thousand Actors or a billion.

Billionsof Actors
Billions of Actors on one control plane.

Hibernates when idle, wakes on demand.

An idle Actor writes its state and unloads. The next request brings it back with nothing lost.

0 MBwhile hibernating

Durable state for every workload.

Every Actor gets a SQLite database, backed by S3 with SSD speeds. Idle Actors cost nothing.

  • 10.4×

    cheaper

  • 1.07 ms

    writes

  • 1.36 ms

    readsStorage at rest using AWS list prices in us-east-1: S3 Standard at $0.023 per GB-month, compared with three Amazon EBS gp3 copies at $0.08 per GB-month each. Excludes request and transfer costs. See the calculation. Write and read latencies are p99 SQLite queries timed in the Rivet Actor, excluding the client round trip. Writes are single-row inserts acknowledged by 2 of 3 instances across zones. Reads are the first random point read after sleep on a 50 MB database. See the benchmark.

  • SQLite
  • S3
A plane of thirty-six small databases, one per Actor, with writes landing on them continuously.

Run the code your agent writes, securely.

Lightweight sandboxing on your own infrastructure, with granular control over network access, filesystem access, and resource limits.

Three streams of AI-generated code flow into a converter, and a stream of Actors flows out the other side.

Works with the tools you already use.

Typed SDKs for your backend and React hooks for your frontend.

  • TypeScript
  • Node.js
  • Rust
  • React
  • Effect

Other powerful features of the Rivet Orchestrator.

Routing, scheduling, types, and telemetry, built in.

Fault tolerance by designA node going down reschedules its Actors elsewhere with their state intact. No replay harness or checkpointing of your own.Multi-regionPlace Actors near the users and data they serve, and route requests to wherever each one currently lives.HTTP & WebSocket networkingAddress an Actor directly over HTTP or hold a live WebSocket to it. No queue or broker in between.End-to-end type safetyActor definitions generate their own client types, so a signature change breaks the build rather than production.React SDKFirst-party hooks that subscribe a component to an Actor's state and keep it live as the Actor updates.OpenTelemetry & observabilityTraces, metrics, and structured logs emitted in OTel format, into the collector you already run.Single Rust binaryThe control plane ships as one static binary with no external dependencies to stand up first.Cron & schedulingWake an Actor on a schedule or at a timestamp it sets for itself, without a separate scheduler.Sleeps when idleIdle Actors release their resources and wake with durable state intact when the next request arrives.Actor-to-actor callsActors address each other by key and call across the cluster as if the other one were local.No Kubernetes operatorOne control plane behind a load balancer, speaking plain HTTP inside your VPC. No CRDs, no operator, no service mesh to keep alive.Open sourceApache 2.0, self-hostable in full. The managed service runs the same control plane you can run yourself.

Run your agent infrastructure where your data already lives.

  • One stateless binary

    One container to install, monitor, and upgrade, on Kubernetes, a VM with systemd, or plain Docker. No database or message bus to run.

  • Managed in your VPC

    With BYOC, Rivet deploys and maintains the control plane inside your cloud over an outbound connection.

  • Storage you control

    Every Actor's data lives in a bucket you own: S3, Google Cloud Storage, Azure Blob Storage, or an S3-compatible store like MinIO.

  • Local dev matches production

    Use the same binary, APIs, and control-plane behavior from laptop to production.

Talk to an engineerExplore Enterprise

Supported clouds

  • Docker Compose
  • Kubernetes
  • Virtual Machine
  • Hetzner
  • AWS ECS
  • Railway
  • Render
  • Custom Platform

Start local. Deploy when ready.

Local & Self-Host

Install Actors and run it locally while you build. When you ship, run the same open-source control plane as a Rust binary or container on your own infrastructure.

  • AWS
  • Google Cloud
  • Azure
  • Hetzner
Open the quickstartRead self-hosting docs

Rivet Cloud

Deploy Actors on Rivet Cloud with managed infrastructure and persisted Actor data.

  • AWS
  • Google Cloud
Open the dashboard

BYOC

Run the control plane inside your own VPC, fully managed by Rivet. Your data never leaves your cloud and there is no inbound management connection.

  • AWS
  • Google Cloud
  • Azure
Read the BYOC docs

Frequently asked questions

Orchestration for agentic workloads.

Run agents, workflows, and sandboxes as durable Actors — on your infrastructure or ours.

Start Building Talk to an Engineer