Give agents an operating system as a library.

Each agent gets a lightweight OS with filesystem, execution, and orchestration. Runs in your existing backend – no sandboxes, VMs, or SaaS.

Bring any agent or framework.

Pi, Claude Code, Codex, and OpenCode on the same virtual operating system—with integrations for Eve and Flue.

Tiny runtime.
Battle-tested security.

Powered byWebAssemblyandV8 isolates.

The same technology poweringChromeandCloudflare Workers.

Linux-compatiblewith POSIX files, processes, and networking.

Cold starts

92× faster

4.8 ms p50

agentOS
4.8 ms p50

Sandbox
440 ms p50

Memory per instance

47× smaller

~22 MB per instance

agentOS
~22 MB

Sandbox
~1024 MB

Cost per execution-second

254× cheaper

$0.000000073/s

Metering 100,000 concurrent VMs

agentOS$0.09
Sandbox$22.20

Library, not extra infrastructure

Install agentOS from npm and run it inside the backend process you already operate.

WebAssembly + V8, not a microVM

V8 isolates run JavaScript while WebAssembly contains compiled tools inside the same compact runtime.

Direct function calls, not extra APIs

Connect agents to your application with ordinary JavaScript calls instead of another network service.

Scoped access, not exposed credentials

Bind trusted host functions without ever giving the agent your raw secrets.

One process, not a VM per agent

Many isolated agent operating systems share one compact runtime instead of duplicating a full microVM stack.

Runs anywhere, no nested virtualization

Deploy on standard Linux infrastructure without a hypervisor or nested virtualization.

Execution

Run Bash, Node.js, Python, and registry software inside the same isolated VM.

  • Native JavaScript performance

    Run Node.js on native V8 isolates with the full JIT, not JavaScript compiled to WASM.

  • Built-in type checks

    Type-check agent-generated code and return diagnostics so the agent can fix errors.

  • Bindings

    Expose typed backend functions without giving credentials to the VM.

  • Subprocesses

    Spawn, stream, signal, and manage child processes with Linux-like semantics.

  • Network requests & servers

    Make outbound requests or serve HTTP from inside the VM under explicit permissions.

Explore execution docs
The agent writes one program instead of a chain of tool calls.

Filesystem

Every agent gets its own persistent POSIX filesystem. Mount S3, Google Drive, host directories, or a full sandbox at a normal path, then use familiar files and shell tools everywhere.

Explore the filesystem
StorageFilesystem path
Host directory
/workspace
S3
/data
Google Drive
/documents

Mounted into one persistent POSIX filesystem.

Orchestration

Schedule recurring agent jobs, build durable RivetKit workflows, connect agents, and share live sessions with ordinary application code.

Write code
Review
Decision
ShipApproved
RetryRejected
RivetKit checkpoints each step, decision, and retry.

Ships wherever your backend ships.

Each VM is a Rivet Actor with durable state. Your existing deployment works.

Library

npm install and run in your process. No servers.

Get Started
Rivet

Rivet Cloud

Managed agentOS on Rivet's edge network with BYOC support. Scales to millions of agents.

Sign Up

Self-Host

Run the open-source platform on Kubernetes, VMs, or bare metal.

Self-Hosting Docs

Turn your backend into the agent platform.

Open source under Apache 2.0. One npm install away.

Read the DocsView on GitHub