Is Render Free? The 15-Minute Sleep, the 30-Day Database Clock, and the robots.txt Nobody Mentions (2026)

TL;DR: Free Render Is Real, and It Is Designed to Expire on You

Render's free tier is one of the few in hosting that doesn't hide a clause. Vercel's Hobby plan is free until you charge a customer, because the license says non-commercial. Railway's "free" is a one-time $5 credit. Render's is different: no commercial restriction, no trial clock on the compute itself, no card. What Render does instead is make the free tier behave like a demo. Sleep after 15 minutes. One minute to wake. A database with a 30-day fuse. A robots.txt that tells search engines to go away whenever nobody's visiting. As of September 2026, every one of those is documented on render.com, and every one of them is the reason a real product moves to the $7 instance within a month. The rest of this post is the detail, with the numbers.

What "free" covers on Render in 2026

Render prices two things separately: a workspace plan (flat, per team) and compute (per service). The Hobby workspace is $0 a month. On it you can run up to 25 services, and four service types have a free compute plan:

• Web services (Node, Python, Rails, Go, Docker — anything) on 512 MB RAM and a fractional CPU
• One Postgres database per workspace, 1 GB of storage
• One Key Value (Redis-compatible) instance, 25 MB, in-memory only
• Static sites, always free, on Render's CDN with custom domains and TLS

The Hobby workspace also includes 5 GB of outbound bandwidth a month (then $0.15/GB), 500 build-pipeline minutes (then $5 per 1,000), 2 custom domains (then $0.25 each per month), one team seat, 7 days of logs, and 2 environments per project. Free web services keep most of the real features: custom domains, managed TLS, service previews, log streams, and rollbacks to the last two deploys.

For a portfolio, a Discord bot, a weekend prototype, or a Rails app you're showing one investor, that is a complete, usable stack at $0. Render's own docs are honest about the intended use: "perfect for testing out a new technology, working on a hobby project, or previewing Render's developer experience. Do not use them for production applications."

The 15-minute spin-down (and the one-minute wake)

This is the limit everyone knows about, so here is the precise version. A free web service spins down after 15 minutes without any inbound traffic, HTTP requests or WebSocket messages included. It spins back up on the next request, which takes about one minute, during which the visitor sees a Render loading page. For a demo you're clicking through, that's a mild annoyance. For a link in a cold email, it's a bounce.

Two consequences that the "just ping it every 14 minutes" crowd misses:

• Local files are lost on every spin-down. Free services have an ephemeral filesystem and can't attach a persistent disk. If your AI-built app stores uploads or a SQLite database on disk, the first quiet afternoon deletes it. This is the single most common "my data vanished" story I hear from founders who shipped a vibe-coded app to a free tier.
• 750 free instance hours per workspace per month. A service only burns hours while it's awake, and a 31-day month has 744 of them. So one service kept permanently awake by a pinger uses the entire allowance; a second awake service pushes you over, and when the hours run out Render suspends every free web service in the workspace until the first of next month.

The robots.txt nobody mentions

Buried in Render's free-tier docs: while a free web service is spun down, any request to /robots.txt gets an automatic User-agent: * Disallow: / response. The request never reaches your app and never wakes it. The intent is sensible — don't let a crawler spin up an idle service — but read it from a search engine's side. Googlebot arrives at 3am, your app is asleep, and Render tells it the entire site is off-limits. If you were wondering why your free-tier landing page never indexed, this is worth more than any amount of on-page SEO. Free Render is fine for software. It is a bad place to host anything you want found.

The 30-day database clock

The free Postgres is where the real fuse is. Per render.com/docs/free as of 2026: only one free Postgres per workspace, 1 GB of storage, no backups of any kind, no connection pooling, and it expires 30 days after creation. Expired means inaccessible. After a further 14-day grace period, Render deletes the database and everything in it. You get emails as both deadlines approach. The fix is to upgrade the database to any paid compute plan, and the smallest is $6 a month for 256 MB. That is the actual price of Render's free tier for anything with users: $6, on day 30. The free Key Value instance has a version of the same problem — in-memory only, so every restart empties it, and Render reserves the right to restart free instances at any time.

Render pricing when you outgrow free

The good news is the ladder is short and, as of 2026, cheap:

• Web service: $7/mo for 512 MB (same size as free, but no sleep, no hour cap, persistent disks at $0.25/GB, SSH, one-off jobs) · $25/mo for 1 CPU and 2 GB · $85/mo for 2 CPU and 4 GB
• Postgres: $6/mo for 256 MB · $19/mo for 1 GB · $40/mo for 2 GB, with point-in-time recovery and backups
• Workspace: Hobby stays $0. Pro is $25/mo plus compute for unlimited seats, 25 GB of bandwidth, full-stack preview environments, and horizontal autoscaling. Scale is $499/mo for HIPAA workspaces and SSO.

So a real app — one $7 service, one $6 database — is $13 a month on Render, and a comfortable one is about $44. Compute bills by the second, so a service you turn off stops costing money. That's competitive with Railway's $5 Hobby plan and it's the comparison that matters, because those two are the closest rivals in the deploy-from-a-repo category.

Render vs Vercel vs Railway: three different kinds of "free"

Founders ask this as one question and it's really three:

• Render: free, no commercial clause, but sleeps in 15 minutes, caps at 750 hours, and expires its database in 30 days. Free for hobbies by design.
• Vercel: free Hobby plan that never sleeps, with roughly 100 GB of transfer and a million function calls a month — restricted to personal, non-commercial use. Free until the Stripe button.
• Railway: no permanent free tier, a one-time $5 credit that expires in 30 days, then $5/mo with $5 of usage included, no sleep, no clause. Not free, and the cheapest "commercial from day one" option of the three, which is why this site runs there.

If you're picking a frontend host and the question is Vercel against its closest rival instead, that's a different comparison with a different answer: Vercel vs Netlify.

Who should stay on free Render, and who should pay the $7 today

Stay free: static sites (no catch at all), prototypes you're demoing live so they're awake anyway, internal tools with a handful of daily users who can tolerate a one-minute wake, and anything with no database or a database you don't mind losing.

Pay today: anything a customer or a search engine will hit unannounced, anything storing files on disk, and anything with a Postgres you'd be upset to lose on day 44. It's $7 for the service and $6 for the database. The free tier isn't a trap. It just isn't for you anymore.

The micro-action for today

Open the Render dashboard and look at the creation date on your free Postgres. If it's older than two weeks, decide now whether that data matters, because the email is coming. If you shipped an AI-built app to a free tier and you're not sure what else is living on the ephemeral disk, the vibe coding security checklist has an agent prompt that inventories exactly that. And if the honest answer is "the app has customers and a free database," that's a rescue, not a hosting question.