Netlify 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
   Netlify

   Free$0

   Railway

   FreeFree
2. Row 2
   Netlify

   Personal$9/month

   Railway

   Hobby$5/mo
3. Row 3
   Netlify

   Pro$20/month

   Railway

   Pro$20/mo
4. Row 4
   Netlify

   EnterpriseCustom

   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

• Netlify simplifies pricing display by removing tiered pricing variants ($12, $15, $25 options) and consolidating to single-tier pricing ($9 and $20/month).

  Netlify·11 Nov 2026

  Netlify simplifies pricing display by removing tiered pricing variants ($12, $15, $25 options) and consolidating to single-tier pricing ($9 and $20/month). Why it matters: • Netlify is reducing pricing complexity and potentially signaling a shift away from usage-based or tier-based billing variants toward simpler fixed pricing • The removal of higher-tier price points ($12, $15, $25) suggests Netlify may be standardizing its billing model or preparing for future pricing restructuring • Competitors should monitor whether this is a permanent simplification or a transition step, as it could indicate changes to how Netlify packages features or seats across teams Pricing: - Removed tiered pricing options: $9/$12/$15/month for 1 member (now single $9/month) - Removed tiered pricing options: $20/$20/$25/month for unlimited members (now single $20/month) - Pricing display now shows only baseline rates without variant options visible on main pricing page Positioning: - Price structure simplified from multi-tier to single fixed price per plan tier - Member pricing remains conceptually the same (1 member vs unlimited) but variant pricing tiers have been consolidated What to do: • Analyze Netlify's billing dashboard to understand if the $12, $15, $25 variants still exist as hidden tiers or regional pricing, or if they've been fully deprecated • Review your own pricing complexity-if your competitor is simplifying, consider whether customers perceive your tiered pricing as confusing and whether you should follow suit • Monitor Netlify's next pricing communication to confirm whether this is a permanent simplification or a UI-only change hiding backend complexity

• Netlify pricing page changed

  Netlify·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.

  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

• Netlify pricing page changed

  Netlify·3 Sept 2026

• Railway pricing page changed

  Railway·1 Sept 2026

• Netlify pricing page changed

  Netlify·31 Aug 2026

• Netlify pricing page changed

  Netlify·29 Aug 2026

• Netlify pricing page changed

  Netlify·26 Aug 2026

• Netlify pricing page changed

  Netlify·23 Aug 2026

• Netlify shifts enterprise CTA from generic 'Contact Sales' to specific 'Book a demo' on pricing page.

  Netlify·20 Aug 2026

  Netlify shifts enterprise CTA from generic 'Contact Sales' to specific 'Book a demo' on pricing page. Why it matters: • Suggests Netlify is optimizing sales funnel for faster enterprise deal velocity-moving toward self-service demo scheduling rather than open-ended inquiries. • CTA change indicates they may be seeing better conversion rates on demo booking, a signal of matured sales processes for larger deals. Positioning & Sales Motion: - Removed 'Contact Sales' link (generic inquiry) - Added 'Book a demo' link with specific demo-pricing-enterprise tracking parameter - Implies shift toward structured, demo-first sales engagement for enterprise prospects What to do: • Audit your own enterprise CTA performance; test whether 'book a demo' outperforms 'contact sales' on your pricing page. • Monitor Netlify's demo booking flow to understand their enterprise qualification and sales cycle improvements.

• Netlify pricing page updated with cosmetic reCAPTCHA verification image changes only.

  Netlify·18 Aug 2026

  Netlify pricing page updated with cosmetic reCAPTCHA verification image changes only. Why it matters: • No material pricing, plan structure, or feature changes detected. • Competitor positioning and go-to-market strategy remain unchanged. • No immediate competitive threat or opportunity signal from this update. Cosmetic Updates: - reCAPTCHA verification image set changed from 'bus' to 'crosswalks' prompt-purely UI refresh with no functional impact. What to do: • No immediate action required; continue monitoring Netlify's pricing page for material changes to plans, pricing tiers, or feature positioning. • Focus competitive intelligence efforts on more substantive product or pricing shifts rather than verification UI updates.

• No material changes to Netlify pricing page detected; reCAPTCHA verification prompts refreshed.

  Netlify·16 Aug 2026

  No material changes to Netlify pricing page detected; reCAPTCHA verification prompts refreshed. Why it matters: • This is a routine security/anti-bot measure refresh with no pricing, plan, or feature implications. • No competitive threat or strategic shift to monitor. Security: - reCAPTCHA verification image set updated (cars → bus prompt rotation) What to do: • No action required; continue normal competitive monitoring.