Pricing and Packaging RFC
complete
D
David Banys
Railway is collecting community feedback for pricing and packaging updates.
As we deal with a surge in popularity, we've also been tightening the requirements to use free services in order to better align incentives with legitimate users and dissuade bad actors.
As we move to support deeper and more complex production applications, getting pricing and packaging "right" is a core concern. If we don't align incentives correctly, we risk confusing you, alienating you, or worse.
So we'd love your feedback! We want to know what you think about Railway pricing and packaging:
- What makes sense to you about current pricing? What doesn't?
- Where do you feel we could do a better job clarifying billing?
- What kind of pricing transparency would you like to see from your PaaS?
- How else can we better align incentives with you the user?
Thanks for your input!
Angelo Saraceno
complete
D
Dwayne Macgowan
I love current pricing. Some tools to avoid surprise spending would be great. For example putting a cap o how much a project can spend, or directly cap on resources it can use (memory&cpu).
Heiko Kanzler
Unfortunately, Railway is unpredictable on cost for me. I created a small project, one MySQL instance and a simple node app. Both only exist, not a single request over a long period and both have been teaching the top of the free tier in a snap. I immediately withdraw my developer package to avoid surprises on my card.
Anbarasu
Currently we receive only one bill for all the projects hosted in Account. It would be better if we can get invoice for every project.
Free 2 Members for Team Plan, by removing the 5 USD Credit would be nice.
It will help the small teams who won't be able to afford the Team Plan