A platform layer you can read, run and change.
RailDock is MIT licensed. The control plane, execution engines, installer and product UI are inspectable instead of becoming another opaque dependency beside production.
Your deployment platform should not be a black box.
A self-hosted control plane can touch source code, SSH credentials, networks and production data. Open code lets operators inspect lifecycle paths, review upgrades and adapt the platform to their environment.
One product, several technical layers.
Contributors can work on API lifecycle code, desired-state reconciliation, host execution, realtime state, product UI, installer logic, documentation or plugin surfaces.
Control plane
API, jobs, models, reconciliation and integrations.
Product UI
Projects, services, metrics, settings and data.
Execution layer
SSH, Dokku, server provisioning and networks.
Knowledge layer
Guides, architecture and API reference.
Follow a request from UI to host mutation.
The repository is the best place to understand how RailDock turns product intent into infrastructure work.