Platform

The project is the unit of operation, not the container.

Source, runtime, data, networking, deployments and operator actions share one model so the control plane can preserve context across the full lifecycle.

desired-state engineGit + Dockermulti-server control plane
Project graph

Applications and data stay in the same operational picture.

Project environments group applications, databases, caches, volumes and private links. The canvas makes those relationships legible while each service carries its own lifecycle surfaces.

ApplicationsGit repositories and container images with deployment history.
DatastoresPostgreSQL, Redis and plugin-backed services inside the same project.
Private relationshipsLinks between services remain visible without requiring public endpoints.
RailDock project topologyproject / topology
RailDock service deployments and process controlsservice / deployments
01

Project context stays visible as you drill down.

Open a service to manage deploy, stop, restart, rebuild, shell access, process counts and revision history, with logs, variables, networking, metrics and settings beside them.

Extensible runtime

Builders, datastores and services can extend the platform.

RailDock plugin and integration settingssettings / integrations

Application types

Web and worker processes deployed from Git or images.

Build strategies

Dockerfile and builder plugins such as Nixpacks or Railpack can be exposed through the integration layer.

Data services

Database, cache and common service plugins can be installed and managed in-platform.

Runtime architecture

A web control plane over execution engines.

Rails coordinates lifecycle work and host operations, React provides the product surface, and execution happens on Linux hosts over SSH through Dokku and host engines.

Backend

Rails + workers

API, jobs, reconciliation and orchestration.

Realtime

Action Cable

Lifecycle events and changing runtime state.

Execution

Dokku + SSH

Application and datastore operations on your hosts.

Surface

React

Projects, services, data and platform settings.

Go deeper

Understand the model before you automate it.

The docs cover projects, environments, services, servers, networking and reconciliation. The API exposes the same control-plane resources programmatically.