Railway can support any type of Database service required for an application stack.
Databases can be deployed into a Railway project from a template, or by creating one through the service creation flow.
Below are the core concepts to understand when working with databases in Railway.
Railway services are containers deployed from a Docker Image or code repository, usually with environment variables defined within the service configuration to control the behavior of the service.
When deploying a database service, data can be persisted between rebuilds of the container by attaching a Volume to the service.
To access a database service from outside the private network of a particular project, proxy traffic to the exposed TCP port by enabling TCP Proxy on the service.
Many database templates are available to Railway users, which ease the process of deploying a database service.
Railway provides several templates to provision some of the most popular databases out there. They also deploy with a helpful Database View.
Explore the guides in the How To section for information on how to use these templates -
Our Template Marketplace includes many solutions for database services.
Here are some examples -
Explore the Databases guide section for more information on how to get started using databases in Railway.
Edit this file on GitHub