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

   Railway

   FreeFree
2. Row 2
   GitHub

   Team$4/user/month

   Railway

   Hobby$5/mo
3. Row 3
   GitHub

   Enterprise$21/user/month

   Railway

   Pro$20/mo
4. Row 4
   GitHubNo tier at this position.

   Railway

   EnterpriseCustom

The entry tier

Changes we recorded

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

• Railway pricing page changed

  Railway·13 Nov 2026

• 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

• Railway introduces Sandboxes & VMs as a new product offering with per-second metering at $50/GB-month and $50/vCPU-month, removes Cloud Regions from Enterprise tier.

  Railway·8 Nov 2026

  Railway introduces Sandboxes & VMs as a new product offering with per-second metering at $50/GB-month and $50/vCPU-month, removes Cloud Regions from Enterprise tier. Why it matters: • Railway is expanding beyond traditional container deployment into infrastructure primitives (VMs/sandboxes), signaling a shift toward broader compute workloads and agent/code execution use cases that could capture workloads currently served by competitors like AWS Lambda or specialized VM providers. • The removal of Cloud Regions from Enterprise tier (now listed only as 'Higher Resource Limits') suggests Railway is either consolidating features or pricing strategy; competitors should clarify their own cloud region strategy and pricing transparency. • The sub-second metering model ($0.00001929 per GB/sec, $0.00001929 per vCPU/sec) and idle-only billing positioning is a direct cost-efficiency message; Railway is emphasizing pay-for-actual-use over wall-clock time, which could appeal to cost-conscious workloads. Product/Features: - New Sandboxes & VMs offering launched: isolated Linux VMs for agents, builds, and untrusted code execution. - Sandbox billing model: metered per second at $0.00001929 per GB/sec and $0.00001929 per vCPU/sec, approximately $50 per GB-month and $50 per vCPU-month for active use only. - Sandbox lifecycle features added: checkpoints, forks, templates, private networking, and public domains. - Idle timeout feature: configurable up to 5 minutes (default), up to 2 hours, or never, with automatic destruction of idle sandboxes. - Sandbox resource tiers: default 2 vCPU/2 GB, scaling to maximum 32 vCPU/32 GB per sandbox. Pricing: - Sandbox pricing: $50 per GB of memory per month and $50 per vCPU per month, metered per second, plus $0.05 per GB egress. - Pricing model emphasizes actual usage: customers pay only for CPU actually used and memory held while running, not for idle wall-clock time. Plans: - Enterprise tier: Cloud Regions removed from listed benefits; now shows 'Enterprise Support, Higher Resource Limits' plus prioritized support with SLOs, dedicated Slack Connect channel, and services with 48vCPU/48GB RAM per replica. Positioning: - Railway is positioning sandboxes as a cost-efficient alternative for waiting/idle workloads ('a sandbox waiting on a model or a user costs almost nothing'). - Emphasis on flexible, per-second metering and automatic cleanup (destroyed sandboxes cost nothing) versus traditional VM hourly billing. What to do: • Audit your own VM/sandbox offering (if any) and cost messaging: clarify whether you meter per-second or per-hour, and whether you charge for idle time. Railway's positioning on 'pay-only-for-active-use' is now a competitive liability if you don't match it. • Evaluate whether Railway's removal of Cloud Regions from Enterprise signals a pricing restructuring or de-emphasis; confirm your own multi-region story with customers and sales to prevent churn justifications. • Monitor Railway's Sandboxes adoption and feature velocity; if this becomes a revenue driver, assess whether your product roadmap should include similar compute-primitive offerings or deeper integrations with agent/LLM workflows that depend on untrusted code execution.

• Railway adds explicit usage-based pricing transparency and enterprise demo booking to pricing page

  Railway·3 Sept 2026

  Railway adds explicit usage-based pricing transparency and enterprise demo booking to pricing page Why it matters: • Railway is emphasizing pay-for-what-you-use cost predictability as a competitive differentiator, signaling confidence in their resource efficiency to undercut traditional flat-rate competitors • The addition of enterprise demo booking directly on the pricing page suggests they're optimizing conversion for high-value deals and moving away from pure self-serve positioning • New messaging around '0% idle cost' and 'only pay for active CPU/memory' indicates Railway is repositioning against competitors with wasteful resource billing or hidden charges Positioning: - Added explicit messaging: 'Only pay for active CPU and memory' (suggests focus on resource efficiency vs. competitors) - Added '0% idle cost' messaging (new value prop differentiator) Pricing: - Introduced or emphasized usage-based billing transparency with specific metrics (CPU/memory-based rather than generic 'compute credits') What to do: • Audit your own pricing model messaging-if usage-based, ensure it matches or exceeds Railway's transparency on what 'active' means and how costs scale • Review enterprise sales funnel: Railway's demo booking link suggests they're converting high-touch deals; ensure your enterprise onboarding process is equally frictionless • Test messaging that counters 'pay for idle time'-either highlight your own utilization efficiency or introduce usage-based tiers if you haven't already

• GitHub pricing page changed

  GitHub·3 Sept 2026

• Railway pricing page changed

  Railway·1 Sept 2026

• GitHub pricing page changed

  GitHub·28 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?