20 days ago
Community discussion thread on the following roadmap update:
TL;DR
This year of Railway in this current shape brought real product wins, a million+ more users, but reliability stumbles that cost us customer trust.
We're embarking on a focused push built around earning that trust back and polishing the platform we've been describing. A lot of the work is already in, and there’s a lot more to come.
For the remainder of this quarter and next, we’re going to be focused on two key areas. Trust and the core product loop.
On the first part:
- We’re going to be rolling out our second-generation of Metal, our second-generation hardware platform, incorporating two years of learnings of running our own sites
- Bringing 4 new sites of datacenter capacity online
- Improving the backup experience
- Extending our Postgres offering to be more batteries included
- Hardening the edge against DDoS with our own native CDN and network infra
- We’re angling to work on ISO27001 for customers with even more sensitive compliance concerns
We're also going to build out more of the core product:
- Making the agentic Railway story elegant (sandbox primitive, remote MCP server, agents that can create templates) - watch this space
- Improving our frontends story with a real CDN
- Railway self-healing deploys
- A Templates renaissance with better discovery and supporting creators
- Improving the API experience via an SDK
- A more elegant IaC story
- Safer rollouts via feature flagging
- The mobile app hitting GA (We didn’t forget about you Android phone havers)
- Revamping the O11y experience
- Extending AI Guardrails to prevent greater destructive actions
Other highlights, which the Support and Solutions team have been hard at work on:
- A support agent in the Railway dashboard enters beta in Q2. We've also been revamping the response AI.
- Bridging all product feedback directly to the engineer who works on the feature. We call this Priority Boarding 2.
- We are also re-working our demo flow to make the buying experience that much, much, much better for companies. You can go from call to contract in 30 minutes.
- You will see a major investment in AEO for model discoverability (You’re welcome/sorry)
- Q2 2026 is the reliability foundation, Q3 2026 is the product loop maturing on top of it, Q4 2026 and into 2027 is when the production agent-native cloud becomes the default.
- We’re going to be looking into improving our pricing and packaging around the agent flow.
See the blog here: https://blog.railway.com/p/railway-summer-update-2026
8 Replies
13 days ago
zdzqdzqdzqdqd
12 days ago
"Extending our Postgres offering to be more batteries included"
Will this include the option to install pg_cron in the base image?
11 days ago
How about stop adding fluffer crap nobody asked for and add decent customer service like people are asking for
10 days ago
I'm sorry you feel that way, but we extend our customer service to everyone on the platform because we are genuinely interested to see how our customers are doing.
We also know the outages are the real complaint under a lot of those reviews. It's exactly what this quarter is built to fix, and the Metal and edge work is the bet we're making on it.
8 days ago
Honestly I'd like to see a total service reliability and infrastructure review on your roadmap based on your recent service outages/degradations.
7 days ago
Railway is the easiest platform for me to use, and I consider it a very complete solution right now. I'm very satisfied, but the constant service outages are making me think about migrating. I'd really prefer that all these problems be mitigated rather than have new features.
josegiufrida
Railway is the easiest platform for me to use, and I consider it a very complete solution right now. I'm very satisfied, but the constant service outages are making me think about migrating. I'd really prefer that all these problems be mitigated rather than have new features.
7 days ago
I totally agree! there are plenty features we need a more stable platform first
5 days ago
Heard. Reliability is the whole point of this update, not a footnote under the feature list, so let me say it plainly instead of leaving it buried. It's why we've been pushing on the eng blogs opening up how we operate the platform and the improvements we made there.



