---
title: "Core Concepts"
description: "The canonical MIOSA product model, from mutable sandboxes to immutable releases, stable deployments, persistent data, and customer-owned infrastructure."
last_updated: 2026-10-11
url: https://miosa.ai/docs/concepts
---

# 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.

> **Note: The central boundary**
>
> Changing a Sandbox changes development state.
> It does not change production.
> Production changes only when an exact immutable candidate is promoted.

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](https://miosa.ai/docs/fundamentals.md).

## Pick what you need

| You want to | Read |
|---|---|
| The ownership chain and the development and production resources | [Resource model](https://miosa.ai/docs/concepts/resource-model.md) |
| How a publish becomes a live release | [The publish pipeline](https://miosa.ai/docs/concepts/publish-pipeline.md) |
| Databases, storage, and bindings | [Data and bindings](https://miosa.ai/docs/concepts/data-and-bindings.md) |
| The desktop product | [Computers](https://miosa.ai/docs/concepts/computers-desktop.md) |
| White-label tenancy and attribution | [Tenancy](https://miosa.ai/docs/concepts/tenancy.md) |
| Browser tokens for previews and shares | [Preview and share tokens](https://miosa.ai/docs/concepts/tokens.md) |
| Tenant preview domain and branding | [Tenant configuration](https://miosa.ai/docs/concepts/tenant-config.md) |

New to the platform vocabulary?
Keep the [MIOSA Glossary](https://miosa.ai/docs/glossary.md) open while you follow the resource and publishing flows below.

## Next

- [Resource model](https://miosa.ai/docs/concepts/resource-model.md): The ownership chain, Sandboxes, and Previews - the mutable side of the platform.
- [The publish pipeline](https://miosa.ai/docs/concepts/publish-pipeline.md): Builder, Release, Runtime Instance, Domain, Deployment, and Version: how source becomes a live release.
- [Data and bindings](https://miosa.ai/docs/concepts/data-and-bindings.md): Postgres, Redis, object storage, volumes, auth, and how they attach to a Deployment.
- [Computers](https://miosa.ai/docs/concepts/computers-desktop.md): The cloud desktop product, and the difference between a Computer and a Sandbox.
- [Tenancy](https://miosa.ai/docs/concepts/tenancy.md): White-label tenancy and external attribution for platforms built on MIOSA.
- [Tokens](https://miosa.ai/docs/concepts/tokens.md): Preview tokens and share tokens for browser access to a sandbox preview.
- [Tenant configuration](https://miosa.ai/docs/concepts/tenant-config.md): Tenant preview domain and tenant branding.

## Deep dives

**Computers (desktop product)** now lives in [Computers](https://miosa.ai/docs/concepts/computers-desktop.md).

**Tenant preview domain** now lives in [Tenant configuration](https://miosa.ai/docs/concepts/tenant-config.md).