Docker Host

Docker Host is MIOSA’s dedicated workspace host model for customers that need many small apps, funnels, lead magnets, APIs, or client sites without creating a new production VM for every deployment. It is the recommended production path for generated apps that should run 24/7 inside a workspace. MIOSA keeps routing, domains, and attribution as the source of truth, and the host supplies the execution capacity.

1. Ensure the workspace host

miosa api POST /docker-deploy/hosts/ensure -d '{"workspace_id": "<workspace-id>"}'
miosa api GET /docker-deploy/hosts?workspace_id=<workspace-id>

The host moves from provisioning to bootstrapping to active. Publishes wait until it is active.

2. Publish an app

miosa deploy create --from-sandbox <sandbox-id> 
  --name my-app 
  --dir /workspace 
  --run-command "npm run start" 
  --port 3000 
  --type docker_deploy 
  --wait 
  --wait-timeout 900s 
  --json

To publish a new version without changing the deployment URL, reuse the same --name.

3. Prove it

miosa deploy get <deployment-id> --json

A Docker Host deployment is live only when the host is active, the app target is running, the container route is reachable, and a probe to public_url succeeds.

Pick what you need

You want to	Start here
Understand host lifecycle and proof	Docker Hosts
Start from a curated app shape	Docker Host templates
Standard static or dynamic publish	Deploy overview
Attach a managed or custom domain	Deployment Domains
Compare standard and Docker Host targets	The deployment model

The always-on workspace host: lifecycle states, publishing flow, proof, and recovery.

Curated app shapes with Dockerfile, Compose, command, and port defaults.

Freeze a sandbox into an immutable deployment version.

Attach managed and custom domains to deployments.

Configure organization branding and domain behavior.

Map MIOSA resources to your users, workspaces, and projects.