---
title: "Multiple Provider Support, Accessibility Improvements, Heroku Compatibility"
date: 2022-11-11T15:00:00.000+00:00
number: 0107
url: https://railway.com/changelog/2022-11-11-multiple-provider-support
---

# Multiple Provider Support, Accessibility Improvements, Heroku Compatibility

Happy Friday! Reminder: [Heroku Buildpacks are going away](https://help.railway.app/product/jaSz4hRjYPgFuJewWQMKVh/heroku-buildpacks-deprecation/fk1FNrDxav9QzKQZ2FSsAk) **Monday, November 14th.** Thats the last we will say about that! Now, let’s move on to this week’s features!

## Multiple Provider Support: Priority Boarding

[Image: Untitled]

For [Priority Boarding](https://docs.railway.app/reference/priority-boarding) users we’ve added the ability to define multiple Nixpacks providers in a single build. This comes in handy when calling code from different runtimes. It’s now easier than ever to create a service with Python and Node compatibility, or Rust and Go compatibility — or any other combination you can dream up. (WASM FTW!)

Previously, the suggested workflow was to create a custom Dockerfile to pull in language runtimes, install them, and *only then* get your code to do the thing you wanted it to do. No longer.

You can now [specify an array of providers](https://nixpacks.com/docs/configuration/file#providers) in the Nixpacks config file and in the service settings in the Railway Dashboard.

When multiple providers are defined, Railway will build your service with the language providers (in the order you defined) and ensure your binaries are ready to be called. The runtimes will then initialize as soon as you start your application.

We’re excited to see what you can do with this new feature. Hop into the [Discord](https://railway.app/discord-link) and let us know how it works for you.

## Accessibility Improvements

In the US alone there are more than 4,000,000 people using an assistive tool to browse the web. Railway now has ARIA labeling throughout the product to improve the experience for those using screen readers and other assistive technologies. 

We’ll always work to make Railway as friendly as possible to those with impairments. [Join our Discord](https://railway.app/discord-link) or [drop us a line](https://support.railway.app/hc/en-us/requests/new) if you have any comments on how we can continue to make Railway more accessible.

## Nixpacks Fixes for Heroku Migrators

[As mentioned previously](https://railway.app/changelog/2022-10-27-pull-request-deploy-environment-override), we are in Search and Destroy Mode™ for any blocker that prevents Railway users from adopting Nixpacks. 

This week we’ve improved the build experience for Ruby and PHP and fixed some common issues like Gem install errors. We’ve also made it easier to debug your service builds with improvements to logging and erroring.

We continue to prioritize and address Nixpacks issues. The feedback we’ve received so far has helped us push Nixpacks forward by leaps and bounds — please keep it coming! Feel free to raise issues with us on [Discord](https://discord.gg/railway) or by replying to this email. 

We’ll keep the bug spray handy.

## Improvements and Fixes

- Nixpacks [upgraded to v0.13.1](https://github.com/railwayapp/nixpacks/releases/tag/v0.13.1)
- Added a `projects` query to the [Public API](https://docs.railway.app/reference/public-api#examples)
- Added the ability to copy Shared Variables to a PR environment
- Added auto-detection of Nixpacks provider(s) during snapshot generation and now display providers on the deployment details page
- Fixed a bug with syntax highlighting in the raw variable editor