Developer tool pricing tracker

Render vs Vercel pricing

Both of these are in Developer tool, and we read both pricing pages the same way, with the same reader. Everything below is what each page printed on the day we read it. Render read on 13 Nov 2026, Vercel on 9 Nov 2026.

We check each page about once a week, so this is a weekly reading, not a live feed. Prices are copied as printed, never converted and never averaged.

The two pages

Vercel

Read on 9 Nov 2026
The last check of this page did not complete, so its figures are from an earlier read.

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
    Vercel
    HobbyFree
  2. Row 2
    Render
    Pro$25/mo
    Vercel
    Pro$20/mo
  3. Row 3
    Render
    Scale$499/mo
    Vercel
    EnterpriseCustom
  4. Row 4
    Render
    EnterpriseCustom
    VercelNo tier at this position.

The entry tier

Vercel is the cheaper of the two at the entry tier: $20/mo on Pro, against $25/mo on Pro. That is $5 less, 20 percent below Render.

Both figures are for the whole account, per month, so they are like for like. This is the cheapest paid monthly tier we can read on each page. Free tiers, quoted tiers and per-unit rates are left out, because none of those is a figure you can put next to another company's figure.

Changes we recorded

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

  • Render simplifies sandbox pricing presentation and removes per-instance features, shifting to workspace-level concurrency limits

    Render13 Nov 2026

    Render simplifies sandbox pricing presentation and removes per-instance features, shifting to workspace-level concurrency limits Why it matters: • Render is de-emphasizing isolated VM guarantees and indefinite runtime-suggesting sandbox positioning is moving away from long-running/stateful workloads toward ephemeral compute • The new concurrency limit model (1,000 default on Pro/Scale) introduces a new dimension of capacity gating that competitors should monitor for upsell/upgrade pressure patterns • Copy consolidation from 'microVMs' to 'VMs' and removal of '40 GB disk included' messaging simplifies positioning but may indicate less differentiation on resource guarantees Positioning: - Changed 'Isolated microVMs for agents, apps, and untrusted code' to 'Isolated VMs for agents' (narrower use case framing) - Removed 'Can run indefinitely' claim entirely - Removed '40 GB of disk included per sandbox' specification - Removed 'Pay only for the CPU you use' summary tagline Features & Limits: - Added new workspace-level limit: 'Default limit of 1,000 concurrent sandboxes on Pro, Scale workspaces' - Added 'Higher limits on request' with link to docs (introduces sales friction for scale) - Changed 'Automatic suspend and resume when idle' to 'Automatic suspend when idle' (removed resume mention) Pricing Presentation: - Reorganized CPU pricing table: separated 'active CPU hour' rate from memory provisioning rate into distinct columns for clarity - Memory pricing display changed from bundled format (e.g., '$0.038/hour for memory') to standalone column header 'provisioned memory' with same hourly rates - CPU rate remains $0.12/active CPU hour across all tiers (no change) - Memory rates unchanged: $0.038/hour (2GB), $0.076/hour (4GB), $0.152/hour (8GB), $0.304/hour (16GB) Navigation & UX: - Added jump links to pricing sections: workspace plans, compute pricing, FAQs (quality-of-life improvement) - Converted Spanish cookie/dialog copy to English (likely site-wide localization effort, not material to pricing strategy) What to do: • Audit your own sandbox/ephemeral compute messaging to ensure clarity on runtime guarantees and resource limits-Render's removal of 'indefinite' runtime suggests this is a differentiator if you support it • Monitor Render's sales patterns around the 1,000 concurrent sandbox cap over next 2-4 weeks; if they're converting upgrades at that threshold, consider your own concurrency/quota model • Review your memory pricing display for clarity-Render's table redesign suggests they heard friction on pricing comprehension; test your own pricing table UX with users

  • Vercel shifts from Edge Requests to CDN Requests model, introduces Flat Rate CDN, Vercel Drives, Daemons, and Backends; replaces per-GB overage billing with new pricing structures

    Vercel8 Nov 2026

    Vercel shifts from Edge Requests to CDN Requests model, introduces Flat Rate CDN, Vercel Drives, Daemons, and Backends; replaces per-GB overage billing with new pricing structures Why it matters: • Vercel is fundamentally restructuring its billing model away from usage-based Edge overage charges ($2 per 1M, $0.15 per GB) to a Flat Rate CDN option with traffic spike protection, reducing customer unpredictability and competitive risk on variable workloads • New product categories (Vercel Drives, Daemons, Backends, Vercel CI) expand the platform into data persistence, background jobs, and compute-moving beyond edge deployment and raising switching costs for customers • Removal of Session Tracing and Advanced Deployment Protection ($150/month) and changes to Speed Insights (now free with 10K events/team, paid add-on for overages) signal consolidation and repositioning of observability offerings Pricing & Billing Model: - Edge Requests pricing model completely removed (was: 10M/month included, then $2 per 1M overage; 1TB/month included, then $0.15 per GB) - New Flat Rate CDN introduced as alternative to usage-based CDN billing on Pro plan, advertised as fixed monthly price with traffic spike protection and no overages - CDN Requests metric introduced (Included in Flat Rate CDN) - Tracing Spans pricing added: 1M span units/month included, then $0.50 per 1M span units (replaces prior Session Tracing with 1 hour/1 day of traces) - Trace Retention changed to 14 days of traces (was: 1 day of traces in one tier) - Speed Insights Plus Events pricing changed to $20 per 1M events (was: $20 per 1M for Edge Requests; now separate add-on) Plans & Features Removed: - Session Tracing feature removed entirely - Advanced Deployment Protection ($150/month) removed - Speed Insights Plus Events no longer built-in to plans New Products & Features Added: - Vercel Drives: Drive Storage 15 GB lifetime included, then $0.05 per GB-month; Drive Reads 30 GB/month included, then $0.0015 per GB; Drive Writes starting at $0.004 per GB - Vercel Daemons: Active CPU and Provisioned Memory tiers added - Backends product category introduced - Vercel CI: 200 CPU minutes/month included - Deployment Storage: 10 GB included - Marketplace Integrations added - Custom Monitors: $0.0035 per GB scanned - Password Protection: $20/project/month Observability & Monitoring: - Speed Insights repositioned as Free tier with 10K events/team/rolling 30 days - Speed Insights Plus Events now available as paid add-on (pricing structure changed) - Tracing Spans introduced as managed feature with 1M span units/month included, $0.50 per 1M overage Positioning & Messaging: - FAQ section added: 'What is Flat Rate CDN?' with explanation of fixed pricing, spike coverage, and no-overages value prop - Copy shift from 'Edge Requests' terminology to 'CDN Requests' throughout - Detailed caching/compression explanation retained but updated to reference CDN Requests instead of Edge Requests What to do: • Audit your own CDN and overage billing model: if you charge per-request or per-GB with variable overages, Vercel's Flat Rate CDN is now a direct competitive threat. Evaluate offering a predictable tier or capping overage costs • Assess whether your observability stack (Speed Insights, tracing, session replay) can compete with Vercel's expanded free Speed Insights + paid add-on model; determine if you need feature parity or differentiation in monitoring/debugging • Map Vercel's new products (Drives, Daemons, Backends, CI) against your platform capabilities-these are land-and-expand vectors. Prioritize blocking the most dangerous combination (e.g., Drives + Daemons for stateful workloads) or lean into areas you own

  • Render restructures database pricing with storage-inclusive tiers, introduces Sandboxes product, and significantly raises high-end instance pricing

    Render8 Nov 2026

    Render restructures database pricing with storage-inclusive tiers, introduces Sandboxes product, and significantly raises high-end instance pricing Why it matters: • Render is repositioning database as a managed service with predictable storage costs (bundling 256 MB-50 GB storage per tier) rather than compute-only, making direct price comparison more complex and potentially advantageous for their mid-market positioning • New Sandboxes product (microVMs for agents/untrusted code at $0.12/CPU hour + memory) is a greenfield offering targeting AI agent and edge workload use cases-a new competitive surface outside their traditional developer infrastructure • Pricing floor moves up on database instances (Standard CPU $10→$10 at 256MB, but new $20 tier at 1GB replaces old $32 tier at 1GB), while max scale jumps from 40GB/10GB RAM to 50GB/32GB RAM-positioning them higher in the infrastructure stack Pricing & Plans: - Database instances now include storage bundled per tier (256 MB-50 GB storage depending on plan), displayed in new column - Standard CPU $10/month: RAM unchanged at 256 MB, but connections drop from 250 to 200; now includes 256 MB storage - Standard CPU $20/month: NEW tier, 1 GB RAM (replaces old $32/month tier which had 1 GB RAM) - Standard CPU $32/month → $60/month: RAM increases from 1 GB to 3 GB, storage 3 GB included, connections rise from 1,000 to 3,000 - Standard CPU $135/month → $100/month: RAM decreases from 5 GB to 5 GB (unchanged), but price drops; storage 5 GB included, connections drop from 5,000 to 5,000 - Standard CPU new $200/month tier: 10 GB RAM, 10 GB storage, 10,000 connections (replaces old $250/month High CPU tier which had 10 GB RAM) - High CPU $250/month → $350/month: RAM increases from 10 GB to 20 GB, storage 20 GB included, connections rise from 10,000 to 20,000 - High CPU $550/month → $600/month: RAM increases from 20 GB to 40 GB, storage 40 GB included, connections rise from 20,000 to 20,000 - High CPU new $750/month tier: 50 GB RAM, 50 GB storage, 50,000 connections (maximum scale cap increased from 40 GB to 50 GB) - Task compute: new $2.50/hour tier added for 8 CPU, 32 GB RAM - Database max scale increases from 40 GB RAM to 50 GB RAM; compute max scale increases from 4 CPU/16 GB RAM to 8 CPU/32 GB RAM New Product: - Sandboxes (beta): new isolated microVM offering for agents, apps, untrusted code - Sandboxes pricing: $0.12/active CPU hour + memory-based rate ($0.038-$0.304/hour depending on configuration); up to 8 CPU, 16 GB RAM per instance - Sandboxes features: indefinite runtime, automatic suspend/resume when idle, 40 GB disk included, pay-per-active-CPU model, snapshot storage at $0.08/GB per month - Sandboxes plan tiers include concurrent sandbox limits (100 default up to 5,000-10,000 on request) and task compute increments (10,000 CPU/40,000 GB RAM base) Features: - Database: 'Dedicated technical account manager' changed to 'Dedicated technical account team' - Database: 'Logical backup' changed to 'Logical exports' for paid instances - Database: new 'Connection pooling' feature added - Database support for 'Free(limitations apply)' tier now explicitly includes 50 connections (previously shown without connection count) Removed Content: - Migration credits offer ($10K cap) removed entirely - Migration credits application link removed - Direct navigation links to workspace plans, compute pricing, FAQs removed from main copy What to do: • Conduct detailed cost-comparison modeling across 5-50 GB RAM range: Render's storage bundling and tiered restructuring may make them appear cheaper on mid-market workloads; identify pricing positioning gaps for your own database product • Assess Sandboxes as a competitive threat in AI/agent infrastructure: their $0.12/CPU hour + memory model targets a different buyer persona (ML/automation platform builders) than traditional app hosting-evaluate whether to expand your own serverless compute or agent-adjacent offerings • Audit your own feature parity on managed database features (logical exports, connection pooling, dedicated account teams) and messaging around support tier upgrades, as Render is bundling these more aggressively into paid plans

  • Vercel introduces per-minute pricing for Basic machine compute, starting at $0.007/min, expanding infrastructure monetization

    Vercel3 Sept 2026

    Vercel introduces per-minute pricing for Basic machine compute, starting at $0.007/min, expanding infrastructure monetization Why it matters: • Vercel is now monetizing granular compute resources that were previously bundled into plans, establishing a new revenue stream and potentially raising TCO for customers running baseline workloads • This represents a shift toward infrastructure-as-you-go pricing beyond traditional seat/plan models, which could impact competitive positioning if customers perceive hidden costs or usage uncertainty • The entry point of $0.007/min creates new pricing complexity that competitors should clarify in their own pricing communication to avoid customer confusion or dissatisfaction Pricing: - New compute billing introduced: Basic machines at $0.007 per minute (exact prior pricing unknown from diff, but this is a new line item) Plans: - Basic machines now explicitly listed as 'Included' in a plan tier, suggesting tiered access or quota-based compute allocation Positioning: - Shift toward consumption-based pricing for infrastructure resources, moving beyond flat-rate plan tiers toward granular pay-as-you-go for compute What to do: • Audit own pricing strategy: determine whether bundled compute limits or transparent per-minute billing is clearer and more competitive for core customer segments • Prepare customer comms addressing compute costs and limits-if Vercel's per-minute model creates sticker shock, emphasize predictability of your own pricing model • Monitor Vercel's adoption metrics and customer churn post-launch to validate whether consumption-based pricing drives upsell or customer friction

  • Render pricing page adds Spanish language support for EU/LATAM market expansion.

    Render3 Sept 2026

    Render pricing page adds Spanish language support for EU/LATAM market expansion. Why it matters: • Indicates expansion beyond English-speaking markets, potentially signaling growth into Spanish-speaking regions (EU, LATAM). • May reflect increased international customer base or strategic localization push to compete globally. • No pricing or plan changes detected-purely a UX/localization enhancement. Localization: - Added Spanish translations for cookie consent dialog and privacy messaging. - Existing English content preserved; no removal of English language option. - No changes to pricing structure, plan names, features, or terms detected. What to do: • Monitor Render's localization roadmap-check if additional languages roll out to assess geographic expansion priorities. • Audit your own pricing page localization strategy; ensure parity or leadership in key markets Render is targeting. • Watch for any regional pricing adjustments or market-specific promotions that may follow this language addition.

  • Vercel pricing page changed

    Vercel2 Sept 2026
  • Render pricing page changed

    Render1 Sept 2026
  • Render pricing page changed

    Render29 Aug 2026
  • Vercel pricing page changed

    Vercel27 Aug 2026
  • Render pricing page changed

    Render26 Aug 2026
  • Vercel pricing page changed

    Vercel25 Aug 2026
  • Render pricing page changed

    Render23 Aug 2026
  • Vercel pricing page changed

    Vercel22 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.

    Render21 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

    Render18 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

  • Vercel rebrands Edge Config to Global Config across all pricing tiers

    Vercel17 Aug 2026

    Vercel rebrands Edge Config to Global Config across all pricing tiers Why it matters: • Positioning shift suggests Vercel is broadening the perceived scope of this feature beyond edge-specific use cases to appeal to broader infrastructure needs • Renaming may indicate feature maturation and expansion-competitors should audit whether their own edge/global config offerings are sufficiently differentiated • The terminology change ('Global' vs 'Edge') could influence buyer perception of feature capabilities and use-case applicability in competitive evaluations Features: - Edge Config renamed to Global Config - Edge Config Reads renamed to Global Config Reads - Edge Config Writes renamed to Global Config Writes What to do: • Audit competitive positioning of your own configuration management features-ensure messaging clarity around edge vs. global scope to differentiate from Vercel's repositioning • Monitor whether Vercel expands Global Config capabilities post-rebrand (read/write limits, latency SLAs, integrations) that could affect feature parity claims • Update internal battlecards and sales materials to address the rebrand in customer conversations to prevent confusion during competitive deals

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

    Render15 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.

The two pages were read on different days, Render on 13 Nov 2026 and Vercel on 9 Nov 2026, so the figures above are not one moment. Prices are copied as printed, never converted and never averaged, and a vendor can change a page any time after we read it. Open both pricing pages before you act on any of this. More Developer tool comparisons, or the dataset behind all of it.

Watch both of these yourself

Tierpeek runs this same read on any pricing page you paste below, every 8 hours, and sends what moved to your inbox or Slack.

Free for 3 days, no card. Or create an account first and add pages from the dashboard.