blog.railway.app

Our Inaugural Community Call Summary

Updated 4/17/2025

Excerpt

Our infra is now much more declarative, where we can scale to meet user demand much more gracefully than before. However, with all the improvements we made, it's becoming increasingly clear that we need to place much more work on our "bones" of the platform to support the more significant features that companies need. A good example is our much-discussed plans for private networking. Networking is something we think we can get right with an excellent user experience but requires a lot of plumbing within our back-end to enable customers on the platform. … Is Remote Shell on your roadmap? Especially for running `rails console` We know this is a sticking point for many Ruby and elixir developers. We will not support SSH in your application because it breaks the immutability principle when deploying your applications. What is the status of GitLab integration? Planned but no timeline. Much of the product is closely tied to GitHub's deployment flow and model. A lot of work will need to be done to disintermediate this. … What is the status of custom plugins/databases? ... We want to dogfood the ability to author interfaces for those integrations as much as possible. But unfortunately, custom anything on the platform is a pandora's box and will take a while. Figma famously took six years to release custom plugins, although we don't think we will take that long.

Source URL

https://blog.railway.app/p/community-call-wrap

Related Pain Points