Render free tier cold starts: why your app sleeps and how to avoid it

Because it was asleep. Render's docs say: “Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic.” The next HTTP request or new WebSocket connection starts it again, and “this process takes about one minute.” Browsers see a loading page while that happens.

Inbound traffic means HTTP requests and WebSocket messages on existing connections. A webhook from Stripe or a Telegram bot waiting for messages also hits that cold start if nothing else has called the service in the last 15 minutes.

The sleep is the limit people notice first. These are the others, from Render's free tier docs:

• 750 free instance hours per workspace per month. A free service uses hours while it runs. When they run out, Render suspends all your free services until the next month.
• Free Postgres expires after 30 days. You get a 14-day grace period to upgrade, then the database and its data are deleted. Storage is 1 GB, and you can have one free database per workspace.
• Free Key Value (Redis) doesn't persist to disk. A restart wipes its data.
• Web services only. Background workers, cron jobs and private services have no free instance type.
• 512 MB of RAM and 0.1 CPU, no persistent disks, and no outbound SMTP on ports 25, 465 or 587.

Render is clear about the purpose: free instances are for testing and hobby projects, and its docs say “Do not use them for production applications.”

Four options, from most to least reliable:

1. Upgrade the service. Spinning down is a free-instance behavior. Render's cheapest paid instance, Starter, is $7 a month with 512 MB of RAM and 0.5 CPU.
2. Ping it on a schedule. An uptime monitor that requests the service every 10 minutes counts as inbound traffic, so it never reaches 15 idle minutes. The catch is the hours: a service that never sleeps runs about 720 to 744 hours a month, which fits inside 750 for one service and not for two. Render's free tier docs don't mention pings, so read its acceptable use policy and decide for yourself.
3. Make the cold start shorter. A smaller app boots faster. Avoid running migrations or downloading large models on every start, and load heavy dependencies only when a route needs them.
4. Host it on a plan that stays on. See the comparison below.

EthioDeploy's free plan also sleeps, after 30 minutes without traffic instead of 15. A visitor who wakes it waits while your app boots (we hold the request for up to 30 seconds), and browsers see an auto-refreshing “waking up” page if the boot takes longer. API clients and webhooks get a 503 in that case, so neither free tier is a good home for a webhook that must answer on the first try.

Render gives more on the free tier itself: more memory, custom domains and more than one service. Ours keeps your database. If you only need one small always-on service, Render's Starter is cheaper. Pro costs more, but includes 1 GB and room for several small apps, and you can pay it in Birr. Full details are on EthioDeploy vs Render.