Compare Netlify and Render free tiers side by side. Pricing, limits, change history, and risk assessment for developers.

Netlify vs Render

Side-by-side free tier comparison. Catalogue dates here run to 2026-10-28.

62 other cloud hosting options →

Verdict

Both Netlify and Render offer free tiers. Netlify provides "Free" while Render offers "Hobby".

A verdict here is not a fixed property of the vendor. A one-off pricing event demotes a vendor while its recorded date falls in the last 180 days and then lapses on its own, with nothing about the vendor having changed; a standing condition — a free tier withdrawn and not restored, a product retired — does not lapse with time. A badge carrying a date states the record it rests on; a badge with no date rests on no record in force.

Netlify

Riskstable
CategoryCloud Hosting
TierFree
Verified2026-10-28
Last read2026-10-28
Changes4 recorded
The Free plan is $0 with a limit of 300 credits per month, covering production deploys (15 credits each), compute (10 credits per GB-hour), bandwidth (20 credits per GB) and web requests (2 credits per 10k requests). Netlify says the Free plan is always free, with hard monthly limits that cannot be exceeded or incur costs; extra credits need a paid plan. Personal is $9 a month with 1,000 credits.

Render

Riskstable
CategoryCloud Hosting
TierHobby
Verified2026-10-02
Last read2026-10-24
Changes1 recorded
Hobby plan, $0 a month plus compute. Free web services (512 MB RAM, 0.1 CPU) spin down after 15 minutes without traffic, with 750 free instance hours per workspace a month. One free Postgres database (256 MB RAM, 1 GB storage, 30-day expiry) and one free Key Value instance (25 MB, not continuously persisted to disk) per workspace. 5 GB bandwidth/month included then $0.15/GB; without a payment method on file, Render suspends Free services for the rest of the month instead. 500 build minutes/month. Up to 25 services, unlimited projects with 2 environments each. Pro is $25 a month plus compute.
  • Render's docs say not to use Free instances for production applications. (From render.com/docs/free, read 2026-10-05.)
  • Free web services cannot send outbound traffic on ports 25, 465, or 587, commonly used for SMTP. (From render.com/docs/free, read 2026-10-05.)
  • A free Postgres database expires 30 days after creation and becomes inaccessible. You then have a 14-day grace period to upgrade to a paid plan before Render deletes it with all its data. (From render.com/docs/free, read 2026-10-05.)
  • Free Postgres databases have no backups of any kind. (From render.com/docs/free, read 2026-10-05.)
  • A free web service loses any changes to its local filesystem, such as uploaded images or a SQLite database, every time it redeploys, restarts or spins down, and it cannot attach a persistent disk. (From render.com/docs/free, read 2026-10-05.)
  • If a workspace uses all 750 free instance hours in a month, Render suspends all of its free web services until the start of the next month. (From render.com/docs/free, read 2026-10-12.)
  • Render's free web services need no credit card. (From render.com/articles/platforms-with-a-real-free-tier-for-developers-in-2026, read 2026-10-22.)
  • Render Sandboxes runs isolated microVMs for agents and untrusted code. It is available on every plan including Hobby, billed at $0.12 per active CPU hour plus $0.038 per hour for memory for the default size. (From render.com/pricing, read 2026-10-29.)
  • A Hobby workspace allows 100 concurrent sandboxes by default. There is no maximum session length on any plan, including Hobby. (From render.com/pricing, read 2026-11-07.)
  • Render Sandboxes is in public beta. During the beta, sandboxes have no public URL and no private network to other Render services. (From render.com/docs/sandboxes, read 2026-10-29.)
  • Render offers Free instances only for static sites, web services, Postgres and Key Value. Background workers and cron jobs need a paid compute plan. (From render.com/docs/free, read 2026-11-05.)
  • Render bills for build pipeline minutes used beyond the monthly included amount, unless the spend limit is reached. Without a payment method or at the limit, Render disables new builds for the rest of the month, and services keep running on their existing builds. (From render.com/docs/free, read 2026-11-05.)
  • Render free web services lack scaling beyond one instance, persistent disks, edge caching, one-off jobs, and SSH or dashboard shell access. (From render.com/docs/free, read 2026-11-05.)
  • Render free web services cannot receive private network traffic. They can send private network requests to data stores and paid services in the same region. (From render.com/docs/free, read 2026-11-05.)
  • Render workspace plan upgrades do not remove free instance limits. A service's compute plan is changed separately. (From render.com/docs/free, read 2026-11-05.)
  • While a Free web service is spun down, Render serves a standard disallow-all /robots.txt response. These requests do not reach the service or trigger a spin-up. (From render.com/docs/free, read 2026-11-05.)
  • A free Render Key Value instance loses its data when upgraded to a paid compute plan. (From render.com/docs/free, read 2026-11-05.)
  • Render Free web services allow rollbacks to only the two most recent previous deploys. (From render.com/docs/free, read 2026-11-05.)
  • Render may suspend free web services with unusually high outbound traffic, such as accessing external databases or APIs. Moving to a paid plan restores the service. (From render.com/docs/free, read 2026-11-05.)

Pricing Change History

Netlify

model change effective 2026-04-14 medium impact
Netlify changed its credit rates: bandwidth went from 10 to 20 credits per GB and compute from 5 to 10 credits per GB-hour, while web requests went from 3 to 2 credits per 10,000. The Free plan keeps 300 credits a month, so each credit buys half as much bandwidth and compute. Source ↗
increased effective 2026-04-14 medium impact
Form submissions are now free across all Credit plans (including the Credit Free tier) — previously each form submission cost 1 credit. Credit Pro also gained unlimited team seats (was $20/seat per Git contributor), which effectively removes the prior CMS/Identity 'every committer becomes a $19 Pro seat' gotcha for free-tier users who ever upgrade. Source ↗
restricted effective 2026-03-01 high impact
No longer in force (2026-04-14). Every repo committer is now charged as a full Pro seat ($19/mo) when using Netlify CMS or Identity with a private repo. Previously only users who logged into the Netlify dashboard counted as seats Reversed 2026-04-14: Netlify's pricing page now states that as of April 14th, credit-based Pro plans no longer charge for any seat. The per-committer charge described here is no longer in force. Source ↗
restructured effective 2025-09-04 medium impact
Restructured to credit-based pricing for accounts created from 2025-09-04; Free projects pause when the month's credits run out. Accounts created before that date stay on their legacy plans unless they switch. Source ↗

Render

restructured effective 2026-04-23 high impact
Render replaced its workspace plans. Bandwidth for the Hobby tier went from 100 GB to 5 GB included per month, then $0.15 per GB, and Hobby workspaces are now capped at 25 services. New workspaces got the new plans on 2026-04-23 and existing workspaces moved on 2026-08-01. Free web services, Postgres and Key Value kept their specs, and free web services draw on the workspace's included bandwidth. Source ↗

Watch Both Vendors for Pricing Changes

We do not push notifications. Every change we record is readable the moment it lands, and the JSON answer carries an ETag — send it back as If-None-Match and an unchanged answer costs one 304.

curl https://agentdeals.dev/api/changes?vendor=Netlify curl https://agentdeals.dev/pricing-changes/feed.xml?vendor=Netlify curl https://agentdeals.dev/api/changes?vendor=Render curl https://agentdeals.dev/pricing-changes/feed.xml?vendor=Render

API docs →