RailDock owns orchestration
Project lifecycle, service operations, desired-state planning and application-level workflows.
Self-hosting
The control plane runs where you decide.
Install RailDock, connect Linux hosts over SSH, and manage application infrastructure without moving ownership of compute or data to a hosted PaaS.
VPS / EUproduction
bare metaldata workloads
VPS / USstaging
private hostinternal apps
Control plane + remote hosts
Centralized operations, decentralized infrastructure.
RailDock separates the operator experience from the place workloads run. Servers can be provisioned, validated, inspected and assigned to projects while execution remains on the target host.
install
curl -sSL https://raw.githubusercontent.com/mona-chen/raildock/main/install.sh | bashOperational boundary
What RailDock owns—and what you still own.
Self-hosting gives you more control, but it also keeps host security, capacity planning, networking and upgrade discipline in your domain.
You own the host boundary
Operating-system hardening, firewall policy, capacity and network reachability remain your responsibility.
Secrets stay in your environment
Application secrets, keys and infrastructure credentials remain inside the infrastructure you operate.
Install intentionally
Start with a host you can afford to understand.
Use the installation and server-provisioning guides to validate the control-plane host and first execution target.