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

   FreeFree

   Supabase

   FreeFree
2. Row 2
   Railway

   Hobby$5/mo

   Supabase

   Pro$25/month
3. Row 3
   Railway

   Pro$20/mo

   Supabase

   Team$599/month
4. Row 4
   Railway

   EnterpriseCustom

   Supabase

   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

• Cosmetic update to Supabase pricing page with image asset refresh only.

  Supabase·12 Nov 2026

  Cosmetic update to Supabase pricing page with image asset refresh only. Why it matters: • No material pricing, plan, or feature positioning changes detected. • Asset URL parameters updated but feature set and messaging remain identical. Assets: - Image asset URLs refreshed with new deployment parameter IDs (dpl_4HXRJyc7qCRke5wT35RvvbvQPbqy → dpl_GyHpMftaZW7jy7HQxu5ELJzRrEN4) - Custom Domain and Point in Time Recovery feature illustrations and descriptions unchanged in content What to do: • No competitive response required; monitor for substantive pricing or feature changes on next update.

• Supabase removes event banner and adds AI tools section to pricing page; Pro plan pricing unchanged at $25.

  Supabase·8 Nov 2026

  Supabase removes event banner and adds AI tools section to pricing page; Pro plan pricing unchanged at $25. Why it matters: • Event promotion removal suggests Select 2026 conference concluded or is de-emphasized in their go-to-market calendar. • Addition of 'AI tools' section signals Supabase is repositioning pricing page as a content hub with AI-assisted discovery features. • No material pricing, plan structure, or feature changes indicate stable positioning with focus on UX/engagement rather than commercial moves. Page Structure: - Removed 'Supabase Select 2026' event banner and call-to-action to register. - Added 'AI tools' section with links to ChatGPT and Claude for pricing inquiry assistance. - Added top-level navigation buttons: 'Sign in' and 'Start your project' in header. Pricing: - Free plan: $0/month - unchanged. - Pro plan: From $25/month - unchanged from prior version. - Team plan: $599/month - confirmed in visible content. Positioning: - Core tagline remains: 'Predictable pricing, designed to scale'. - Value proposition copy unchanged across all three tiers. What to do: • Monitor Supabase's Select 2026 event outcome and sponsorship strategy-if event is de-prioritized, assess whether their enterprise/community engagement is shifting. • Test Supabase's new AI-assisted pricing discovery UX to evaluate if it impacts conversion or customer education; compare against your own pricing page clarity. • Continue tracking Pro and Team plan pricing quarterly; no movement here suggests Supabase is holding on pricing discipline despite potential cost pressures.

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

• No material pricing or feature changes detected-cosmetic markup updates only

  Supabase·9 Sept 2026

  No material pricing or feature changes detected-cosmetic markup updates only Why it matters: • The diff contains only encoded/obfuscated markup with no readable content changes to pricing, plans, or features • Unable to assess competitive positioning shifts without clear, legible source data Markup & Formatting: - Diff contains non-standard character encoding/obfuscation (curly braces, brackets, angle brackets) with no translatable content - No readable pricing figures, plan names, or feature descriptions present in diff - Cannot confirm any changes to Supabase's pricing page structure or content What to do: • Request a clean, readable diff of the Supabase pricing page (HTML, JSON, or plain text) • Re-submit analysis once source material is legible and parseable

• 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

• No material changes detected-unrecognizable diff content suggests formatting noise or encoding artifact.

  Supabase·3 Sept 2026

  No material changes detected-unrecognizable diff content suggests formatting noise or encoding artifact. Why it matters: • The diff appears to be corrupted or non-human-readable markup rather than substantive pricing or feature changes. • Unable to assess competitive positioning shifts without valid page content. Data Quality: - Diff content is garbled markup with no identifiable pricing, feature, copy, or positioning information. What to do: • Re-run the page capture or diff generation to obtain valid, readable content before competitive analysis can proceed.

• Railway pricing page changed

  Railway·1 Sept 2026

• Supabase pricing page changed

  Supabase·1 Sept 2026

• Supabase pricing page changed

  Supabase·29 Aug 2026

• Supabase pricing page changed

  Supabase·27 Aug 2026

• Supabase pricing page changed

  Supabase·26 Aug 2026

• Supabase pricing page changed

  Supabase·23 Aug 2026

• 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