# A computer for every agent, in your own cloud.

Design partners

Firecracker microVMs for agents and untrusted code. Boot in about a second, pause with memory, resume in under a second, and keep the disk for next time. One API, on compute you own, in your VPC.

- **cold boot to a running sandbox:** ~1 s
- **resume from pause, memory and all:** <1 s
- **per sandbox, never shared:** 1 kernel

Trusted by engineering & platform teams at scale

## Agents are only as good as their computers.

### Your code leaves your cloud

Hosted sandboxes run your repos, secrets, and data on someone else's infrastructure.

### Every session starts cold

Clone. Install. Build. Again. The agent waits, and you pay for it.

### A shared kernel is a thin wall

AI-written code in a container shares a kernel with everything else on the host.

With Ravion

## One API. Instant computers.

Create, exec, pause, resume. From TypeScript or plain HTTP.

Step 1

### Create a sandbox in one call

Pick CPU, memory, and a disk. Name the disk and the next sandbox starts with everything the last one installed.

Replaces E2B, Daytona, Modal

Step 2

### Everything is an API

Exec commands, write files, pause, resume. Pause freezes memory and disk. Resume picks up mid-thought, in under a second.

Replaces custom VM orchestration

Step 3

### The same sandboxes run your CI

Pipelines and GitHub Actions runners use the same microVMs and sticky disks. One fleet, in your account.

Replaces separate CI fleet

## Three calls to a computer.

Create, exec, pause. The same API from TypeScript, Python, or curl. Proposed, and open for feedback.

## Untrusted code. Your perimeter.

Agents run where your data already lives. Ravion only hands out the machines.

Interact with Ravion through the UI, CLI, API, or Git. Ravion sends sandboxes to your AWS account and gets status back. Everything else runs inside your account.

-   UI
-   CLI
-   API
-   Git

RavionControl plane

-   Schedules sandboxes
-   API, SDK, and keys
-   Logs and usage

Sandboxes

Status

Your AWS accountYou own it

Your VPCPrivate network

Firecracker hostsEC2

-   sbx\_7Hq2
-   sbx\_K91d
-   sbx\_p4Wm

A network namespace per sandbox

Your data

-   Postgres
-   Internal APIs

A hop away

-   Snapshots and disks in S3
-   Scoped credentials per sandbox

## Fast, isolated, and yours

### One-second boots.

Firecracker microVMs on hosts in your account.

### Sub-second resume.

Pause with memory. Resume exactly where it stopped.

### Instant sticky disks.

Copy-on-write disks stream blocks as you read them, so a warm disk is ready before you need it.

### Hardware isolation.

A VM per sandbox, its own network namespace, scoped credentials.

### In your VPC.

Reach private databases and APIs without opening a single port to the internet.

### Spot pricing.

Run on Spot capacity at AWS Spot rates.

## Coming from another sandbox?

The Sandbox API is in early access with design partners. Here is how your code maps to it.

Teams come to Ravion from E2B when agents need to reach private data and the sandboxes have to run inside their own AWS account.

agent.ts+7\-3

```typescript
-Before: import {Sandbox} from "e2b"
+After: import {Ravion} from "@ravion/sdk"
+After:
+After: const ravion = new Ravion()

-Before: const sandbox = await Sandbox.create()
-Before: await sandbox.commands.run("pnpm test")
+After: const sandbox = await ravion.sandboxes.create({
+After:   environment: "agents-prod",
+After: })
+After: await sandbox.exec("pnpm test")
```

E2BRavion

sandbox.files.write()POST /v1/sandboxes/{id}/files

Move in three steps

1.  01

    Become a design partner and connect your AWS account.

2.  02

    Swap the E2B client for the Ravion SDK.

3.  03

    Name a disk so each sandbox starts with everything the last one installed.

Sandbox questions

### When can we use it?

We're building Sandboxes with a small group of design partners. Apply and tell us what your agents need.

### What is a sandbox?

A Firecracker microVM with its own kernel, network namespace, and disk. Create it from the API, run commands in it, pause it, resume it, throw it away.

### Where do sandboxes run?

On EC2 hosts in your AWS account and VPC. Ravion manages the fleet. You keep the data and the network.

### What does a sticky disk do?

Name a disk and it outlives the sandbox. The next sandbox with that name restores it in milliseconds and streams only the blocks it reads.

### Is this what powers Ravion CI?

Yes. Pipeline steps and GitHub Actions runners run on the same sandboxes. [See pipelines](https://www.ravion.com/pipelines)

## Give your agents somewhere safe to work.

We're building Ravion Sandboxes with a small group of design partners.

Firecracker microVMs / Sticky disks / Runs in your AWS account