database
Deploy PostgreSQL, Redis, MySQL, or MongoDB with pre-configured volumes, networking, and connection variables.
- Supports four official database templates: PostgreSQL, Redis, MySQL, and MongoDB, each with persistent volumes and automatic connection variable setup
- Always checks for existing databases before creating to avoid duplicates; queries environment config via GraphQL to detect running instances
- Provides reference variables for connecting other services (e.g.,
${{Postgres.DATABASE_URL}}for backends; public URLs available for frontend-to-database patterns) - Integrates with the
environmentskill to wire connection strings into dependent services after deployment
Database
Add official Railway database services. These are maintained templates with pre-configured volumes, networking, and connection variables.
For non-database templates, see the templates skill.
When to Use
- User asks to "add a database", "add Postgres", "add Redis", etc.
- User needs a database for their application
- User asks about connecting to a database
- User says "add postgres and connect to my server"
- User says "wire up the database"
Decision Flow
ALWAYS check for existing databases FIRST before creating.
More from railwayapp/railway-skills
use-railway
>
3.6Kservice
This skill should be used when the user asks about service status, wants to rename a service, change service icons, link services, or create services with Docker images. For creating services with local code, prefer the `new` skill. For GitHub repo sources, use `new` skill to create empty service then `environment` skill to configure source.
1.6Kcentral-station
This skill should be used when the user asks about Central Station threads, community discussions, support questions, feature requests, or wants to search Railway's community knowledge base. Use for queries like "search central station", "find threads about", "what are people asking about", "recent support threads", or "central station topics".
1.5Kstatus
This skill should be used when the user asks "railway status", "is it running", "what's deployed", "deployment status", or about uptime. NOT for variables ("what variables", "env vars", "add variable") or configuration queries - use environment skill for those.
1.5Krailway-docs
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
1.1Kdeployment
This skill should be used when the user wants to manage Railway deployments, view logs, or debug issues. Covers deployment lifecycle (remove, stop, redeploy, restart), deployment visibility (list, status, history), and troubleshooting (logs, errors, failures, crashes, why deploy failed). NOT for deleting services - use environment skill with isDeleted for that.
1.0K