Has anyone found a good solution for keeping vibe-coded apps stable after launch?
by•
Built my app with Lovable a few months ago. Launch went fine but since then I've had three separate production issues; auth breaking, database timeouts, a webhook that silently fails. Each one took me days to figure out and I have zero engineering background.
Curious what others are doing. Are you just patching it yourself, hiring freelancers each time, or has anyone found something more ongoing? I've been wondering if a monthly retainer for this kind of support would actually be worth it or if that's just me.
256 views
Replies
the pattern you are describing is not a stability problem, it is a missing operational layer. generated code ships without the boring scaffolding a human engineer adds by reflex: idempotency keys on webhooks, retry budgets, alerting on silent failures, a runbook for the three things that will break first. lovable gave you the app. nobody gave you the on-call playbook. a retainer can work, but only if the person writes that playbook in week one rather than firefighting per incident. otherwise you are paying senior rates for someone to rediscover your own system every time it breaks.
This thread is exactly what I've been researching. I'm a full-stack dev, and I keep seeing the same story: launch goes great, then week 2 brings the "random production issue every week" phase and Sentry/Datadog are way too technical to help.
Genuine question for everyone here: when something breaks in your app today, what do you actually do first? (Ask the AI? Panic-Google? DM a dev friend?)