Render Review

Render is the host I would give a Rails or Django app that still runs a web process, a queue worker, and Postgres. Those three pieces are a bill you can name in advance. I would not give it a frontend that never stays warm, or a worker that should vanish from the bill at night.

The workspace plan sets who can log in, how much outbound traffic is included, and whether a pull request can boot the whole stack. That line moves when a teammate needs the dashboard, not when the app needs more RAM.

The compute plan sets RAM and CPU for one service, and it keeps charging while that service is running.

Toolradar data: the hosting and deployment ranking we publish scored 297 tools in September 2026. Render is not among the 10 named at the top.

Heroku and DigitalOcean App Platform sit in the group ranked 11 through 30. The median cheapest paid plan among those 10 is $5.50/mo.

How we compared: Render, Railway, Fly.io, Northflank, DigitalOcean App Platform, and Heroku, priced in USD on September 24, 2026. No vendor paid for a mention. We did not deploy a test app.

A Next.js site with no long-running process belongs on the Vercel review and the serverless platforms roundup.

Render is a Git-connected platform where you pick a size for each service, so the month has a ceiling you can read first. A web service gets a public URL, HTTP/2, and managed TLS, and that URL is what visitors open.

A private service stays off that URL, and a background worker runs with no HTTP port, so the queue is not a public site.

Cron, static sites, Render Postgres, and Key Value (compatible with Redis clients) are their own service types, so each one is its own line. Native builds cover Node.js, Bun, Python, Ruby, Go, Rust, and Elixir, so those stacks ship without a Dockerfile.

Java, .NET, and anything else ship as a Docker image, and that image is still a sized instance.

A blueprint file, render.yaml, describes the web process, the worker, and the database in one pull request. That file is how a team stops staging from drifting away from production. Hobby, Pro, and Scale are self-serve, so you can open the account without a sales call.

Enterprise is a contract and publishes no list price, so you cannot budget it from the page. Custom compute, up to 64 CPU and 512 GB of RAM, is quote-only, so a large box is a sales conversation.

You connect a repo, choose a compute plan, and Render runs the build, so the size is the decision. Build commands and pre-deploy commands spend pipeline minutes, and Hobby includes 500 of those minutes. That allowance fits a modest solo app and gets tight if you rebuild all day.

Past it, new builds can be blocked if you have no card, or billed if you do. A free account then stops rather than running up a charge.

A spend cap on pipeline minutes stops new builds while the last good artifact keeps serving. The live site stays up, and the next release waits. A Free web service spins down after 15 minutes without inbound HTTP or WebSocket traffic, then takes about a minute to wake. Browsers see a loading page during that wake, so the first visitor on a cold link waits.

The workspace gets 750 free instance hours each calendar month. Spun-down time does not spend those hours, and leftover hours do not roll over, so a quiet week cannot be saved for later. A second free web service running beside the first will exhaust the pool before the month ends.

Paid web services and workers do not spin down, so sleep is a free-tier behavior only.

The disk on a service is ephemeral, so uploads and a local SQLite file disappear on redeploy, restart, or spin-down, and rows belong in Postgres. A persistent disk keeps those files, and attaching one disables zero-downtime deploys for that service.

Free web services may send private-network requests to a database in the same region, and they cannot receive private traffic.

Hobby can preview a single service, which covers one pull request and not the API beside its database. Full-stack preview environments, the pull request that boots the API and the database together, start on Pro, and so does horizontal autoscaling.

Vertical scaling, moving one service to a larger plan, is available on Hobby, so you can buy RAM without a teammate. Suspend a paid service and the compute clock stops at that second.

Hobby has no monthly fee and allows one member, 25 services, two custom domains, and two environments per project, which keeps it a solo account. A second person in the dashboard means Pro, the flat fee in the table, and seats stop multiplying.

Twenty people cost the same workspace line as two, until the team needs SSO, SCIM, or a HIPAA workspace, which sit on Scale.

A Starter web service is $7/mo and Basic-256mb Postgres is $6/mo, so the pair is $13/mo on Hobby before bandwidth. A worker cannot use the free plan, so it is a second Starter and stays billed when idle. Five people add the Pro workspace on top of that web service, worker, and database. The sum is $45/mo before outbound traffic, and the headcount is not inside that sum.

The April 23, 2026 changelog is why a 2025 quote will mislead you, because Professional was $19 per member per month. Five members were $95 before any instance, and twenty were $380. Pro replaced that bill with one workspace charge and unlimited members.

Scale replaced Organization, which had been $29 per member per month. Render's post the same day says 75% of paying customers would see the bill fall or stay flat. A small team with heavy bandwidth or many domains could pay more.

An editor's note says every workspace had been moved by August 1, 2026, and compute prices did not change in that rollout. The instance menu is the part of an old quote you can still trust.

Outbound bandwidth is now the seat fee, then $0.15 per GB after the included pools, shared by every service, including static sites and free web services. A marketing site on the same workspace can eat the API's allowance.

Scale includes 1 TB, inbound is free, and extra custom domains and persistent disk are both $0.25 a month, per domain or per GB.

Postgres storage past the included gigabyte is $0.30 per GB, and a paid disk also disables zero-downtime deploys, so storage changes the release. Build pipeline overage, dedicated outbound IPs, and AWS PrivateLink are separate rows in the table.

Adding a card runs a $1 USD authorization that Render refunds, so the card check is not money you keep. If a Pro or Scale workspace has no services, live or suspended, and no activity all month, Render waives that month's workspace fee. Enterprise publishes no list price, so a contract buyer has to ask.

Railway's subscription is a usage credit, and a stopped service drops CPU and memory, unlike an instance that bills while it runs. Fly.io has no workspace fee, and the small shared machine changes with the region, so the city sets the price.

Northflank's sandbox stays awake, so a preview that must not sleep still costs. App Platform's smallest container is a fixed size on an account that may already pay for Droplets. Heroku's always-on dyno matches Starter and does not grow RAM when you buy metrics.

Prices below were read on each vendor's pricing page on September 24, 2026.

Render fits a developer who will name the instance and keep the worker and Postgres as separate services. Watch outbound traffic after the included pool, because that is what the invoice assumes. Hobby is the solo account, and Pro is the switch when a teammate needs the dashboard. Pro is also the plan when a pull request has to boot more than one service.

Skip it when the process should cost nothing while it is stopped, which is the comparison on the Railway review. Skip it when the city is the reason you are picking a host, which is Fly.io.

Skip it when the rest of the account already pays DigitalOcean, and read the DigitalOcean review before you add App Platform.

A database that has to branch for every preview is a different product. Start with the Neon review and Postgres hosting, and with Supabase if login ships next to the tables.

Leaving dynos is Heroku alternatives and the Heroku review. A static site that should not treat bandwidth as the meter is the Netlify review.

A machine you patch yourself is VPS hosting for developers.

Subscribe free for the next change to this bill.