Render Pricing 2026: What You Actually Pay Per Service

Last verified: October 7, 2026.

Render's pricing is simple in shape and complicated in math. The shape is per-service billing — each web service, worker, cron job, Postgres database, and Redis instance is a line item on the monthly invoice, billed by the second. The complication is the line items themselves: a small SaaS that feels like one thing is four to five billable services, and the cost adds up in a way that surprises first-time Render users who came from Heroku or from a usage-only PaaS like Railway or Fly.io.

This walkthrough reads Render's pricing the way a new customer encounters it. First the compute plans, then the database pricing, then the April 23, 2026 workspace repricing that changed how teams pay, then the real-world cost examples by app tier, then the comparison against Heroku, Railway, Fly.io, Vercel, and a $5/month Hetzner VPS.

The Web Service Compute Plans

Render's web services run on a tier of compute plans from $7/month to $700/month, billed by the second:

Background workers and cron jobs use the same instance pricing. The free compute plan exists for web services and Postgres (more on that below) but suspends after 15 minutes of inactivity — Render explicitly warns that the free tier is not for production use. Three Standard instances cost $75/month. A Pro Plus instance at $175/month is roughly the cost of a small dedicated VM; the difference is that Render manages the OS, the runtime, the deploys, and the TLS.

Render Postgres Pricing

Render Postgres is the managed database, and the pricing scales steeply past the Starter tier:

The $7 Starter database has 256 MB RAM and 1 GB storage — Render positions it for development, not production. The Basic tier at $20/month is the minimum viable option for a real application: 1 GB RAM is enough for most small SaaS backends, and 16 GB storage covers years of growth for a typical schema. Standard at $95/month is the right jump for apps with multi-GB working sets or read-replica needs.

Free Render Postgres has a 30-day hard expiration. After 30 days, the database enters a 14-day grace period, then Render deletes it (along with all data). The free Postgres is fine for evaluating the platform, not for keeping anything you care about.

Render Redis (Key Value) Pricing

Render Key Value instances are Redis-compatible and priced steeply relative to memory:

Redis pricing is where Render is most expensive relative to alternatives. The 25 MB Starter at $10/month is barely enough for a session cache on a low-traffic app; the 1 GB Standard at $85/month is the same money as a small VPS where you could run Redis with gigabytes of memory. Render's value here is operational — managed Redis with persistence, replication, and failover — not cost. For pure caching at scale, a sidecar Redis on a Hetzner or DigitalOcean box wins on price.

The April 23, 2026 Workspace Repricing

On April 23, 2026, Render removed per-seat workspace fees and replaced them with flat monthly subscriptions. The change rolled out to new workspaces immediately and migrated legacy workspaces by August 1, 2026:

For a 3-person team on the legacy Professional plan, the bill was 3 × $19 = $57/month before any usage. On the new Pro plan, the same team pays $25/month flat — a 56% cut. For a 15-person team on the legacy Professional plan ($285/month), the same team on Pro pays $25/month flat — a 91% cut.

The repricing also added self-serve compliance on Pro (SOC 2, ISO 27001 reports, audit logs) and SSO/SCIM/HIPAA on Scale. Bandwidth and build pipeline minutes moved to usage-based billing at $0.15/GB and $5/1,000 minutes respectively. The new Hobby and Pro plans include less bandwidth than their legacy counterparts because legacy plans subsidized bandwidth with seat fees.

The sting: teams that needed SOC 2 under the legacy Organization plan ($29/member/month) move to Scale at $499/month flat. For a 15-person team, $435/month becomes $499/month — a 15% increase for the same compliance posture. The move is rational for growing teams and irrational for teams under 17 members.

Real-World Cost by App Tier

Three representative cost stacks, billed in October 2026:

The small-SaaS number is the most important one to internalize: a real production app on Render starts at $49/month and reaches $150–$220/month once you add staging. Staging is a full duplicate cost — Render does not have a "preview environment" magic; staging means paying for every service twice. Teams that forget this find their staging bill is bigger than their production bill.

Per-service billing adds up. Per-service billing means every microservice, every queue worker, every cron job is a line item. A five-microservice architecture on Render can cost more than a single monolithic deployment on a comparable VM. The trade is operational simplicity versus per-line-item cost.

The Comparison That Decides the Platform

Render competes against Heroku, Railway, Fly.io, Vercel, and the cheap VPS tier. The numbers:

Render wins on per-service predictability. The invoice is the same shape every month; the math is arithmetic, not usage metering. Railway wins on usage bursts — a service that idles for most of the month and runs hard for three days is cheaper on usage-based pricing than on Render's always-on billing. Fly.io wins on multi-region deployment and on price for small apps. Heroku loses on price but wins on ecosystem (add-ons, buildpacks, decade of operational tooling). Vercel wins on Next.js and frontend deployment, loses on backend cost. Hetzner wins on price for self-managed teams and loses on operational overhead.

When Render Is the Right Pick

Render is the right platform when you want predictable per-service billing, prefer a simpler model than usage-based pricing, need managed PostgreSQL without running your own, and your stack has 2–4 services maximum. The "2–4 services" ceiling is real; Render's per-line-item billing punishes microservice-heavy architectures.

Consider switching when you run five or more services and the per-line-item cost stacks, when you need staging without doubling the bill (look at Fly.io's machines or a self-managed K8s), or when your database needs outgrow the managed Postgres tiers (the $395/month Pro Plus tier is the practical ceiling — past that, a managed Postgres on a VPS or a hosted Postgres on Neon or Supabase wins on cost).

For the 80% of teams running a single API, a single worker, a single Postgres, and a single Redis, Render is the simplest bill to read and the closest thing to a Heroku replacement that does not price like 2018 Heroku.

Read next

Heroku Pricing 2026: Eco, Basic, Standard Compared is the direct legacy comparison — same Heroku-shaped workloads, current Heroku bills, and Railway Pricing 2026: Usage-Based vs Render Per-Service is the usage-based alternative that beats Render on bursty workloads and loses on predictable monthly bills.