Render

render.comcontributed by Samuele Ongaro

KEEP IT

The value is the network, the data or the infrastructure. Keep paying.

Runs web services, workers, cron jobs and managed Postgres from a git repository, with deploys, health checks, scaling and certificates handled by the platform.

Promptfree, for everyone, and the only version there is
Do not rebuild this if the managed database is why you are here. Somebody else recovering it is what you are paying for.

Backups taken, retention managed, point-in-time restore available, and a person who will help when a disk fails. That last part is the product, and it is worth more than the compute.

WHEN TO KEEP PAYING
- You do not want to be responsible for a database at three in the morning
- Preview environments per pull request, which are genuinely useful

WHEN TO SELF-HOST
- One application, steady traffic, and a willingness to own the backups. Then a VPS costs a fraction, and the shape is under Heroku elsewhere in this catalogue

IF YOU SELF-HOST, THE DATABASE IS THE WHOLE RISK
Everything else — the process, the certificates, the deploy — is recoverable in minutes from a repository. The data is not. So:
- **Continuous replication** of the write-ahead log to object storage, which gives a recovery point measured in seconds rather than a night. Litestream for SQLite, the archive facility for Postgres
- Nightly snapshots as well, with a stated retention
- **A restore rehearsed onto a clean machine, with the time it took written down.** An untested backup is not a backup, and that number is your actual recovery time. Almost nobody knows theirs
- A verification job that restores a sample and checks integrity, because a backup that has been failing quietly for three weeks looks exactly like one that is working
- An alert on the age of the last successful backup, somewhere you will actually see it

AND THE MIGRATION DISCIPLINE THAT PREVENTS MOST INCIDENTS
Backwards-compatible in both directions across a deploy: add a column, deploy, write to it, backfill in batches, then read from it, and remove the old one in a later release. Never two of those steps together. Test every migration against a restored copy of production first.

THE HONEST TRADE
Self-hosting saves real money and makes you the person who is called. Write that down alongside the saving, and decide with both numbers in front of you.

THE ONE-LINE VERSION
Pay for somebody to recover the database, or set up replication and rehearse the restore. There is no third option.

What you lose

  • Managed Postgres with backups, point-in-time recovery and failover you never configure
  • Zero-downtime deploys, health checks and automatic rollback as defaults rather than scripts
  • Autoscaling and private networking between services
  • Certificates, DDoS absorption and DNS handled at the platform level
  • Somebody else being paged when a host dies at three in the morning

If you would rather not build

  • Dokku — a small single-host platform
  • Railway — paid, similar model, usage-based pricing

What it costs

read from their page 15 Aug 2026

PlanBilled monthlyBilled yearlyLast read
—$19/mo—15 Aug 2026

Their pricing page is where these came from. Seeing a different price? Tell us.

The escape hatch

open source · no votes, no paid placement

Coolify

$0

Builds from git and deploys to a server you own.

coollabsio/coolifyfree · open source

Kamal

$0

Deploys containers to servers you own, with zero-downtime rollovers.

basecamp/kamalfree · open source

Why this verdict

our own opinion · changed only by a person

23/100

Verdict no at 23: the runtime side is genuinely straightforward and this prompt does it properly. The managed database is the line — backups, recovery and failover are the work, and doing them yourself means testing restores forever.

History

tracked since 9 Aug 2026 · nothing is ever overwritten

Interest · last 30 dayspeak 1/day
views0130 Aug4 Sept9 Sept14 Sept19 Sept24 Sept28 Sept
— views— prompt copies none yet— votes none yet

Questions about Render

answered from the record above

Is Render free?

No — the plan we track is $19 a month. Professional at $19 per user per month, plus per-service compute from about $7/month; databases and bandwidth are billed separately.

Can you replace Render by building your own?

KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 23 out of 100, build time longer than it saves. Read what you lose before you decide.

How much does Render cost?

$19 a month on Professional — $228 a year. Recorded 9 Aug 2026.

What do you lose by replacing Render?

Managed Postgres with backups, point-in-time recovery and failover you never configure; Zero-downtime deploys, health checks and automatic rollback as defaults rather than scripts; Autoscaling and private networking between services; Certificates, DDoS absorption and DNS handled at the platform level; Somebody else being paged when a host dies at three in the morning. If any of those carry weight for you, keep paying.

Is there an open-source alternative to Render?

Yes: Coolify, Kamal. The prompt on this page is for when you want it your way instead.

Related entries

same category first, most replaced first

All 21 in Hosting & databases

Not sending yet

Every week, something stops being worth paying for.

New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.

free forever · no tracking pixel · stored here, never passed to anyone

Esc