Production data safety is pulling against the need to restore published applications quickly.
A forward migration protects future publishes from the split, while each production change risks data that founders already rely on.
Who you’d be doing this for
“My customers can book in the preview, then the live app says the field doesn’t exist.”
Axel Larsson · Founder
Runs a customer booking application generated through Replit Agent and published for paying clients.
What is at stake
Published apps are reading older schemas, and founders are seeing live features fail after deployment. You have to weigh rapid recovery against irreversible changes to production data.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- rapid recovery vs production data integrity
- broad containment vs founder publishing continuity
- generated incident analysis vs independently verified evidence
- rollback certainty vs forward migration durability
Why Replit
Replit Agent publishing turns generated applications into live products, so a broken development and production split reaches founders' customers directly.
Written with these in mind
Not your kind of problem? 30 more at Replit, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.