Render

Modern Heroku alternative. Web services, background workers, Postgres, Redis, cron, all integrated.

VISIT RENDER

Key takeaway: For a conventional web app with a database, background workers, and cron, Render is the least surprising place to put it. It is the natural landing spot for Heroku refugees because the mental model transfers unchanged. Pick Railway instead if interface polish and per-second billing matter more, or Fly.io if you need more than one region.

Quick facts

  • CategoryPaaS
  • PricingFreemium
  • LicenseProprietary
  • Created2019
  • GitHub starsclosed
  • Edge-readyNo
  • Free tierYes
  • Egress billingFair

Bundled services: Postgres Redis Persistent disks Cron Background workers

What it is

Render is the modern Heroku, full PaaS for web services, static sites, background workers, cron jobs, with native Postgres + Redis + persistent disks. Auto-deploy from Git, preview environments, predictable pricing. Used heavily by teams migrating off Heroku and by mid-market SaaS that wants infrastructure to disappear.

Best for

  • Teams migrating off Heroku without changing app architecture
  • Background-worker-heavy apps (queues, cron, scheduled jobs)
  • Apps that need persistent disk + Postgres + Redis in one platform

When not to pick it

Skip Render for static-only or Jamstack-first work, Vercel / Netlify / Cloudflare Pages fit better. Skip if you need the AWS-native primitives (SQS, Lambda).

My take

Render is the right pick for traditional web-app workloads that need a real PaaS. Pricing is fair, DX is solid, and the migration path off Heroku is well-trodden.

Why Heroku teams land here first

Render reproduces the Heroku mental model without the Heroku bill: connect a repository, define services, and get web processes, background workers, cron jobs, managed Postgres, Redis, and persistent disks in one place. Nothing about the application has to change, which is the entire point of the migration and the reason this is the most travelled path off Heroku. Preview environments per pull request behave the way you would expect. Blueprints let you declare the whole stack in a file, so environments are reproducible rather than clicked together by hand. For a team whose product is an ordinary web app with a queue behind it, this is the platform shape that lets infrastructure stop being a topic in standup. Pricing is predictable per service rather than metered into surprise, which is a meaningful difference from the Jamstack hosts once traffic grows.

What Render deliberately is not

Render is regional, not global. There is no edge runtime and no isolate model, so a user far from your chosen region pays the round trip. For a Jamstack site or a latency-sensitive read path, Vercel, Netlify, or Cloudflare Pages fit better and Render is the wrong tool. It is also not AWS: if your architecture depends on SQS, Step Functions, or a specific managed database flavour, you will end up straddling two providers. And while the free tier exists, free web services sleep when idle, which makes it a demo tier rather than a production one. The right read is that Render sells the disappearance of operations for ordinary web applications. Ask for more than that, whether multi-region placement, edge compute, or hyperscaler primitives, and you should be looking at Fly.io or AWS.

Frequently asked questions

Is Render a good Heroku replacement?

It is the most direct one. Web services, workers, cron, managed Postgres, and Redis map almost one to one onto Heroku concepts, so applications usually move without architectural change. The main adjustments are add-ons with no Render equivalent and anything relying on Heroku-specific buildpack behaviour. Budget a few days rather than a project for a typical app.

Does Render have a free tier?

Yes, and it is useful for demos and side projects rather than production. Free web services spin down when idle and cold start on the next request, which is fine for a portfolio piece and not fine for a paying customer. Free databases carry limits too. Production work belongs on paid instances.

Render or Railway?

Render for a stable production platform with predictable per-service pricing and a well-worn Heroku migration path. Railway for the better interface, per-second billing, and fast environment creation, accepting that there is no free tier. Both target the same workloads. Render feels more like infrastructure, Railway feels more like a developer tool.

Links

Compare Render side-by-side

Render vs Railway → Render vs Fly.io → Render vs Heroku →

Similar tools you should also consider

Fly.io

Run Docker containers in 30+ regions. Per-region scaling, Postgres included, edge-shaped PaaS.

Read the take →

Railway

Modern PaaS with the cleanest DX in the category. Per-second pricing, Heroku-style git deploys.

Read the take →

Heroku

The original PaaS. Mature, capable, expensive, and still relevant in enterprise.

Read the take →

If Render is your pick, the next conversation is short

The 30-min call is where your hosting choice becomes a real architecture, a migration plan if you are switching, and a price range you can take to your stakeholders without surprise bills in month 4. Describe your stack, your traffic shape, your budget. I tell you whether Render is genuinely your fit.