Migrations Migrating from Heroku, Render, Hatchbox or Cloud 66? We move your production app within 48 hours →
Databases and backups

Databases and backups

Postgres, MySQL, Redis, MongoDB, ClickHouse and more — provisioned, connected and backed up.

  • Provisioned on your server, one database and user per app, credentials injected as variables. Engines: Postgres, MySQL, Redis, MongoDB, ClickHouse, Elasticsearch, InfluxDB, RabbitMQ, Memcached, and S3-compatible storage.
  • Standalone databases from the canvas run as private services reachable at <name>.railyard.internal.
  • Backups: scheduled, verified by restoring them, one-click restore; Postgres point-in-time restore.
  • Console: query Postgres and MySQL from the app page; Redis and Mongo consoles on the canvas.
  • Copies: copy production into a staging environment.

Dedicated pages per engine cover this in more depth, with a real one-click app to deploy: Postgres, Redis, MySQL and MongoDB.

Connect from your computer

Managed databases are private: only apps on the server can reach them. To use psql, TablePlus, redis-cli or clickhouse-client from your machine, open Trusted addresses on the database or add-on card and allow your IP. Railyard opens a TCP proxy on the server for that address only; every other address stays blocked and the password is still required. The card gives you the command to paste. This works for Postgres, MySQL, ClickHouse, Redis and RabbitMQ, and for datastores that live on a separate database server.

Insights

The database console’s Insights tab shows cache and index hit rates, connections against max_connections, database size, the slowest and most frequent queries from pg_stat_statements, long-running queries you can cancel, and unused indexes.

Provider-run databases

From an app’s Resources tab, create a Managed Postgres database in your own DigitalOcean or AWS account instead of on a Railyard-managed server. Connect DigitalOcean or AWS under Team → Cloud accounts, pick a size and Postgres version, and Railyard creates it, waits for it to come online, and attaches it to the app as DATABASE_URL with sslmode=require. Progress shows live on the Resources tab.

On AWS, Railyard keeps the database inside your VPC when the app’s server is also on AWS in the same region (no public exposure); otherwise it opens the database to the public internet but locks it down to that one server’s IP. If an older AWS connection doesn’t yet grant RDS permissions, the Resources tab prompts you to reconnect AWS to pick up the new permissions.

Delete the database from the same card — type the app’s name to confirm. On AWS, a final snapshot is kept unless you explicitly choose to skip it.

Found an issue or have a question?
Theme
Colors