If you're sizing a small Python app for Render's free tier — a web service in front, and a worker process that has to stay up to drain a queue — the worker half of that doesn't work. The pricing page doesn't make it obvious why, so here is what it actually says.
Render's free compute is real, but it doesn't apply to every service type. Their pricing FAQ is specific about which ones: free compute plans let you spin up web services, Render Key Value instances, and Render Postgres databases at no charge. Background workers aren't on that list. And on Render a worker is its own service type — not a web service you happen to run a loop inside. The cheapest instance you can attach to one is Starter, at $7/month.
So what you actually get for $0 is a web service that sleeps after 15 minutes idle, a Key Value instance, and a Postgres database that expires after 30 days. That's fine for a demo. It is not a setup for anything that has to keep working while nobody is looking at it.
The failure mode is the part worth knowing in advance. The obvious workaround is to move the queue loop inside the free web service — but that service spins down once traffic stops, and your queue quietly stops draining. No error, no crash, nothing in the logs. It just looks like there was nothing in the queue.
If you're mapping out which free tiers still include what, I keep that written up here: https://toolfreebie.com/best-free-hosting-2026/
Top comments (0)