Destructive confirmations
Deletion and recovery actions use explicit confirmation behavior instead of casual one-click mutation.
Security
A deployment platform sits close to production. Treat that boundary seriously.
RailDock combines application authentication and authorization with operational guardrails around server access, deploy keys and destructive actions.
Control-plane access
Separate human access from automated access.
Organizations, membership, invitations and roles shape interactive access. Deploy keys and Git-source integrations give automation and source access their own resources.
◇
Organizations & membersshared control-plane boundaries
RBAC◇
Deploy keysautomated deployment access
scoped◇
Server validationexplicit connectivity and provisioning checks
checked◇
Activity historyoperator and lifecycle events remain visible
loggedSnapshot-aware recovery
Recovery workflows can preserve a safety snapshot before replacing current datastore state.
Infrastructure stays yours
You retain responsibility for host hardening, firewall rules, SSH trust and secure network exposure.
Security is a deployment concern
Review the trust boundary before exposing the control plane.
Read authentication, server and secret-management guidance as part of installation—not after production is connected.