Docs

MIOSA documentation

Build on MIOSA

The infrastructure behind agent products. Run agents in isolated sandboxes and full computers, preview what they build, and ship it to production under your own brand.

Start building API reference
npm i -g @miosa/cli
CLI docs
Browser use A real browser
in every sandbox. Drive it with Playwright over CDP, or watch and take control. Browser use quickstart

Learn MIOSA, earn up to $100 in credits

Three tracks, one finish line. Words +$20, Games +$50, Videos +$30 (not open yet).

See how it works
$0 / $100

The platform behind agent products

Sandboxes, computers, agent runs, previews, and deployments under your own brand. Start with the guide

Product names and logos are trademarks of their respective owners and are used to describe what you can build. No endorsement implied.

Two ways to build

Build for your customers, or for your own team

For product teams

Build a product

Launch your own agent platform and sell it to customers, on MIOSA infrastructure that stays invisible.

Launch an agent platform for your customers: dots, Grok Bot, or Manus-style products
White-label branding, custom domains, and your own billing
Multi-tenant isolation with per-customer usage and attribution
Always-on agents, each with its own computer
Run on MIOSA compute or bring your own cloud
Start from OSA, our open-source agent, as your first product agent
Pick what to build Platform builder guide

For your own company

Build your company's Business OS

An internal platform where your team's agents, apps, and data live together. You do not launch it, you run your company on it.

One internal platform where your agents, apps, data, and workflows live together
Every agent gets its own computer, connected to your CRM, docs, calendar, and terminal
Your own access control, secrets, and audit trail
Start your agents from OSA, our open-source agent, and run them on those computers
Not something you launch. It is how your company runs
BusinessOS template Build internal apps

Open sourceApache 2.0

Start here

Everything you need to ship an agent platform

Quickstart

Create a sandbox, run code, and publish a preview in a few minutes.

Sandboxes

Isolated Linux environments for generated code, installs, builds, and previews.

Computers

Full desktops for browser and computer-use agents, with human handoff.

Deployments

Immutable releases on stable URLs, with domains, environments, and rollback.

SDKs

Typed clients for the whole API.

API reference

Every REST endpoint for sandboxes, computers, deployments, and tokens.

Or start from an agent

Learn first

Learn the platform before you build

Remember how much it took to stand up infrastructure on AWS? We collapsed that. You get the power of a data center without needing to know all of it. Even if you are not deeply technical, you can build a real platform by driving MIOSA through the CLI, MCP, and the SDKs. In many cases you can vibe-code it with an agent like OSA, Claude Code, or Codex.

Drive it with OSAOur open-source agent, Apache 2.0

This is not basic. To build well you need the vocabulary. Learn the words and the primitives. We teach you all of it.

Learn the words The glossary defines every term used across MIOSA, from sandbox to workspace to release, in plain language. Open the glossary
Learn with games Quiz, flashcards, match, scenarios, CLI commands and a stack builder, at your level: like I'm 9, high school, builder, or technical.
Daily 5 Five mixed questions a day Build the stack Assemble a real architecture Command or not? Spot the real miosa command Quiz 10 definitions, four choices
See all 11 games
Then follow the path Full learning paths

For LLMs

Machine-readable docs

Agents can retrieve current public documentation from indexes, without scraping the site.

Agent operating guidellms.txtllms-full.txt
Current production contract

Use URLs returned by the API instead of constructing hostnames yourself:

  • preview_url for sandbox previews.
  • desktop_url for computer desktops.
  • public_url for deployments.
  • custom_domain or deployment-domain URLs when a workspace has branded domains configured.
  • docker_deploy_app in deployment responses as App Engine container proof.

For App Engine, a deployment is not proven live until it has a normal Deployment row, deployment_product: "docker_deploy", an active workspace App Engine host, a docker_deploy_app row, a running container route, and an HTTP response from public_url.

See the changelog for the latest public platform behavior.