Happy Friday! This week, we have been hard at work implementing some features to support the upcoming pricing changes. Let’s dive in!

TL;DR - We added a new page dedicated to making it easier to understand when you qualify for the free plan and when you may need to provide more proof of humanity.

Railway has one of the most generous free plans out there, and some times people ask us: “Well… how do you make money?”. We charge for usage, but you knew that, part of it is being cost effective to run. 

As a result, we try our best to clamp down on spam workloads and make sure people take “only one candy bar” so others can enjoy the platform. We use account verification to prevent multi-accounting and abuse to keep our free plan, well, free.

If we do our jobs right, we can convince companies to jump on the platform and have private hobby workloads co-existing alongside. However, the existing rule set was hard to understand. 

 Now theres a single place to see where you stand without you being left in the dark. 

We know that there are students learning to code and we are working on additional methods to support them. Thats coming at a later time. In the meantime we added…

Now we have allowed you to attach a card to your account if your GitHub doesn’t meet certain standards. Keep in mind, this will not charge your credit card and you will still be subject to the free plan limits. We hope this is a good step moving forward for those who want to trial Railway.

We have now set TLS 1.2 and above by default. We set this safeguard protect our users against a set of common exploits from older versions. Older browsers that don’t support TLS 1.2 and above will not work with Railway.

Our Bounty system thus far has been a success and we are pleased to announce that v0.1.0 of NixPacks will be ready for release next week. It includes the following (stable) language providers:

This means that NixPacks have reached the same language support as CloudNative Buildpacks with no need to change your existing program’s behavior. We have built enough confidence where we can cut it over to be the default build system next week. Thank you again to all contributors and testers who made this possible.

We welcome Ahmed, a new Infrastructure Engineer to our team!

We have removed support for TLS 1.0 and 1.1

https://res.cloudinary.com/railway/image/upload/v1655509446/docs/verification_qmmpw2.png

New Verification Flow, TLS Improvements, NixPacks Parity

Changelog #0086