Come Back From Vacation to a Deleted Database: How Free Hosts Handle Idle Projects
Photo: President (1981-1989 : Reagan). White House Photographic Office. 1981-1989, Public domain, via Wikimedia Commons
Picture this: you spend three weekends building a recipe tracker for your family's annual Fourth of July cookout. It works. Your cousins love it. Then life happens — work gets busy, football season starts, and you don't log in for two months. When you finally come back, the URL serves a sad error page. Your database? Gone. Your host's excuse? It's right there in section 14.3 of the terms of service you scrolled past at 1 AM.
We've all been burned by this or know someone who has. So this week at FreeServerHost, we went through the inactivity and resource-reclamation policies of the free tiers developers actually use, and mapped out exactly which ones will sleep-wipe your project while you're at the lake house.
The Three Flavors of 'Idle'
Not all inactivity policies are created equal. Broadly, free hosts fall into three camps:
The hibernators. Some platforms don't delete anything — they just shut your app down and spin it back up when traffic arrives. You eat a slow cold start (which we've covered before in our cold start showdown), but your data is intact. This is annoying, not catastrophic.
The soft reapers. These hosts send a warning email — sometimes — and then suspend or delete your project after 30 to 60 days of no logins, no deployments, or no inbound requests. Render, for example, suspends free services after extended inactivity. The grace period exists, but only if you actually read the emails hitting your spam folder.
The hard reapers. A few database-as-a-service providers are the strictest of all. Mongo Atlas's free tier deletes clusters after a period of inactivity if you don't respond to their outreach. Supabase pauses free projects after a week of inactivity — pausable, but you have to actively restore them. Miss the restoration window and things can get ugly.
The pattern here: infrastructure-style hosts tend to be more forgiving than database providers, because storage costs them real money whether you visit or not.
What Counts as 'Active'? (It's Probably Not What You Think)
Here's the trap most hobbyists fall into: they assume visitors count as activity. Often they don't.
Some hosts define activity as dashboard logins. Others want deployments. A few measure outbound bandwidth or API requests. And some — the sneaky ones — require any of those thresholds to be met within a rolling window, meaning a burst of traffic in week one does nothing for you in week seven.
Read your host's definition carefully. 'No inbound requests for 60 days' is very different from 'no logins for 60 days.' The first one, a cron job can fix. The second one, only you can.
The Survival Checklist for Dormant Side Projects
If you've got a project you want to come back to — not just abandon — here's the routine we recommend:
-
Automate a heartbeat. A free cron service (cron-job.org, GitHub Actions scheduled workflows, or UptimeRobot's free tier) pinging your app every few days keeps request-based reapers at bay. GitHub Actions is the workhorse here — a five-line YAML file and your app gets a poke every 48 hours.
-
Log in quarterly, calendar it. A recurring Google Calendar event titled 'Keep the recipe app alive' feels dumb until it saves you a weekend of rebuilding. Fifteen seconds of dashboard login defeats login-based policies.
-
Back up your data off-platform. This is the big one. Even if your host never deletes anything, free tiers get deprecated, companies get acquired, and regions go down. A monthly
pg_dumpor a JSON export pushed to a private GitHub repo costs nothing and means the worst case is a redeploy, not a rebuild. -
Keep the warning email address alive. Half of these deletions happen because the signup email was a burner address on a domain that expired. Use an inbox you actually check.
-
Know your redeploy time. If you've got your app in version control with an infrastructure-as-code setup or even just a good README, deletion becomes an inconvenience instead of a funeral. Docker configs and a
docker-compose.ymlin the repo mean you can be back up anywhere in under an hour.
Should You Just Pay Already?
Honest answer: sometimes. If a project has real users and real data you'd genuinely mourn, a $5/month VPS or a paid tier with no reaper clause is cheaper than your time. Free tiers are fantastic for experiments, portfolios, and things you'd rebuild anyway.
But for the long tail of side projects you're not ready to kill and not ready to fund? A heartbeat ping, a quarterly login, and an off-site backup will get you through almost every inactivity policy out there. Set it up once, forget about it, and enjoy your vacation. Your app will still be there when you get back — probably.
Have a horror story about a host that nuked your project? We collect them. Drop it in the comments — the best ones make it into our next terms-of-service deep dive.