Deploying on MIOSA means turning a Sandbox into a stable production URL backed by immutable build artifacts, versioned history, and instant rollback. Once published, the URL never changes — only which version it points at.

The deployment pipeline

Every publish travels the same path:

1. Sandbox — the mutable environment where you (or an agent) write code.
2. Source Snapshot — an immutable tarball of /workspace captured at publish time. The sandbox can keep changing; the snapshot is frozen.
3. Builder VM — a short-lived Firecracker microVM that runs install + build from the snapshot. It exits when the release is stored.
4. Release — the immutable build output. Static: a tarball. Dynamic: a rootfs/OCI image.
5. Deployment Version — the row in history. version_number increases monotonically. Every version is bootable forever.
6. Runtime Instance — for dynamic deployments, a Firecracker microVM booted from the release rootfs. Static releases skip this; MIOSA’s edge serves the files directly.
7. Domain — the route. Managed (auto-TLS) or custom. Points at the active version. Rollback is re-pointing this route — no rebuild.

Static vs Dynamic

Pass kind: "auto" (or runtime_kind: "auto" in Python) and MIOSA inspects the build output to decide. A dist/ with no server entrypoint becomes static; a Procfile or detected start command becomes dynamic.

The deployment object

A Deployment is the stable product object — the thing the world thinks of as “the live app.” It has a name, a slug, an active version, and one or more domains pointing at it.

Project
  └── Deployment ("smile-dental")
        ├── active_version_id ──► Version 17 ──► Release sha:abc...
        ├── Version 16 (archived, still bootable)
        ├── Version 15 (archived, still bootable)
        ├── domains:
        │     ├── smile-dental.miosa.ai   (managed, auto-TLS)
        │     └── smiledental.com         (custom, verified)
        └── data:
              └── postgres:  DATABASE_URL=...

A Deployment URL is stable. New publishes change which version it points at, not the URL itself.

What gets versioned

Rollback works because every release is immutable and stays in storage. Re-point the domain at version 14 and version 14’s release rootfs boots immediately.

Next