Changes and versions

Change your app with confidence. Nothing goes live by accident.

Every change is saved, tried on a private test copy, and only reaches your users when you say so. If something isn't right, going back is one sentence.

How a change reaches your users

Ask, try, then decide.

01You ask Claude"Add a phone number to the booking form, then put it on &Deploy."

02It's savedThe change becomes version 4. Version 3 is still there, untouched.

03It's checkedWe check it for security problems before it goes anywhere.

04You try itIt appears on your private test copy, with its own separate information.

05You decideWhen you're happy, say "put it live". Until then, your users see version 3.

Your test copy

A safe place to try things.

Every app has two copies. The test copy is just for you and anyone you share the link with. The live copy is what your users see. They keep their information completely separate, so testing never touches real customers or real data.

Test copyLive app

Who sees itYou, and anyone you share it withYour users

Its informationSeparate, for testingYour real information

When it changesEvery time Claude saves a changeOnly when you say so

Before changesChecked for security problemsChecked, and backed up first if stored information changes

Going live

Three safety nets before your users see a change.

Only when you say so

Tell Claude "put it live", or press the button in your dashboard. Claude can't do it on its own, and when you connect it you choose whether it's allowed to at all.

Held back if something's unsafe

If a change would leave information open to strangers, it can't go live until it's fixed. You'll get a plain-English explanation, and Claude can fix it for you.

Backed up before it changes

If an update changes how your information is stored, we take a backup first. Visitors switch to the new version all at once, never halfway.

Going back

Changed your mind? Just ask.

Every version is kept, along with what was asked for and who asked. If the newest one isn't right, say "bring back the previous version" and Claude puts it back live.

Every version saved, never overwritten See what changed and who asked for it Go back with one sentence to Claude

VersionWhat changedTestingLive

v4 Booking form asks for a phone number Yes —

v3 Added the team calendar — Live

v2 Sign-in with Google — —

v1 First version — —

Technical details for your IT team

Version control: Each version is a full snapshot committed to a private Git repository (self-hosted Gitea) on its own branch with a pull request; promotion to production merges it.
Environments: Dev and production per app, each with its own Postgres database, signing keys, API keys and secrets.
Releases: Static releases are uploaded to an immutable prefix, then routing switches atomically; the last 5 releases are retained.
Schema changes: Supabase-style SQL migrations, applied once per environment in order, each in its own transaction; edited migrations are refused. An on-demand backup is taken before production migrations.
Provenance: Each version stores the conversation prompts that produced it, a dependency vulnerability scan and its deploy log.

Your app is one message away from being online.

Connect Claude Create your account