You launched your app with Lovable, Bolt, Cursor or Replit. It works. Now you wonder what "maintenance" means when you are not changing anything. This post gives you a routine: about an hour a month, a bit more each quarter, and a few jobs once a year. The vendor facts come from Node.js, Netlify, Vercel and Supabase docs, checked in November 2026.
What breaks when nobody looks
An app can rot without a single code change. The Node.js version it runs on reaches end of life. A package gets a security alert. A free plan pauses an idle project. The card on file expires. A domain lapses. Sign-up emails start landing in spam. Someone who helped you last year still has access to everything.
Short answer: every month, spend an hour on alerts, errors, bills, emails and a run through your main flow. Every quarter, restore a backup, review who has access and check your runtime versions. Every year, check domain renewal, the card on file and your privacy page. Write down what you checked, and test every update on a copy first.
Monthly, about an hour
- Dependency and security alerts. Open the Security tab of your GitHub repository. Handle the alerts that affect production first. The details are in the post on GitHub security alerts.
- Uptime and errors. Look at what went wrong this month: downtime, error alerts, failed payments. If you have no alerts set up, start with uptime monitoring and error alerts.
- Costs. Open each bill and each usage page: host, database, email, domain. Compare with last month. How to avoid a surprise bill and what a small web app costs to run explain what to look for.
- Sign-up and password emails. Sign up with a fresh address, then ask for a password reset. Do both mails arrive, and not in spam? If not, read the SPF, DKIM and DMARC post.
- Run the main flow yourself. Sign up, do the core action, and pay with a test card. Do this on a staging copy, not on live data: how to set up a staging copy.
Quarterly
Restore a backup once
"Backups are on" is not the same as "I can get my data back." Once a quarter, restore a backup into a separate test project and open the app against it. If it fails, you want to learn that now. The backups post shows how on Supabase, Neon and Firebase.
Review who has access
List who can log in to your host, database, domain, GitHub and email service. Remove former helpers and check that two-factor login is on. See how to lock down the accounts that run your app. If you are handing the app to a new developer, this access handover post helps.
Check your runtime versions
This is the job people skip, and it is the one that bites. Node.js is the runtime behind most of these apps, in builds and in server functions. Each major version has a life cycle. The Node.js end-of-life page says: "Major versions of Node.js are released, patched, and designated End-Of-Life on a predictable schedule." And: "When a version reaches End-Of-Life, it means that it will no longer receive updates, including security patches."
Where do your versions stand? The Node.js releases page marks Node.js 18 and 20 as EOL, and Node.js 22 as LTS. The same page says: "Production applications should only use Active LTS or Maintenance LTS releases." I did not find an end-of-life date for each version on those pages, so look at the table yourself when you read this. It changes over time.
Netlify. The Netlify dependency docs say a build's Node.js version "is initially determined by the default version preinstalled on the site's selected build image", and that Netlify pins the site to that version "so your builds won't change even if the build image's defaults change." So a site you launched long ago may still build on an old Node.js. To change it, use Project configuration, Developer settings, Continuous deployment, Dependency management, set a NODE_VERSION environment variable, or add a .node-version or .nvmrc file. The docs note that those last three override the setting in the UI. For functions they say: "Typically, the functions runtime Node.js version automatically matches the version used for the build." I found nothing on that page about what happens to a version that is deprecated.
Vercel. The Vercel Node.js versions page says: "By default, a new project uses the latest Node.js LTS version available on Vercel." It lists the available versions as 26.x, 24.x and 22.x, and says only major versions are available. You choose the version in Settings, Build and Deployment, Node.js Version, or in package.json under engines. To check, run node -v in the Build Command, or log process.version inside a function. What happens to old versions? Vercel's announcement about Node.js 20 says it is being deprecated "for Builds and Functions on October 1, 2026". After that date, Node.js 20 is disabled in Project Settings, and projects using it for Functions "will display an error when a new deployment is created." Existing deployments are not affected: "Invocations to already-deployed functions will continue to work normally." So an old app keeps running, then fails the day you try to ship a fix. That is a bad moment to find out.
Database side. Supabase's upgrade docs say: "Your project is taken offline and the Dashboard shows the upgrade status." They also say to plan for the database "to be unavailable" during the upgrade, and to make sure "a recent backup is in the Backups page" first. They do not give end-of-life dates for Postgres versions, so I won't either. If you upgrade, treat it like any change: backup first, off-peak, and test the app afterwards.
When you change a runtime version, do it on a branch and a preview deploy, not on live. Build, click the main flow, then merge.
Yearly
- Domain: check the renewal date and that auto-renew is on at your registrar.
- Card on file: check the card at the registrar and at each host. An expired card can take an app or a domain down without a single code change.
- TLS certificates: on Netlify and Vercel these renew by themselves, but still check once a year that they did. Netlify's HTTPS docs say: "Certificates are generated and renewed automatically as needed." The exception: if you uploaded a custom certificate, "Netlify cannot do this automatically." Vercel's SSL docs say it "automatically attempts to renew the SSL certificates it issues for your custom domains 14 to 30 days before they expire", and that "certificate renewal is separate from renewing the domain's registration." So the certificate renewing does not renew your domain name.
- Privacy page and cookies: does the text still match what the app does? Did you add an analytics tool or a new form since? See the GDPR checklist for a small app and analytics and cookies.
Free plans that pause
Free plans can stop an app nobody opened for a while. Supabase pauses inactive free projects: what to do when your project is paused. If your app has real users, a pause is an outage. Check the plan of every service the app depends on, and note which ones are free.
Keep a maintenance log
One document or file is enough. One line per check: the date, what you checked, what you changed. It takes a minute and pays back twice. You stop asking yourself "did I do the backup test?" And when you hire someone later, they see the history at once, which makes a handover much easier.
What to hand to your AI tool, and what you check
AI tools are good at the reading and the typing. Example prompts:
- "List every dependency with a known vulnerability and the smallest safe update. Show me the diff before you apply it."
- "Which Node.js version does this project build and run on? Where is it set:
package.json,.nvmrc, or the host settings?" - "Read the build log of the last deploy and list every warning about deprecated packages or versions."
- "Write a one-page maintenance checklist for this project from its files: host, database, email service, domain."
Always test an update on a staging copy or a preview before it goes live. Check yourself that the diff is small, the build passes, the main flow works, and the AI did not remove a feature to make a warning disappear. Bills, access and backup restores are for you to check. A tool cannot see your registrar or your card.
Checklist
Monthly
- Security alerts: production ones first.
- Downtime and errors from the past month.
- Every bill and usage page, compared with last month.
- Sign-up and password reset emails arrive, not in spam.
- Main flow run on staging.
- One line in the maintenance log.
Quarterly
- Backup restored into a test project.
- Access list reviewed, former helpers removed, 2FA on.
- Node.js version checked on host and locally, against the Node.js releases page.
- Free plans noted.
Yearly
- Domain renewal date and auto-renew.
- Card on file at registrar and hosts.
- TLS certificate renewed.
- Privacy page and cookie setup match the app.
Want someone to keep your app healthy?
I finish, fix and manage apps built with Lovable, Bolt, Cursor or Replit. Send me the details and I'll reply within 24 hours.