You've got a completed build and someone to show it to. This is the shortest chapter in the handbook, because the flow is genuinely small — which is rather the point of it.
The flow
- On the build's card, choose Publish.
- Pick a slug — the yourname in
yourname.buildmidas.com. Taken slugs suggest alternatives. - Confirm. The build goes live in moments; the card shows the URL and the live state, and the site appears in your Published page.
That's the whole thing. No DNS, no accounts elsewhere, no cost.
Details worth knowing
- Server-backed apps publish too. A build with accounts, a database, or multiplayer goes live with its server side hosted and managed — same button. (One live server-backed app per account on the free tier.)
- Republish is per-version. When you iterate, the live site does NOT change until you publish the version you want — preview freely without touching production. Republishing an older version is the rollback.
- Unpublish means unpublish. The URL stops serving; the build stays yours, republishable anytime.
- Public visibility is a separate toggle — published sites can be listed publicly (some end up in the Showcase) or stay link-only.
When you outgrow the subdomain: your own domain over a deploy target, or the app stores via the ship path — the three routes compose, and most serious products end up using more than one.
← All posts