Before we get started, let’s talk about the 

 — that’s 25% of whatever we make from a template sent to your bank account via GitHub Sponsors or Buy Me a Coffee.

If you wanted to get started contributing templates, we put together a 

 to give you more information. Inside you’ll read about how we’ve already hit $40K in template payouts and payouts are growing more than 30% month over month. Check that out 

Network Egress and Volume are now available as usage charts

This week we added usage and cost charts for Network Egress and Volume. 

This should make it far easier to reason about how much you’re being charged over time for egress and storage. 

To access these charts, you’ll need to select your project in the 

 menu. (Make sure you have the right team selected!)

If you have more requests for usage and billing features, we’d like to hear them. Drop us a line 

The new deployment details pane features a deployment checklist and relevant environment variables

This week we updated the service deployment pane. 

In addition to a cosmetic makeover, we now also include the relevant deployment checklist as well as the environment variables that were used for the deployment. 

This should make it much easier to access the info you need when working within a particular deployment in the UI. 

Let us know what else you’d like to see in the deployments pane by leaving some feedback 

Screenshot of the integration card within the Profile settings page

For those not in the loop, Railway develops our own Help Center to make it so that we don’t have to ask “Project ID?” over and over again. However, we have found ourselves repeating ourselves quite a bit in a burgeoning channel that we have been spending more time in.

Our mail room is quite a mess especially now that the Railway team has around 200+ active Slack Connect channels. So in the same way how we have blended our Discord <> Help Center seamlessly- we are bringing that to companies who have a Slack Connect channel. Don’t have one? 

The first step is associating Railway accounts to Slack accounts so we know who is who in our Support tool. The next step is being able to page us with a Slash command. So we advise you to stay tuned for the next Changelog.

we wrote some docs for the compliance focused about our (very light) permissions footprint. 

We added the ability to pre-fill template variables with query params

We added public projects to public profiles

We added the ability for team members to 

We added the ability to add a demo project to a template

We fixed an issue with autodeploying services that depend on a shared variable

https://res.cloudinary.com/railway/image/upload/v1719016111/2024-0621_ecwry6.png

Improved Cost Charts, Improved Deployment Details, Slack Account Link

Changelog #0191