Run cloud agents on your infra

Self-host execution while Oz manages orchestration, integrations, and run visibility.

Book a demo Read the docs

Trusted by over 16,000 engineering teams at leading companies

Since 2023

Keep agents under your control.

Agents execute on machines you provision inside your cloud, VPC, or data center.

Orchestrate your agents.

Oz manages scheduling, routing, integrations, and the full run lifecycle.

Enterprise-grade observability.

View every agent run in real time with auditing, observability, and tracing built in.

Oz agents work where you do

Run Oz agent workloads on any infrastructure including public cloud, VPC, or on-prem.

Read the docs

Oz agents work across any cloud or on-prem environment

Trigger agents across your stack

Start runs from the CLI, API, Slack, Linear, or the Oz dashboard. Integrate agents directly into existing developer workflows and automation pipelines.

See integrations

Diagram showing Oz agents triggered from CLI, Web, Integrations, API/SDK, and Warp

Use the latest models without changing infrastructure

Use Claude, Codex, Gemini, or other supported models. Oz abstracts the execution layer so teams can change models without modifying their runtime environment.

View supported models

Model picker showing Claude Sonnet, Claude Opus, GPT Codex, and Gemini Pro

	Other Agent Platforms	Oz
Oz is built for enterprise
Control over where your code runs	Code runs in vendor-managed environments you don't control.	Run agents inside your own cloud, VPC, or on-prem environment.
Runs inside your VPC	Workloads execute in the vendor's cloud, outside your VPC.	Self-hosted workers run inside your VPC alongside your other services.
Self-hosted agent execution	Execution is locked to vendor-provided runners.	Bring your own compute. Oz coordinates; your hardware runs the work.
Central orchestration layer	Limited orchestration — typically per-agent, with no unified scheduler.	One control plane for scheduling, routing, retries, and lifecycle.
Full audit history	Limited audit trails, often retained for short windows only.	Every run, prompt, tool call, and diff is captured and queryable.
Open worker architecture	Closed worker model with vendor-defined runtimes.	Workers are open and pluggable — run any container or runtime.
Steerability	Fire-and-forget — no in-flight steering once a run starts.	Pause, redirect, and steer agents mid-run from the CLI or dashboard.

The @warpdotdev crew keeps doing awesome work. Spin up hundreds of agents in the cloud through your CLI or phone, what a world!

Lenny Rachitsky

Author, Lenny's Newsletter & Podcast

Get started with Oz

Pick the path that fits how you want to try it.

Quick start.

Launch an Oz agent right from the web app. Best for launching coding automations for tasks like PR review. Connect a GitHub repo, pick an execution environment, choose a curated skill or one of your own, and Oz manages hosting, execution, and updates.

Launch an agent

Build-your-own.

Use the Oz CLI, SDK, and API to launch local or cloud agents. Best for running parallel agents. Create environments via the CLI, fire custom triggers from internal events, host on our infra or yours, and keep full control over network access, data residency, and secrets.

Read the docs

Talk to our team.

Talk to a member of our team. Request a demo, learn how Warp can help your specific organization, and get started with a trial.

Book a demo