TABLE OF CONTENTS
item

AI Summary
Redeploy 2.0 makes updating a live app on livemy.app safe and reversible. The redeploy dialog now asks what you want to ship: restore the original code, pull the latest changes from your GitHub branch, or upload a new archive. A checkbox creates an automatic restore point right before the update, labeled “Automatic backup”, and it does not use a slot in your versions quota, so one click rolls everything back if the new version misbehaves. Apps now start on their own after a restart or a restore from backup, and if one is down the dashboard shows an honest “App down” badge with a redeploy button. A deploy is only marked successful when the live URL actually responds. The release also ships full documentation at docs.livemy.app: quick start, core concepts, custom domains, AI-assisted fixes, MCP and SSH for developers.
Ask anyone who built an app with AI what the scariest moment is. It’s not the first deploy. The first deploy is exciting. The scary part comes later, when your app is live, real people are using it, and you need to change something. What if the update breaks the thing that already works?
We ship updates to livemy.app almost every week, and this release is entirely about that moment. Here’s what’s new.
Redeploy 2.0: you choose exactly what goes live
Until now, “Redeploy” meant one thing: run the same deploy again. Now the redeploy dialog asks what you actually want to do:
Restore the original. Deploy the exact code that was deployed before. A clean reset when you just want the app back the way it was.
Update from your branch. Pull the latest changes from your GitHub repository and deploy those. livemy.app still never redeploys behind your back: you pick the moment, and it picks up your newest code.
Upload a new archive. For projects deployed from a ZIP, upload the new version right in the dialog.
Three situations, three answers, one button.
A restore point before every update
This is the part we’re most excited about. In the redeploy dialog, tick one checkbox and livemy.app takes a snapshot of your project right before the new version goes out.
If the update misbehaves, open your versions list and roll back to the snapshot. It’s labeled “Automatic backup” so you always know which one it is, and it doesn’t use up a slot in your versions quota. While it’s working, your project card tells you exactly what’s happening: “Creating restore point…” during the snapshot, “Restoring…” on the way back.
Think of it as an undo button for deploys. You shouldn’t need a plan B to press Redeploy. Now the platform has one built in.
Your app survives restarts and restores
A quieter change, but an important one. Previously, in some cases, an app restored from a backup could come back with everything in place except the app itself running. Now livemy.app locks in autostart at deploy time, so your project comes back up on its own after a restart or a restore. It just stands back up, the way it was.
And if an app is down anyway (for example, an older project deployed before this fix), the dashboard says so honestly: the project card shows an “App down” badge with a Redeploy button right next to it. One click and it’s back.
A deploy only counts as successful if your site actually answers
Deploy status is now confirmed by a real check of your live URL. If the page doesn’t respond properly, the deploy isn’t marked as successful. Fewer green checkmarks with a broken site hiding behind them. Honest status, every time.
New: documentation at docs.livemy.app
livemy.app now has full documentation at docs.livemy.app, and it’s one click away from the dashboard (account menu → Documentation).
What’s inside:
Quick start. Deploy your first app in a couple of minutes: connect a public GitHub repository, upload a ZIP, or pick a demo template.
Core concepts. Projects, deploys, plans, and the AI agent, explained in plain language.
Guides. Fixing and updating your app through the AI assistant without ever touching a server, connecting your own domain, and tools for developers: MCP from your IDE and SSH access.
From your first deploy to a custom domain, you can now figure out the whole platform without leaving it.
The theme of this release: trust
Every item on this list answers the same question: “can I touch my live app without being afraid?” Choose what you redeploy. Get a restore point before you do. Know your app will stand back up. See a deploy status that tells the truth. And when in doubt, read the docs.
Your app is live and people are using it. Updating it should feel like a normal move, not a risk. That’s the release.
→ Open your dashboard and try Redeploy 2.0 on your next update.
FAQ
What is a restore point?
A snapshot of your project that livemy.app creates automatically right before a redeploy, if you tick the checkbox in the redeploy dialog. If anything goes wrong with the new version, you restore it from your versions list.
Does the automatic backup use up my version slots?
No. The pre-redeploy snapshot is labeled “Automatic backup” and doesn’t count against your versions quota.
Does livemy.app redeploy automatically when I push to GitHub?
No, and that’s by design. Redeploy is always your decision: one click in the dashboard, or a trigger through MCP. The new “update from your branch” option pulls your latest code at the moment you choose to redeploy.
Where do I find the documentation?
At docs.livemy.app, or from the dashboard: account menu → Documentation.

Dmytro Chervonyi
,
Co-founder & CMO, livemy.app
Co-founder & CMO at livemy.app. 12 years as a CMO scaling SaaS from $0 to $10M+ ARR across marketing, sales, and infra products and tools. Now building the missing step between AI-built code and a live URL — for non-developers who’d rather ship than learn DevOps.
