Security
How Railyard is secured.
A plain description of the controls that exist today. We would rather be specific about what is in place than gesture at a badge.
Access control
- Roles nest: viewer, deployer, admin, owner — each includes the permissions below it.
- Two-factor authentication with TOTP and single-use backup codes.
- API tokens are scoped and individually revocable.
- Every deploy, configuration change and membership action is written to an append-only audit log.
Agent communication
- Agents authenticate to the control plane with a shared secret on every call.
- A newly registered agent arrives unclaimed and does nothing until an administrator claims it into a team.
- Deploy commands stream over a single connection; cancelling a deploy terminates the subprocess on the server rather than leaving it running.
Secrets
- Application configuration is stored encrypted and injected into containers at run time.
- Build-time secrets are mounted through BuildKit rather than baked into an image layer.
- Backups can be verified by restoring them, so an unusable backup is discovered before you need it.
Your infrastructure
Railyard does not own the servers your applications run on. They are created in your own cloud account or attached from hardware you already control, which means the ultimate access boundary is yours — including the ability to revoke ours.
Reporting a vulnerability
Email security@railyard.run with enough detail to reproduce the issue. We will acknowledge within two business days and keep you updated until it is resolved. Please do not test against other customers' infrastructure.