Feedback: What Should We Ship in 2026? - Railway Help Station

Lines often turn up in the wrong order making basic debugging impossible - especially when logging objects. I've tried to use formatted logs for my own console logs but it's still a nightmare and not ideal having to jump through hoops to work around Railway's bugs. When libraries (e.g. for environment variable validation) log warnings or reports in object format it's often unreadable on Railway because Railway logs everything in the wrong order. The 500 logs/sec limit is another Railway hoop (and what feels like a bug) to continually have to work around. If an error or something unexpected happens on my server to trigger this, I'm often unable to investigate it beacuse the logs arrive in the wrong order and I can't see the action that actually caused it as Railway may have deleted this due to the limit. Another basic logging / debugging use case that is extremely difficult in Railway. See screenshot: https://i.imgur.com/MnHCl8P.jpeg You can see my uptime monitoring ping comes through all sweet - and then 30 seconds later, random lines of logged objects start appearing in the wrong order and the 500/second log limit is reached. But you don't even get to see the first 500 logs, you don't get to see the first few lines of these logs to see what triggered it, you just see Railway's kinda buggy, out-of-order log delivery and then its "messages dropped" warning and you're left completely unable to perform basic debugging. So even if Railway is going to keep its 500/second log limit, it's implemented in a broken and buggy way. … marqmartiHOBBY ... The "vibe coding" movement is exploding, and by 2026, the primary bottleneck for developers won't be writing code, but managing its lifecycle on the move. We are already seeing tools like Cursor and Copilot optimize for mobile interfaces, allowing engineers to prompt and ship features from anywhere. However, Railway remains the missing link in that mobile-first workflow. To truly capture this new wave of developers, a native Android and iOS app is no longer just a "nice-to-have"—it’s a necessity for closing the loop between a mobile IDE and the production environment. ... Project-level IaC is the #1 feature preventing me from becoming a user of railway aarongainzPRO 12 days ago Focusing on the VM runtime upgrade. There are many cases of "high load" services that perform horribly within Railways opinionated runtime (restricted cgroup, limited tweaks to be made). … Some other limitations: - can't modify filedescriptor limits (stuck at 1000 on Railway, no permission to edit) We heard about the VM runtime in mid-2025, with rumours it would be in beta by EOY 2025. Still no updates on the progress there. Almost seems like it's not a focus anymore.