Databases and backups

• 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.

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.