Render vs Supabase pricing

The two pages

Tier by tier

Rows are lined up by position on each page, not by tier name, because the names never match across two vendors. Row 1 is the top tier on each page, row 2 the one under it. Where one page has fewer tiers than the other, the row is left blank rather than paired with something it is not.

1. Row 1
   Render

   HobbyFree

   Supabase

   FreeFree
2. Row 2
   Render

   Pro$25/mo

   Supabase

   Pro$25/month
3. Row 3
   Render

   Scale$499/mo

   Supabase

   Team$599/month
4. Row 4
   Render

   EnterpriseCustom

   Supabase

   EnterpriseCustom

The entry tier

Changes we recorded

Every change we have written up for either page, newest first.

• Render pricing page changed

  Render·1 Sept 2026

• Supabase pricing page changed

  Supabase·1 Sept 2026

• Supabase pricing page changed

  Supabase·29 Aug 2026

• Render pricing page changed

  Render·29 Aug 2026

• Supabase pricing page changed

  Supabase·27 Aug 2026

• Supabase pricing page changed

  Supabase·26 Aug 2026

• Render pricing page changed

  Render·26 Aug 2026

• Render pricing page changed

  Render·23 Aug 2026

• Supabase pricing page changed

  Supabase·23 Aug 2026

• Render introduces new pay-per-use Flex tier for Workflows and removes Beta label, repositioning around migration credibility while maintaining existing tiered pricing.

  Render·21 Aug 2026

  Render introduces new pay-per-use Flex tier for Workflows and removes Beta label, repositioning around migration credibility while maintaining existing tiered pricing. Why it matters: • Flex tier targets cost-sensitive or bursty workload users with transparent per-CPU and per-GB billing, potentially competing on unit economics for non-production or experimental tasks • Removal of 'Beta' from Workflows signals production readiness and confidence, likely accelerating adoption among enterprises evaluating infrastructure migration • Shift from 'switching clouds' to 'migrating production infrastructure' in credit messaging indicates Render is targeting higher-stakes, larger deal enterprise migrations rather than general cloud shopping Pricing & Billing Model: - New Flex tier added at $0.20/active CPU hour + $0.05/active GB hour (pay-per-use) vs. existing tiers which are provisioned capacity billing - Flex tier specs: up to 1 CPU, up to 4GB RAM, billed only for active compute time (new 'Billed for' column introduced across all tiers for clarity) - Existing Starter through Pro Max tiers unchanged in price ($0.05-$2.00/hour) but now explicitly labeled 'Provisioned capacity' billing Positioning: - Workflows promoted from Beta to GA (label removed) - Marketing copy evolved from 'Switching clouds?' to 'Migrating production infrastructure?' - narrower, higher-value segment focus - Workflows now explicitly claim 'Up to 10,000 CPUs for concurrent tasks' (previously 'Run 1000s of parallel, async tasks') - quantified ceiling signals scalability confidence Tier Removal: - Pro Ultra tier ($7.00/hour, 8 CPU, 32GB) removed from pricing table; all other existing tiers remain with identical pricing What to do: • Audit your own Workflows or task scheduling offering: assess whether a pay-per-use Flex option is missing from your pricing and whether it could unlock a cost-conscious segment Render now targets explicitly • Review messaging around production-grade readiness and migration support; if you lack a clear 'migration credits' or 'migration support' program, prioritize one to compete on enterprise land • Model the unit economics of Render's Flex pricing ($0.05/GB-hour, $0.20/CPU-hour) against your own offerings to ensure competitive positioning on bursty, non-production workloads

• Render updates privacy notice cookie disclosure with American English spelling

  Render·18 Aug 2026

  Render updates privacy notice cookie disclosure with American English spelling Why it matters: • Cosmetic localization change only-no material impact to pricing, features, or positioning • Reflects minor editorial refresh; no strategic or competitive implications Positioning: - Changed 'utilises' to 'utilizes' (British to American English) - Changed 'personalisation' to 'personalization' (British to American English) - Privacy policy link and functionality remain unchanged What to do: • No action required-this is a cosmetic copy update with zero competitive impact

• Render updates cookie notice with British English spelling (minor localization adjustment).

  Render·15 Aug 2026

  Render updates cookie notice with British English spelling (minor localization adjustment). Why it matters: • Indicates possible UK/EU market localization efforts, though no pricing or feature changes present. • No competitive threat or strategic shift-purely a terminology/regional language update. Messaging: - Changed 'utilizes' to 'utilises' (US to British English) - Changed 'personalization' to 'personalisation' (US to British English) - Cookie notice text remains functionally identical in meaning and transparency What to do: • Monitor for follow-up localization changes (currency, regional pricing tiers, compliance messaging) that might signal Render's expansion into UK/EU markets. • No immediate action required unless Render introduces region-specific pricing or compliance changes.

• Supabase shifts usage limits FAQ from proactive notification focus to self-service usage tracking

  Supabase·15 Aug 2026

  Supabase shifts usage limits FAQ from proactive notification focus to self-service usage tracking Why it matters: • Indicates Supabase is emphasizing user agency in monitoring consumption rather than platform-triggered alerts, suggesting confidence in dashboard instrumentation • May reflect customer feedback that self-service visibility matters more than automatic warnings for cost management • Could signal Supabase's intent to move users toward automated scaling or commitment-based pricing rather than hard usage caps Positioning & Messaging: - Removed FAQ question: 'Do I get a notification if I am approaching my usage limits?' - Added FAQ question: 'How can I track my usage?' - Shift from reactive notification model to proactive user-initiated tracking What to do: • Monitor Supabase's updated answer to the new FAQ question to understand their tracking/dashboard capabilities and whether this signals movement toward usage observability as a differentiator • Audit your own usage notification and tracking features-if you offer clearer alerts or more granular real-time limits, emphasize this in competitive positioning • Watch for follow-up pricing/plan changes that might accompany this messaging shift, as it could foreshadow a move toward consumption-based or tier-free pricing models