MIOSA developer platform

Build in a sandbox. Run anywhere.

One operating layer for agents that write code, use computers, manage data, and ship durable applications.

Open quickstart Read core concepts

Isolated sandboxes Immutable releases Customer cloud ready

production workflow

ready

Build Sandbox

Preview Live URL

Verify Evidence

Promote Release

Run Production

Terminal miosa.app.yml

$ miosa app preview . --json

$ miosa app verify rel_9f2a . --json

$ miosa app promote rel_9f2a . --yes

✓ release rel_9f2a verified and live

Public URL my-app.osa.miosa.app

View deployment contract

Explore the platform

Run many workspace apps as containers on one always-on App Engine host, with MIOSA-owned routing, domains, and proof.

Dispatch Claude Code, Codex, or command runners to sandboxes and computers, then stream events and collect artifacts.

Follow the authoritative discovery, preview, verification, promotion, recovery, and rollback contract for automated workers.

Use REST, CLI, TypeScript, Python, Go, Java, Elixir, MCP, and ADK surfaces that share the same deployment proof contract.

Attach Postgres, storage, Redis, volumes, and durable application state without rebuilding the infrastructure layer.

Core infrastructure

Use isolated Linux environments for generated code, dependency installs, file edits, build commands, tests, and preview servers.

Publish generated applications to stable URLs with versions, releases, environment variables, dynamic runtimes, App Engine, and rollback paths.

Put previews, deployments, App Engine URLs, browser tokens, customer attribution, and custom domains behind your own product model.

Build the server-side control plane that dispatches prompts into sandboxes, computers, local devices, and Agent Runs.

Orchestrate MIOSA-managed compute, connected machines, AWS, Google Cloud, and hybrid placement through one resource model.

Give agents a full Linux desktop when they need browsers, screenshots, clicks, uploads, form fills, or human handoff.

What you can build

Build a branded prompt-to-app platform where agents generate full-stack software, stream their work, open live previews, manage versions, and publish production deployments.

Coordinate sandbox agents, computer agents, artifact generators, browser QA, deployment agents, and live UI events.

Add a backend that resolves users, dispatches prompts, streams agent work, stores artifacts, and enforces quota.

Build autonomous company operators, agent departments, persistent virtual devices, miniapps, jobs, approvals, and connected-tool workflows under your own brand.

Give each customer isolated workspaces, branded preview domains, deployment domains, custom domains, browser tokens, and usage attribution.

Turn prompts into published landing pages, intake forms, calculators, content hubs, and campaign sites without exposing MIOSA.

Run apps that need a server process, API routes, background work, environment variables, and persistent release management.

Execute user code in isolated environments, stream stdout and stderr, capture artifacts, and shut work down when finished.

Use Computers for real browser sessions: navigate, click, type, upload files, capture screenshots, and hand control to users.

Bring third-party computer capacity into MIOSA while keeping one API, one product surface, and one user relationship.

Measure sandbox lifecycles, desktop readiness, screenshot/action latency, and task success across agent workflows.

Platform guides

Concepts Core resource model: workspaces, projects, sandboxes, previews, deployments, computers, and attribution.

Authentication API keys, browser-safe tokens, and customer-scoped access patterns.

Deployment domains Preview domains, deployment domains, custom domains, DNS verification, and TLS.

Data and persistence Postgres, storage, Redis, volumes, and generated app state.

Security Secrets, connect accounts, network rules, audit logging, and white-label credentials.

Evaluations OSWorld-style task scoring, desktop readiness, traces, and regression checks for agent workflows.

Benchmarks Current sandbox and desktop timing measurements, with clear labels for sample size and run context.

Provider comparison How MIOSA, native computers, BYOC, and external providers fit different product needs.

Developer surfaces

Surface	Use it when
REST API	You want complete control over sandboxes, files, exec, previews, deployments, computers, domains, tokens, and events.
Backend orchestration	You are building the server-side layer that dispatches prompts into MIOSA devices and streams work back to your UI.
CLI	You want to create, inspect, publish, and debug resources from a terminal.
Python SDK	You are building agent loops, backend orchestration, or data workflows in Python.
TypeScript SDK	You are building Node services, web backends, or product integrations in TypeScript.
Go SDK	You are building backend services that need typed deployment, App Engine, and proof helpers.
MCP server	You want an AI agent to use MIOSA tools through the Model Context Protocol.
Agent Development Kit	You want higher-level agent building blocks on top of the raw sandbox and deployment APIs.

For LLMs

MIOSA publishes machine-readable docs indexes so agents can retrieve current public documentation without scraping the site.

Agent operating guide Authoritative CLI, release, recovery, and rollback behavior for agents and automation.

LLMs index Compact public docs map for agent retrieval.

Full LLM context Expanded public docs corpus for deeper agent context windows.

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.