Who maintains your vibe-coded apps?
AI made it easy to build a tool in an afternoon. An internal dashboard, a client portal, a small app for one workflow. Plenty of founders have five of them now.
Building them was the fun part. Keeping them running is a different job. A package breaks, an API changes, a user finds a bug, and you’re the only one who can fix it, in code you didn’t write.
A lot of founders would rather pay someone monthly to look after the code.
What maintaining a vibe-coded app means
Maintenance is everything that keeps an app working after it ships. Most of it is invisible until something breaks.
- Package and security updates
- Fixes when an API or an AI model changes
- Bugs your users find
- Small changes and new features
- Hosting, database and backup checks
- Errors caught before users report them
Vibe-coded apps need more of it than most. Nobody knows the code well, the AI picked whichever packages it liked, and each tool was built a little differently. Every fix starts with figuring out how that app works.
Your options
Do it yourself with AI
This works for a while. Your AI tool can update packages and fix bugs. But every fix takes your time, the tool forgets how the app works between sessions, and quick fixes pile up into the mess that makes an app hard to change. The guide to fixing a vibe-coded app covers that part.
A freelancer for each fix
It’s cheap per task. But every fix starts with someone learning the code again, and good freelancers are often busy on the day something breaks.
An agency retainer
You get a team and a contract. You also pay for account managers, and the person who knows your code may change every few months.
A monthly developer subscription
One person who knows all your apps, works from a backlog and charges a flat monthly fee. It’s the closest thing to what founders mean when they say they want someone else to maintain the code.
Which one fits depends on what the tools are worth to you. For side projects, doing it yourself is fine. For tools your business or your clients depend on, someone should own them.
What a good maintainer does first
1. Put every app in one place
Every app goes into your own GitHub, one repo each, with access you control. Apps that live only inside Lovable, Bolt or Replit get exported first.
2. Write down what each app does
Where it’s hosted, what it costs each month, which services and keys it uses, and who uses it. Most founders are surprised by at least one app they forgot was still running.
3. Close the security gaps
AI-built apps often ship with exposed keys or a database anyone can read. The vibe-coded app checklist covers what to check.
4. Set up monitoring
Error tracking and uptime checks on every app, so problems show up in a dashboard before they show up in your inbox.
5. Automate the updates
A tool like Dependabot or Renovate opens a pull request whenever a package has an update. Someone reviews it, tests the app and merges it, so updates stop piling up.
6. Retire what nobody uses
Fewer apps means less to maintain. Two tools that do almost the same thing can usually become one.
After that, maintenance becomes routine. Updates go out every week, bugs get fixed as they come in, and new features land in code someone understands.
What it costs to maintain an app
Running a small app is usually cheap. Hosting and databases have free tiers or small monthly plans, and AI API costs grow with use.
The real cost is time. Somebody has to read the error, find the cause and ship the fix, and with five apps that happens every week. The question is whether that somebody is you.
A few habits make the job easier for anyone who does it. Build every tool on the same stack, share login and UI components between them, and add an AGENTS.md file to each repo so AI tools follow the same rules.
How Frontend Supply works
Frontend Supply is a monthly frontend subscription for startups, and vibe-coded apps are welcome. I can take over all your tools at once. I move them into your GitHub, keep them updated and fixed, and build what you need next. I work in the code, and I take on the backend side when you need it.
It’s one senior frontend engineer and a set of AI agents. I lead them like a team. I plan the work, set the architecture and component APIs, and correct them when they cut corners or use bad patterns. They work in parallel, so your products get about 12 hours of work a day.
It’s $5,000 a month, flat, with no contract. The price covers the work, not a number of apps. For side projects, that’s more than you need. It makes sense when your business runs on these tools. You can start with a one-week trial for $1,250. More about me.
When you’d rather build the next thing than keep fixing the last five, I make sure they keep running.
FAQ
How much does it cost to maintain an app?
Hosting a small app is often free or close to it. Most of the cost is the time it takes to keep it updated and fixed, whether that’s your time or someone else’s.
Can someone maintain an app they didn’t build?
Yes. The first days go into reading the code and mapping how it works. After that, it’s like any other codebase.
Do I have to stop using Lovable or Cursor?
No. Keep using them for new ideas. Once an app matters, move it to GitHub so every change can be reviewed and undone. There’s more on that in hiring a developer for a Lovable app.
What happens if I cancel?
Everything stays in your GitHub, and you own all of the code. My Slack DMs stay open for advice after you cancel, at no charge.