---
title: "Early Adopter EOL, Configurable Restart Policy, Nixpacks Default"
date: 2022-07-15T15:00:00.000+00:00
number: 0090
url: https://railway.com/changelog/2022-7-15
---

# Early Adopter EOL, Configurable Restart Policy, Nixpacks Default

Bring out the confetti, cake, and funeral procession. This changelog is a mix of emotions. 

## Early Adopter Plan End Of Life

[Image: Untitled]

We got some bad news. The Early Adopter plan is reaching end of life and will be removed in its entirety by August 1st. Those on the Early Adopter Plan received an email with details about it, but consider this our public announcement.

For those new(er) on our journey. The Early Adopter Plan ceased being offered on August 2021 and was slated for removal at that time. We took our sweet time removing it, and now its come.

As always at Railway, we won’t pull the rug on you. We will be dispersing enough credits for all of your projects to stay online for an additional month. Afterwards, accounts will transition into the Developer Plan with the prepaid payment method. 

We can’t overstate how thankful we are for those Railway believers, Railievers, if we will, for trusting us with their workloads since Day 1.

## Configurable Restart Policy

[Image: Untitled]

You asked! We listened. Infrastructure Engineer, Ahmed, traversed the plains of infra, service, and front-end to deliver configurable restarts.

Now, within the Service settings, a user is able to configure a restart policy of either `Never`, `Always`, or `On-Failure` with an optional maximum number of restarts. Additionally, we only restarted in the past to exit on a non-zero exit. With the new option, you can even change that behavior.

Predictable failure never looked so good.

## Nixpacks as Default

[Image: Untitled]

Nixpacks is now the default builder for all new services made on Railway. Barring a few hiccups with Ruby on Nixpacks we are seeing smooth sailing. Fun fact: Nixpacks on the platform has the lowest build failure rate vs. all other build methods, including raw Dockerfiles. This has only fed our (small) egos.

In addition: the older build methods are now marked as deprecated. They will remain in the service until we announce a transition plan for them. Don’t worry we won’t remove those options until we are 99.99 percent confident we can perform a cutover. Stay tuned. 

## Improvements and Fixes

- Say hello to Five! He is an Infrastructure Engineer who will help us kick things up a notch!
- We improved the PORT experience, now users will be warned if they miscapitalize the PORT var
- We have improved the way we discover Dockerfiles
- Fixed a lot of issues with Nixpacks in relation to C headers, the stuff you need for compiled languages. We now know too much about C headers.
- Various infra improvements to handle increased scale.