---
title: "HIPAA BAAs, Build Reliability, and Dependabot and Renovate Bot"
date: 2024-07-12
number: 0194
url: https://railway.com/changelog/2024-07-12-hipaa-baas
---

# HIPAA BAAs, Build Reliability, and Dependabot and Renovate Bot

If you’re interested in Railway’s compliance footprint, integration with dependency bots, and build reliability, well, this is the changelog for you. 

But before we get started, we wanted to let you know that we’ve opened a couple of new job reqs for designers and engineers interested in solving big distributed systems problems at scale with us. 

Check out those open roles [here](https://railway.app/careers). 

Now let’s get into the fun stuff.

## HIPAA BAAs

[Image: HIPAA BAAs are now available ]

Hello there from the Business Team here at Railway. 

The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a federal law that **requires the creation of national standards to protect sensitive patient health information from being disclosed without the patient's consent or knowledge. **

In the past, we would advise users to eschew handling patient data on our platform. No longer. 

After a lengthy compliance process with help from our customers and our legal team, we now are able to enter into a BAA.

HIPAA Business Associate Agreements are now available to customers above $1,000 of monthly committed spend. 

[Book an onboarding call](https://cal.com/team/railway/demonew) to get one. If you’re working with health data, we’re excited to make this happen for you.

Now let’s talk about build reliability. 

## Build Reliability

Railway is best when you don’t have to think about stuff going wrong. 

Builds have been taking too damn long lately, and for some, they’ve been timing out. 

First and foremost, we want to acknowledge that this level of service (builds timing out) is not up to our standard.

Second, we’d like to tell you about what’s been going on, what we did to solve the issue, and how these build issues will occur less moving forward.

Over the past few weeks, as we scheduled workloads on the hosts within our fleet, some operations would hang as a result of the nature of the runtime, or the host, or the workflow itself.

In isolation this doesn’t lead to any major issues, but when multiplied many times over, it led to a soupy mess of poor performance exacerbated by demand spikes.

At one point this past week, we had to disable builds for Hobby plan users. Users saw that for small images, build times shot up from 3 minutes to 10 minutes, and even longer for large codebases. 

In the past for previous outages related to builds, we would apply a patch and things would operate nominally for 2 to 3 months. No longer. We used this opportunity to overhaul the build queue and scale it up. 

After the overhaul, we’ve seen build times go down to as low as 45 seconds and already we are now processing a record amount of builds after the applied fixes.

Action speaks louder than Changelogs of course so we invite you to keep on [raising issues](https://help.railway.app/) no matter how small if they impact your experience on the platform.

## Support for Dependabot and Renovate Bot

[Image: We’ve added support for Dependabot and Renovate Bot]

Railway now supports automatic environment creation via [Dependabot](https://newslink.railway.app/e/c/eyJlIjoxMjY5ODEsImVtYWlsX2lkIjoiZXhhbXBsZSIsImhyZWYiOiJodHRwczovL2dpdGh1Yi5jb20vZGVwZW5kYWJvdCIsInQiOjE3MjA4MTY5MzF9/c24be850051a69982e61fc86e0545c1ff9d5b1b9a7bd6a7e46a60ccef8810aa7) and [Renovate Bot](https://newslink.railway.app/e/c/eyJlIjoxMjY5ODEsImVtYWlsX2lkIjoiZXhhbXBsZSIsImhyZWYiOiJodHRwczovL2dpdGh1Yi5jb20vcmVub3ZhdGVib3QvcmVub3ZhdGUiLCJ0IjoxNzIwODE2OTMxfQ/13e70f8f195297c18d744cf59373d3afb2464b86b11b914d081142fca43876dd).

If you'd like to hook your bots into your Railway project to keep your dependencies secure and up-to-date, check out the [new environment setting](https://docs.railway.app/guides/environments#enable-pr-environments) in your Project settings.

[Image: The feature is available in Project settings]

Like many features, this feature originated from a customer support request. 

So be sure to [let us know](https://help.railway.app/) if there’s anything standing in the way of your project’s success. 

## Fixes and Improvements

- We fixed some edge cases where deployments could sometimes appear out of order in the deployments pane
- We added the ability to see historical usage data for the past two billing cycles