station.railway.com
Tell us your Railway wish for 2025Q1 - Railway Help Station
Excerpt
The tokens are bound to individual accounts or teams, limiting the flexibility required for a reseller managing several clients. With a cap of 1000 requests per hour, the API’s rate limiting may not be sufficient for the higher demands typical in a reseller setup. The API’s endpoints and schema are optimizzed for a single tenant’s use, rather than providing a multi-tenant framework that resellers require. … Replicating everything from scratch would take over 6-12 months, whereas you lot already have endpoints for deploying templates and GitHub repositories. ... This would be super useful for debugging.- Lazy loading / performance improvements to template search in the UI. It hurts to wait 3-4 seconds on a $2500 machine to search for a template. I'm willing to bet react-window or some paging would solve the lag without significant work on y'alls end.brodyEMPLOYEE … ... In my case, we have it configured so that in the dev/qa environment, which is only used during the workday, it doesn't consume unnecessary resources overtime. However, when I develop, it often takes me more than 10 minutes to make a new request, and it's a bit annoying having to restart the service every 15-20 minutes.
Related Pain Points
API rate limiting insufficient for reseller use cases
7Railway's API is rate-limited to 1000 requests/hour and tied to individual accounts or teams, making it inadequate for resellers managing multiple clients. The API schema is also optimized for single-tenant use rather than multi-tenant operations.
Long local development compile-deploy-restart cycle (5+ minutes)
7Developers must compile class files, replace them in .ear archives, and restart application servers like Tomcat, with the entire cycle taking approximately 5 minutes. This blocks iteration and makes debugging frustrating compared to hot-reload capabilities in other languages.
Slow template search UI causing developer friction
3The template search feature in the Railway UI has poor performance, taking 3-4 seconds to search on reasonably powerful machines, causing unnecessary delays during project initialization.