---
title: "SOC 2 Type I, Resource Limits, Request for Writers"
date: 2024-07-26
number: 0196
url: https://railway.com/changelog/2024-07-26-soc2-typeI
---

# SOC 2 Type I, Resource Limits, Request for Writers

Happy Friday!

Before we get started, let’s talk about [Cron Jobs](https://docs.railway.app/reference/cron-jobs). 

If you’ve had issues recently with cron reliability, we’d like to [hear about them](https://help.railway.app/feedback/cron-reliability-improvements-c2f2c959). 

We’ve been flat-out on improving cron quality due to a number of unflattering reports from users over the past few weeks … and although we’ve made a number of substantial improvements, [we’d like to make more](https://help.railway.app/feedback/cron-reliability-improvements-c2f2c959). 

Please [let us know](https://help.railway.app/feedback/cron-reliability-improvements-c2f2c959) about any continuing issues that you’ve had. 

Ok, thank you, on with the regularly scheduled programming. 

Let’s get into it!

## SOC 2 Type I

[Image: Railway is now SOC 2 Type I compliant as well as HIPAA compliant]

Railway is growing up.

There comes a time in every infrastructure provider’s life where use cases start demanding exceptional levels of data security controls and processes. That time for us is now. 

This week, we’re pleased to announce that we’ve completed pen-testing and audit for SOC 2 Type I certification. We are now SOC 2 Type I compliant across all tiers of service. 

We expect to achieve Type II compliance within the next several months.

And if you missed it, we are also HIPAA compliant as of [two weeks ago](https://railway.app/changelog/2024-07-12-hipaa-baas#hipaa-baas) — double whammy. 

If you’re a customer or prospective customer who requires a SOC 2 auditor’s report or HIPAA BAA, please feel free to [schedule a time to talk with our team](https://cal.com/team/railway/demonew). 

Onward!

## Resource Limits

[Video: Resource limits are now available in service-level settings]

Are you worried about unexpectedly high bills due to spikes in usage? 

This week we introduced [resource limits](https://docs.railway.app/guides/optimize-usage#resource-limits) at the service level.

This is extremely helpful in several scenarios:

1. You don't want to risk a high bill due to unexpected spikes in usage
2. You are okay with the service crashing if it exceeds the limit

Please make note of the second item above — your service will likely crash if limits are exceeded. (With great power comes great responsibility.)

You can find resource limits in the service settings under `Deploy`. 

For more information, be sure to [read the docs](https://docs.railway.app/guides/optimize-usage#resource-limits). 

And if you have any comments or questions about the feature, please [let us know](https://help.railway.app/feedback/resource-limits-feedback-e3e3f313). 

Thanks!

## Request for Writers

If you love Railway and want to get paid to write about it, we just opened up applications for a new community contributors program called [Write the Rails](https://forms.gle/v9ta7Si47wM3FdQR9).

In short, we’re looking for experienced writers to submit tutorials to explain Railway concepts to a rapidly growing audience. 

Sound interesting?

Read all about [the program](https://forms.gle/v9ta7Si47wM3FdQR9) on the [application submission site](https://forms.gle/v9ta7Si47wM3FdQR9). 

Have a great weekend! ✌️

## Features and Improvements

- You can now download your *most recent* build or deployment logs from the dashboard using the command palette. With a service deployment modal open, press `CMD + K` then type `Download Build Logs` or `Download Deployment Logs` and hit enter. *Voila!* Up to 5000 log lines are downloaded to your machine with a uniquely identifying filename