Documentation

Everything needed to go from API key to a running sandbox.

5 min read Getting started

Introduction

Renderops runs your code in isolated Linux microVMs that boot in under 200 ms. Hand a sandbox to an AI agent, a CI job, or untrusted user code, and nothing reaches your own infrastructure.

You're billed per second of runtime, metered from create() to kill(). A sandbox that's sleeping bills at 25% of the running rate, so idle work stays cheap.

Quickstart

Go from zero to a running sandbox in under 5 minutes. Every step is isolated, reproducible, and production-ready from day one.

Create a Renderops account

Every new account gets $25 in free credits — enough for hundreds of sandbox-hours. No credit card required to start.

Complete
2

Copy your API key

Your API key authenticates every SDK call. Treat it like a password — never commit it to source control. Add it to your .env file.

# .env
RENDEROPS_API_KEY=rk_live_...
Go to API Keys
3

Install the SDK

4

Create your first sandbox

5

Pause or kill the sandbox

Platform

A complete infrastructure layer for AI agents — from code execution to browser control to persistent storage.

Sandboxes

Isolated Linux microVMs with configurable CPU, RAM, and disk. Boot in 200ms.

Browser Automation

Full Chromium inside the sandbox. Drive Playwright and Puppeteer natively.

Persistence

Snapshots, volumes, and object storage. Checkpoint state between runs.

Networking

Custom domains, egress control, and private VPC peering.

Logs & Metrics

Real-time log streaming, structured events, and OpenTelemetry export.

Templates

Pre-built environments for Python, Node, Rust, Go, and custom Dockerfiles.

Chromium, headless and ready

Every sandbox ships with a fully-isolated Chromium instance. Connect via CDP, run Playwright, Puppeteer, or any compatible library without any driver setup.

Note: The browser instance is isolated per sandbox. Cookies, sessions, and local storage never leak between runs — making it ideal for multi-tenant AI agents.

import { chromium } from 'playwright'

// Get the CDP endpoint from the sandbox
const cdpUrl = await sandbox.browser.cdpUrl()

// Connect Playwright to the in-sandbox browser
const browser = await chromium.connectOverCDP(cdpUrl)
const page = await browser.newPage()

await page.goto('https://example.com')
const title = await page.title()

// Take a screenshot – saved inside sandbox filesystem
await page.screenshot({ path: '/sandbox/screenshot.png' })

console.log(title) // 'Example Domain'
await browser.close()
Console output
Browser started – Chromium 124.0.6367 88ms
Connected via CDP 91ms
Navigated to https://example.com 340ms
Example Domain
Screenshot saved – 1440×900px 390ms

CLI

The renderops CLI gives you full control over sandboxes, templates, and logs without leaving your terminal.

$ npm install -g @renderops/cli
$ renderops auth login
renderops ls List all active sandboxes
renderops create Boot a new sandbox interactively
renderops exec Run a command inside a sandbox
renderops logs Stream logs from a running sandbox
renderops kill Kill a sandbox and stop billing
renderops templates Browse and apply environment templates

Frequently Asked Questions

Ctrl+I