VibeCare · AI app maintenance & support
Monthly maintenance for AI-built and vibe-coded apps.
Your code, looked after by me, for one monthly fee. I fix bugs, keep things up to date, watch for errors and handle the everyday upkeep, so you can get back to building.
If the app is broken or not quite finished, we start with a rescue and move to monthly care once it's in shape.
When I can help
Errors you can't reproduce, and every fix seems to break something else.
Packages are out of date, deploys are stressful, and nobody is checking that things still work.
Payments, email, sign-in, webhooks or an AI provider aren't doing what they used to.
The AI tool got you most of the way. The last part needs someone who can read and fix the code it wrote.
Whether you built it with Cursor, Claude Code, Lovable, Bolt or by hand, how the code was written doesn't matter much to me. What I look at is how the app behaves and how hard it will be to maintain.
Two services
For a broken or unfinished app
Get the app working, and know exactly what changed.
I take a short look first, and we agree on what "fixed" means before I start.
New features, redesigns and rewrites are separate projects. A rescue is about making what you already have work.
For a working app · monthly
Ongoing maintenance for the app you already have.
The monthly fee reserves a set number of hours for your app, so problems are handled by someone who already knows the code.
How the monthly fee works
It's a maintenance subscription. The code and the hosting stay yours. You're paying for my time to look after them, not renting software.
Hours: the fee buys a set number of hours each month. Investigating, fixing, testing, updating, reviewing errors and writing the monthly note all come out of them. We agree priorities first, and I ask before going over.
Replies: within one business day on our agreed working days. That means a first look and a next step, not always a finished fix.
Monitoring: I check your existing error tracking while I'm working on your app. Nobody is watching it overnight, and there's no uptime guarantee.
Cancelling: give at least seven days' notice before the next renewal. Unused hours don't roll over.
Questions
Web apps that real people use. Rails is what I know best. If yours is built on something else, tell me what it is. I'll be honest about whether I'm the right person before you pay for more than a quick look.
No. I explain what I found and what I changed in plain English. You decide what gets done and when it goes live.
Not unless there's a good reason. The aim is to keep what works and fix what doesn't. If a rewrite really is the better option, I'll explain why and quote it separately.
It depends on the app, so I quote after a quick look: a fixed price for a rescue and a monthly fee for care. For an established business app, the Rails maintenance plans list prices.
The code is yours, and you keep control of the repository and hosting. I work in your repository, every change can be reviewed, and I only ask for the access the work needs. Please don't email passwords, production data or API keys.
We agree on that before I start, including whether AI tools can see your code or data. If you'd rather they didn't, just say so.
Running an established business app rather than a side project? Rails maintenance & AI integration support is probably a better fit.
What does it do, what did you build it with, and what's going wrong? I'll tell you whether a rescue or monthly care is the right place to start.
Helpful to include: the app's URL, what you built it with, where it's hosted, the main problem and your timing. I don't need repository access for the first conversation.