Build a v0-style app

What you’re building: a UI generator. A prompt becomes a rendered page or component, previewed and published to a stable URL.

Primitives you’ll use: Organization, Sandboxes, Agents, Deployments, Custom domains

What you’re building

v0-style tools focus on the interface: turn a prompt into a React/HTML page, render it, and give the user a URL. The output is usually a static site, which is the simplest thing MIOSA can publish.

The loop is short: generate the markup, write it into a sandbox that already has Node, build the static output, show it in a preview, and publish the built directory. Publishing static output needs no run command and no server, so it deploys in one step and stays cheap.

If the user later wants a backend, promote the same workspace to a dynamic deployment with a run command.

What you need on MIOSA

Architecture

Step 1: Create an account and an API key

Install the CLI, sign in, and mint a key for your product. The secret is printed once; store it as an environment variable, never in code.

npm i -g @miosa/cli
miosa login
miosa whoami
miosa api-key create ui-gen-key --preset agent     # prints the secret once
export MIOSA_API_KEY="msk_u_..."

Both SDKs read MIOSA_API_KEY from the environment, so a server or a worker needs nothing else. See API keys for scopes and how to create keys in the console.

Step 2: Create the resources

Step 3: Wire the agent loop

A generated UI is only as good as its edit loop. Keep the workspace and let the user refine with a prompt; each turn writes the file and reruns the build.

Step 4: Preview

A Preview is a throwaway public URL for a port inside the machine. Start the app as a background process so it survives the CLI disconnecting, then expose its port.

Open the exact Preview URL MIOSA returns.

Step 5: Deploy

Publish the machine to an immutable Deployment. Give it the source machine, the path the app lives at inside it, and the command that serves it.

Publishing the same deployment name again creates a new immutable version and keeps the same URL. Roll back with miosa deploy rollback ui-gen --to <version-id>, and inspect a live app with miosa deploy logs ui-gen -n 100. See Publishing and Rollback.

Step 6: Custom domain

Attach a domain your customer owns to the deployment. The platform URL keeps working while DNS propagates.

miosa deploy domain-add ui-gen app.example.com
miosa deploy domains ui-gen          # shows the DNS record and verification target
miosa deploy domain-verify ui-gen <domain-id>

Copy the exact DNS record MIOSA shows into the customer’s DNS provider; for a subdomain it is normally a CNAME. Once verified and TLS is active, MIOSA routes the domain to the deployment’s active version. In code, read the URL from the publish response instead of building it: the SDK method is miosa.deployments.domains.add(deploymentId, { domain }) (TypeScript) or miosa.deployments.domains(deployment_id).add(domain=...) (Python). See Domains.

Costs and limits

Everything bills while it runs: machines (sandboxes and computers) by the second, managed databases while running, and deployments when they serve. Pausing a machine stops compute billing but keeps disk. Set an --idle-timeout or a --ttl so a forgotten machine cannot run forever, and cap spend with rate limits and per-workspace quotas.

• Pricing - plans, the published rate card, and the free Developer grant.
• Sizing and limits - machine sizes and what each costs to run.
• Timeouts and auto-stop - --ttl, --idle-timeout, and pause/resume.

Next steps