Glossary

Rollback

Restoring a previous working version of your app after a change goes wrong.

Definition

Rollback means putting your app back to an earlier, known-good version after a bad deploy or edit. Instead of frantically patching a broken release, you restore the last version that worked and then fix forward when you are ready. It is the safety net that makes frequent AI-driven changes acceptable for real internal tools.

Why it matters

AI assistants can break something while trying to help. A prompt that “just tweaks the form” might wipe a calculation or change who can see a page. For finance and ops tools, downtime or wrong numbers hurt. Rollback lets you host and update boldly: share the app with the team, keep iterating, and undo a mistake in minutes instead of rebuilding from memory.

How Croft fits

Croft includes one-click rollback on deploys so a bad AI change does not strand your team. Combined with continuous encrypted off-site backups and nightly snapshots of app data, you can restore the app experience and the information it holds. That is part of private hosting for vibe-coded apps, not an add-on you wire yourself. See Under the hood and Security.

Keep reading

FAQ

Frequently asked questions

What does rollback mean for an app?

It means restoring a previous deploy so the app behaves like it did before the bad change.

Is rollback the same as a backup?

Related but not the same. Rollback usually restores the app version you deployed. Backups protect the data the app stores. You often want both.

Why do AI-built apps need rollback?

Because changes arrive quickly from prompts. Rollback makes those changes reversible when something important breaks.

Stake out your croft.

Your team's first app could be live before lunch.

Get your croft

7 days free, no card to start. From $24/month - cancel anytime and take everything with you.