SOMA and runtimes (early access)

Short answers on the runtime you boot a sandbox on.

SOMA (Secure Optimized Machine Architecture) is MIOSA’s own open-source Rust VMM on Linux KVM, giving each sandbox one hardware-isolated VM with its own kernel. See SOMA.

No. Firecracker (standard) is the default; SOMA is early access and enabled per organization. See Choosing a runtime.

Pass runtime_profile: "standard" | "soma" | "auto" when creating a sandbox, from the REST API, the SDKs (runtime), the CLI (miosa create --runtime), or the console. An invalid value returns INVALID_SANDBOX_RUNTIME_PROFILE; there is no silent fallback. GET /api/v1/sandboxes/runtimes lists the runtimes your organization can select. See Choosing a runtime.

miosa create --runtime soma --size xs

Email support@miosa.ai with the subject SOMA early access: followed by your organization name. See SOMA.

Sandboxes, previews, publishing, data, and white-label are generally available. Computers, dynamic deployments, App Engine, and tenant deployment domains are in partner preview; GPU-backed sandboxes are not productized and remain on the roadmap. See Availability and roadmap.

Was this page helpful?