GitHub vs Vercel 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
   GitHub

   FreeFree

   Vercel

   HobbyFree
2. Row 2
   GitHub

   Team$4/user/month

   Vercel

   Pro$20/mo
3. Row 3
   GitHub

   Enterprise$21/user/month

   Vercel

   EnterpriseCustom

The entry tier

Changes we recorded

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

• GitHub repositions pricing around Copilot and restructures plan messaging from feature-based to AI-first positioning

  GitHub·8 Nov 2026

  GitHub repositions pricing around Copilot and restructures plan messaging from feature-based to AI-first positioning Why it matters: • GitHub has made Copilot-integrated AI development central to all paid tiers, not optional add-ons, signaling that AI-assisted coding is now table-stakes for developer platforms • The rebrand from 'Team' and 'Enterprise' to outcome-focused tiers ('Advanced collaboration', 'AI-powered development, governed at enterprise scale') signals a strategic shift toward AI-first competitive positioning • Removal of trial offer for Free/Team plans and emphasis on Enterprise 30-day trial suggests GitHub is consolidating sales motion toward higher-ACV enterprise deals with AI bundled in Positioning & Messaging: - Hero headline shifted from 'Try GitHub, the complete developer platform' to 'Try the Copilot-powered platform', centering AI as primary value prop - Plan names de-emphasized in favor of outcome-based descriptions: Team tier now 'Advanced collaboration for individuals and organizations'; Enterprise now 'AI-powered development, governed at enterprise scale' - Enterprise plan description changed to emphasize governance at scale rather than security/compliance as lead message Pricing: - Free plan: $0 USD per user/month (unchanged) - Team plan: $4 USD per user/month (unchanged) - Enterprise plan: $21 USD per user/month (unchanged) - All pricing remains stable; no increases detected Features & Bundling: - GitHub Copilot access now explicitly listed as core feature in Enterprise tier ('Everything from Team, plus: GitHub Copilot access') - GitHub Codespaces Access moved to Free tier as included feature (previously positioned as upgrade-worthy feature for Team) - New Enterprise features added: Agent governance, Premium Support (with SLA tiers of 30-min Urgent response and 24/7 support) - Secret Protection and Code Security repositioned from Team add-ons to core Team differentiators Add-on Products & Pricing: - Explicit pricing tiers now shown for standalone products: GitHub Copilot (free tier with up to 2,000 completions/month), Codespaces ($0.18/hr compute, $0.07/GB storage), Git Large File Storage ($5/month for 50GB) - New product surfaces: GitHub sandbox (Copilot agent workflows in isolated environments) and GitHub Code Quality (maintainability/reliability fixes) - Premium Support now segmented into Premium (30-min SLA on Urgent) and Premium Plus (assigned CRE) as Enterprise upsells Promotional & Trial Strategy: - Removed standalone Free plan promotional language ('Join for free', 'free forever messaging) - Added 'Compare plans' link alongside trial CTA to drive consideration of higher tiers - GitHub Universe 2026 banner added, driving traffic to product announcements; suggests launch momentum behind new positioning What to do: • Audit your own AI feature positioning: if Copilot inclusion is now table-stakes in GitHub's mid-market and enterprise sales, determine whether your platform can credibly compete without AI-native coding assistance bundled, or pivot messaging to AI augmentation as complementary rather than core • Stress-test your compliance and governance story on enterprise deals: GitHub's repositioning of Enterprise around 'governance at scale' for AI agents signals enterprises will demand auditability and control-validate whether your enterprise offering addresses this gap • Revisit your add-on monetization strategy: GitHub is disaggregating Copilot, support, and security into explicit SKUs with published pricing, suggesting customers expect transparency and optionality; review whether your bundling strategy is defensible or whether unbundling would improve attach rates

• 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

  Vercel·8 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

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

  Vercel·3 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

• GitHub pricing page changed

  GitHub·3 Sept 2026

• Vercel pricing page changed

  Vercel·2 Sept 2026

• GitHub pricing page changed

  GitHub·28 Aug 2026

• Vercel pricing page changed

  Vercel·27 Aug 2026

• Vercel pricing page changed

  Vercel·25 Aug 2026

• Vercel pricing page changed

  Vercel·22 Aug 2026

• GitHub adds interactive pricing calculator to help customers estimate costs based on custom usage

  GitHub·20 Aug 2026

  GitHub adds interactive pricing calculator to help customers estimate costs based on custom usage Why it matters: • Reduces friction in sales cycle by enabling self-service cost estimation before contacting sales, likely improving conversion rates for larger deals • Signals confidence in pricing model and transparency, positioning GitHub as more accessible than competitors with opaque enterprise pricing • Makes per-user/per-action pricing easier to understand, reducing objections from customers concerned about unpredictable costs at scale Positioning: - Added prominent link to interactive pricing calculator on main pricing page - Emphasizes self-service, transparent cost estimation as core value proposition What to do: • Audit your own pricing transparency-if you lack a calculator or cost estimator, build one immediately to match this UX standard • Analyze whether your pricing model is simpler or harder to understand than GitHub's calculator output; adjust positioning accordingly • Test customer perception: do prospects convert faster with transparent calculators vs. sales-gated pricing?

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

  Vercel·17 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