Core Concepts

MIOSA gives developers and agents a safe development loop without making production mutable. You work in a Sandbox, inspect the result through a Preview, and publish a frozen candidate Release. After MIOSA verifies that candidate, promotion moves the Deployment’s stable URL to the new Version.

If you read only one line, remember this:

Sandbox (mutable) → Preview → Publish → Release (immutable) → Verify → Promote → Deployment (stable URL).

The old Version remains available for rollback. Databases, storage, secrets, and domains remain attached to the Deployment instead of being copied into each release.

This page is the resource model: what the MIOSA resources are and how they relate. For the API protocol - authentication, token types, idempotency, rate limits, errors, and events - see API fundamentals.

Pick what you need

You want toRead
The ownership chain and the development and production resourcesResource model
How a publish becomes a live releaseThe publish pipeline
Databases, storage, and bindingsData and bindings
The desktop productComputers
White-label tenancy and attributionTenancy
Browser tokens for previews and sharesPreview and share tokens
Tenant preview domain and brandingTenant configuration

New to the platform vocabulary? Keep the MIOSA Glossary open while you follow the resource and publishing flows below.

Next

Deep dives

Computers (desktop product) now lives in Computers.

Tenant preview domain now lives in Tenant configuration.

Was this page helpful?