2 months ago
Hello. I would like to choose the best plan for my project. Requirements:
1. A Frontend Server and an API Server
2. A Supabase DB that is connected via ipv6 (you support it, correct?)
3. A private access for QA team
4. A public access for a specific endpoint - Stripe webhook
As I understand, the Hobby Plan will give me 5 USD for my account that will expire quickly. The service will cost me at least 20 USD. So I can subscribe to Pro and the price would be the same, is it true?
Pinned Solution
2 months ago
you're right, railway did add outbound ipv6 support check this : https://railway.com/changelog/2026-02-27-smart-diagnosis . it's currently in priority boarding (railway's early access program) and it's opt-in , you have to enable it per service in your service settings. once enabled, your service can reach external ipv6 addresses like supabase. inbound connections still use ipv4, only outbound is affected.
on your cost questions: yes your math is correct. hobby = $5 fee + $35 overage = $40. pro = $20 fee + $20 overage = $40. same total. but resources are not rigid , railway charges by the minute based on actual usage. if your qa environment is mostly idle with no traffic, real usage will be way below 1gb ram / 0.5 vcpu 24/7, so your actual bill will likely be much lower than $40. the $40 is a worst case assuming full resources running all month.
and yes pro is better value here, same cost at your usage level but you get team workspace access when your qa team grows, plus smtp support and other pro-only features.
honestly in general railway is just the better platform, the pricing model is fairer, you only pay for what you actually use, the dx is cleaner, and they're shipping features like outbound ipv6 that other platforms like render.com still haven't caught up on. easy choice
I hope this help you :)
3 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Hello, heres an answers to clarify for your setup:
plan: you need pro, not hobby. hobby doesn't support team workspaces so your qa team can't get access at all. pro is $20/mo and that $20 subscription fee includes $20 of usage credit, so if your actual resource usage stays under $20 you just pay the flat $20. matches your estimate.
supabase via ipv6: this won't work. for my information (not sure if there is some update) railway does not support outbound ipv6 https://docs.railway.com/networking/outbound-networking. any outbound ipv6 request will fail with "network is unreachable". you need to connect to supabase using an ipv4 connection string instead
stripe webhook public access: railway exposes the entire service publicly when you add a domain, not just a single endpoint. if you want only the stripe webhook route to be accessible and everything else locked down, that logic needs to be handled inside your app code (e.g. return 401 on all other routes), not at the railway platform level.
I hope this help you :), let me know if you need more explanation
domehane
Hello, heres an answers to clarify for your setup: plan: you need pro, not hobby. hobby doesn't support team workspaces so your qa team can't get access at all. pro is $20/mo and that $20 subscription fee includes $20 of usage credit, so if your actual resource usage stays under $20 you just pay the flat $20\. matches your estimate. supabase via ipv6: this won't work. for my information (not sure if there is some update) railway does not support outbound ipv6 <https://docs.railway.com/networking/outbound-networking>. any outbound ipv6 request will fail with "network is unreachable". you need to connect to supabase using an ipv4 connection string instead stripe webhook public access: railway exposes the entire service publicly when you add a domain, not just a single endpoint. if you want only the stripe webhook route to be accessible and everything else locked down, that logic needs to be handled inside your app code (e.g. return 401 on all other routes), not at the railway platform level. I hope this help you :), let me know if you need more explanation
2 months ago
Thank you for clarifying. I got the answer for the team. Let's assume I will be the only QA for now.
Cost calculation for my QA environment (no traffic expected):
Using Railway's pricing:
- Memory: $0.00000386/GB-sec or 1GB for 30 days = $10
- CPU: $0.00000772/vCPU-sec or 0.5 vCPU for 30 days = $10
- Total per service: $20/month
I need 2 services (Frontend + API) = $40/month usage.
Questions:
- With Hobby ($5 + $5 credits), I'd pay $40 total ($5 fee + $35 excess). Correct?
- With Pro ($20 + $20 credits), I'd also pay $40 total. Is Pro better value here (unlimited seats for QA team)?
Or the resources are not rigid and are calculated based on workload?
Note that recently I received an email that said that Railway now supports ipv6. That's the reason I prefer it over Render.com.
2 months ago
you're right, railway did add outbound ipv6 support check this : https://railway.com/changelog/2026-02-27-smart-diagnosis . it's currently in priority boarding (railway's early access program) and it's opt-in , you have to enable it per service in your service settings. once enabled, your service can reach external ipv6 addresses like supabase. inbound connections still use ipv4, only outbound is affected.
on your cost questions: yes your math is correct. hobby = $5 fee + $35 overage = $40. pro = $20 fee + $20 overage = $40. same total. but resources are not rigid , railway charges by the minute based on actual usage. if your qa environment is mostly idle with no traffic, real usage will be way below 1gb ram / 0.5 vcpu 24/7, so your actual bill will likely be much lower than $40. the $40 is a worst case assuming full resources running all month.
and yes pro is better value here, same cost at your usage level but you get team workspace access when your qa team grows, plus smtp support and other pro-only features.
honestly in general railway is just the better platform, the pricing model is fairer, you only pay for what you actually use, the dx is cleaner, and they're shipping features like outbound ipv6 that other platforms like render.com still haven't caught up on. easy choice
I hope this help you :)
Status changed to Solved brody • 2 months ago