Skip to content
inetGeek

Render

Managed cloud platform that builds and runs web services, background workers, static sites and databases from Git repositories or Docker images.

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

Updated 22 criteria compared

Category
paas
Free tier
Yes
Entry paid plan
Not documented
Regions
Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
01.

Who it suits.

Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.

Consider something else if…

Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.

Editorial · Palash Bagchi · approved

02.

What the documentation says.

Each value below links to the page it was read from, with the sentence it came from. Criteria Render does not publish are not listed.

Pricing

Free tier

Yes

Sources (1) →
  • Deploy for Free – Render Docs ↗

    “You can deploy certain Render service types free of charge: Web services (web apps in Node.js, Python, Rails, etc.), Render Postgres databases, Render Key Value instances”

    Read 2026-09-05 · official docs

Pricing model

The Hobby plan does not have a monthly fee, so you only pay for usage.

Sources (1) →

When you exceed a cap

Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is hit, Render stops all pipeline tasks including service builds for the rest of the month (platform-wide, all plans)

Sources (1) →
  • Build Pipeline – Render Docs ↗

    “If you run out of pipeline minutes during a given month, you automatically purchase a supplementary amount of minutes for your current tier, unless you've reached your monthly spend limit, or you haven't added a payment method. In the above cases, Render stops running pipeline tasks (including service builds!) for the remainder of the current month.”

    Read 2026-09-05 · official docs

Limits

Storage (entry plan)

No persistent disk is included on any instance type, including the entry `0.5c-512mb` plan; services run on an ephemeral filesystem unless a persistent disk is attached separately

Sources (1) →

Memory (entry plan)

512 MB RAM (with 0.5 CPU) on the `0.5c-512mb` instance type, the cheapest paid web service compute plan (legacy name: Starter)

Sources (1) →

Sites or apps included

25 total services on the Hobby workspace plan (Render's entry workspace tier, compute billed separately); also limited to a single team member

Sources (1) →

Monthly visits cap

No request-count cap is published; traffic is capped by outbound bandwidth, 5 GB/month included on the Hobby workspace plan (Pro 25 GB, Scale 1 TB)

Sources (1) →

Included bandwidth

Hobby: 5 GB; Pro: 25 GB; Scale: 1 TB; Enterprise: Custom

Sources (1) →
  • Outbound Bandwidth ↗

    “Workspace plan / Included bandwidth — Hobby 5 GB, Pro 25 GB, Scale 1 TB, Enterprise Custom”

    Read 2026-09-05 · official docs

Build minutes

Hobby: 500; Pro: 1000; Scale: 5000

Sources (1) →
  • Build Pipeline – Render Docs ↗

    “Each workspace receives included Starter-tier pipeline minutes per month — Hobby 500, Pro 1000, Scale 5000”

    Read 2026-09-05 · official docs

Concurrent builds

One active build per service, platform-wide on all plans; a new build cancels the in-progress one for that service

Sources (1) →
  • Build Pipeline – Render Docs ↗

    “Each Render service can have only one active build at a time. Whenever a new build is initiated, Render cancels any in-progress build for the same service.”

    Read 2026-09-05 · official docs

Execution

Managed connection pooling

Supported

Sources (1) →
  • Connection Pooling for Render Postgres — Render Docs ↗

    “If your Render Postgres database requires more simultaneous connections than its compute plan allows, you can enable connection pooling for it at no additional cost. When enabled, Render runs PgBouncer in front of your database to manage its connection volume: [...] Connection pooling is not available for free databases.”

    Read 2026-09-05 · official docs

Deployment

Git deployment

Supported

Sources (1) →

Docker deployment

Supported

Sources (1) →

Containers

Supported

Sources (1) →
  • Docker on Render – Render Docs ↗

    “Your services can: Pull and run a prebuilt image from a registry such as Docker Hub, or Build their own image at deploy time based on the Dockerfile in your project repo.”

    Read 2026-09-05 · official docs

Scheduled jobs

Supported

Sources (1) →
  • Cron Jobs – Render Docs ↗

    “You can create cron jobs on Render that run periodically on a schedule you define.”

    Read 2026-09-05 · official docs

Infrastructure

Persistent processes

Supported

Sources (1) →
  • Background Workers – Render Docs ↗

    “Background workers are services that run continuously (like a web service or a private service), but they don't receive any incoming network traffic.”

    Read 2026-09-05 · official docs

Persistent storage

Supported

Sources (1) →
  • Persistent Disks – Render Docs ↗

    “You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts.”

    Read 2026-09-05 · official docs

Managed databases

Supported

Sources (1) →
  • Render Postgres ↗

    “Deploy fully managed, enterprise-grade databases that scale to any workload.”

    Read 2026-09-05 · official docs

Edge network

Supported

Sources (1) →
  • Static Sites – Render Docs ↗

    “Render serves your site over a blazing-fast, reliable, and secure global CDN. We cache your content on network edges around the world, ensuring the fastest possible load times for your users.”

    Read 2026-09-05 · official docs

Scales to zero

Supported

Sources (1) →

Autoscaling

Limited

Sources (1) →
  • Scaling – Render Docs ↗

    “Render can automatically scale your service up and down based on CPU and/or memory utilization targets that you specify. [...] Autoscaling requires a Pro plan or higher.”

    Read 2026-09-05 · official docs

Regions

Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore

Sources (1) →
  • Regions ↗

    “Oregon, USA / Ohio, USA / Virginia, USA / Frankfurt, Germany / Singapore”

    Read 2026-09-05 · official docs