Ship without flinching: preview deploys for agent-built apps

The day your app gets its third user, deploys change character. Before, “ship it” meant let’s see. Now it means hopefully the migration doesn’t eat the data while Ana is using the app.

Under one of the most-watched Claude Code tutorials, a commenter asks, word for word: “Is there a way to have a staging environment to test before production?” It’s a great question, because the standard answers are either heavyweight or hand-waving.

What big teams do, and why you shouldn’t

Companies solve this with staging environments: a permanent second copy of everything, CI pipelines that promote builds through it, sometimes blue-green deploys with traffic switching. It works, and it costs a platform team.

A side project doesn’t need any of that machinery. It needs exactly one thing: to see the change running, at a real URL, before anyone else does.

The loop

On Alora that’s a built-in verb. The whole exchange with your agent looks like this:

you:    change the pricing table — but let me see it before it’s live
agent:  alora preview
        → https://myapp--preview.alora.page   (production untouched)
you:    …clicks around on the phone… looks right. promote it.
agent:  alora promote
        → https://myapp.alora.page   ✓ the preview is now live

What’s happening underneath:

• preview deploys the candidate as a new version that isn’t activated, served at yourproject--preview.alora.page. Production keeps running the old version the whole time.
• The preview obeys the same privacy rules as the project. Apps are born private on Alora, so the preview URL asks visitors to log in too — it’s a rehearsal, not a leak.
• promote makes that version live. Not happy? alora preview stop discards it, or just walk away — previews expire on their own after 24 hours.

Preview data is ephemeral on purpose

The scariest deploys aren’t visual changes — they’re migrations. The ones that rewrite the database.

That’s why the preview gets a clean, throwaway data directory instead of a window into production’s. Your migration runs for real, against data it can’t hurt. If it’s wrong, you’ve learned that on a copy that evaporates — not on Ana’s records. A staging that shares production data would make the riskiest tests the most dangerous ones to run; this makes them free.

The fine print, kept short

A preview is billed like any app — cents per active hour — sleeps when idle, and disappears after a day. It works before your first production deploy too, so “show me before anything goes live” works on day one. And because it’s in the agent docs, your agent already knows the whole flow: just ask for a preview.

Shipping to real users should feel like pressing a button you’ve already tested. Now it is.