Greetings from Railway HQ where the Q4 train has left the station and is starting to gather speed.
We’re back to regularly scheduled programming after Launch Week 01, a team retreat in New Orleans, and a week of Railway Hacks, and we couldn’t be more excited to share some new features with you.
Let’s get this thing started!
Database Templates GA on Monday

As mentioned during Launch Week, services with volumes are the future of databases on Railway. Database templates have been in Priority Boarding for a few weeks now and we’ve been busy improving flows and softening any hard edges.
On Monday, database templates will be the default for anyone deploying a new database on Railway.
Some updates we’ve made meanwhile include:
railway connectworks for database templates- Improved information around the “Data” tab
- Prompting to connect to your database via variable references
- Ability to deploy database templates when you don’t have a GitHub account linked
- Clearer volume names
- Fixed TCP proxy connection leak
- New templates for
As always, please reach out on Discord if you find any issues.
Usage Limits to GA

A few weeks ago, we launched Usage Limits to Priority Boarding.
Usage Limits allow you to set a maximum limit for usage during a billing cycle.
The response has been excellent and today we’re thrilled to announce that Usage Limits are now generally available via Account settings.
For more information, be sure to read the docs.
And be sure to jump on Discord to let us know what you think!
Atomic Feature Flags to PB

Atomic Feature Flags let Priority Boarding users opt-in to new features on a case-by-case basis.
This is exciting for a number of reasons:
- New features will be opt-in at the atomic level, giving you more control of your Railway experience
- We’ll be able to release new and experimental features with breaking changes to Priority Boarding on an opt-in basis
- We’ll be able to transition to more granular control of feature releases
We’re excited for this new tool for releasing features, hope you like it!
Deploy Public GitHub Repos
Deploy a public GitHub repo by pasting a URL into the command paletteIt’s now possible for Priority Boarding users to deploy any public GitHub repo to Railway simply by pasting the URL in the command palette.
Have a public repo that you’d like to run on Railway? Give it a shot!
You’ll first have to activate the feature flag via Account Settings → Feature Flags. After that, you’ll be able to paste your URL in the command palette (or on dev.new) and we’ll automatically detect the repo and import it into your project.
Let us know what you think on Discord!
Fixes and Improvements
- We added a new GraphQL API collection generator service template using Graphman and Flask
- For Free and Trial users, we decreased the volume size to 0.5 GB
- We added an option in the volume settings to grow the volume size when transferring the project to a team on the Pro plan
- In the CLI, we now prompt for a service when linking a project
- When introspecting a database service, we now show a banner with a link to the docs on variable references
- We improved Docker image parsing