Add a server

Your apps run on servers you own. Railyard never marks up compute: your provider bills you directly.

Create one on your cloud

Servers → Add a server → Create on your cloud, then pick the provider, region and size. Live monthly prices are shown once a token for that provider is saved in Team → Cloud credentials; a saved token is reused automatically (tick Save it to the team the first time).

Railyard creates the server with a one-time SSH key, installs Docker, Caddy and the agent as a systemd service, and the server registers itself.

Bring your own server

Any Ubuntu 22.04 or 24.04 machine works if:

• the SSH user has passwordless sudo;
• ports 22, 80 and 443 are reachable from the internet;
• it has at least 1 GB of RAM (2 GB or more if you build apps on it).

The private key is used once for the install and is not stored.

Build servers

Big builds don’t have to run on the machine serving your apps. When no build server is online, Railyard starts a temporary one sized for builds (the provider’s smallest 8 GB size, or your app server’s size if the provider refuses it). After 20 idle minutes it’s parked, not destroyed, so the next build within 7 days reuses the same warm server instead of waiting on a fresh boot; past that it’s torn down.

Private networking

Servers → Private network → Turn on joins every server on an encrypted WireGuard network (10.210.x.x) instead of talking over public IPs — databases, extra servers and replicas use it, across providers and regions. Once on, every app’s <name>.railyard.internal address resolves from any other app on any server of the team, not just apps on the same server; see Variables and secrets.