# Build on MIOSA

Understand the building blocks. Run code in a sandbox, inspect a preview, and publish a version you can return to.

## Build on MIOSA

[Quickstart](/docs/quickstart) · [API reference](/docs/api)

## The building blocks

- [Sandbox to deployment](/docs/quickstart): A complete first workflow: create an environment, write an application, inspect it, and publish a version with a clear rollback path.
- [Install the CLI or SDK](/docs/installation): Pick the interface that matches your workflow, configure credentials once, and verify the connection before making changes.
- [The product model](/docs/product-model): A small resource vocabulary makes the system easier to understand. Give every resource a clear owner, lifetime and purpose.
- [Projects](/docs/projects): Group the resources for one application without hiding who owns them.
- [Services](/docs/services): Choose a web process, a worker or a scheduled job according to the work it does.
- [Deployments and rollback](/docs/deployments): Publish a specific version, verify that version, and retain a clear route to the last known good release.
- [Sandboxes](/docs/sandboxes): An isolated place for code and tools. Create it for a task, keep the state you need, and stop it when the task is finished.
- [Snapshots and persistence](/docs/snapshots): Save the state you intend to recover, understand what the snapshot includes, and verify the restored instance.
- [Computers](/docs/computers): Use a desktop when the task depends on visual applications, browser state or direct interaction.
- [Data and bindings](/docs/data): Choose storage by the shape and lifetime of the data, then connect it explicitly to the application.
- [Domains and previews](/docs/networking): Understand what a temporary preview exposes and what a stable domain promises to its users.
- [Models, harnesses and tools](/docs/agents): An agent is easier to understand when its reasoning, execution loop and machine are separate concepts.
- [CLI workflow](/docs/cli): Use explicit resources and structured output to make terminal workflows readable and repeatable.
- [SDKs](/docs/sdks): Use the same resource model from application code. Pick a language and keep identifiers and failures explicit.
- [MCP](/docs/mcp): Expose defined capabilities to an agent client without making the client guess how to call your service.
- [API fundamentals](/docs/api-reference): Read the resource contract, send an explicit request, and inspect the exact response before taking the next action.
- [Permissions and secrets](/docs/security): Make the ownership boundary visible, keep credentials out of browser bundles, and preserve useful failures.
- [Make this documentation your own](/docs/customization): Replace the content, adjust the tokens, and connect only the services you need. The reading experience works on its own.
- [Changelog](/docs/changelog): Changes to this local documentation reconstruction.

## Learn by doing

[Learn and earn](/docs/learn/earn) · [Glossary](/docs/glossary) · [Interactive labs](/docs/learn/games)

## Machine-readable documentation

[Index](/llms.txt) · [Full context](/llms-full.txt)