Security
What's true today, and what's planned
RelayOps is a working beta for design partners. This page says exactly which protections exist now and which are on the roadmap, so you can judge the proof for yourself.
| Area | Today | Planned |
|---|---|---|
| Where checks run | today The relayops verify step in your GitHub Actions or GitLab CI, so your code stays in your CI. Or a Docker sandbox on the RelayOps server. | planned A runner agent in your own cloud or Kubernetes cluster. |
| Sandbox network | today Deny by default. Installs reach only the package registries on an allowlist you can review; tests get no network unless allowed. Cloud metadata and private ranges are always blocked. | |
| Secrets | today Never passed to the code under test. Tests that need one end INCOMPLETE ("needs secret"), and only the secret's name is recorded. Git tokens are short-lived, read-only and revoked after checkout. | planned Short-lived secret injection per repository, never written to evidence. |
| Signing | today ECDSA P-256 over a DSSE envelope. Signed with a development key, and every Passport, report and PR comment says so. | planned Production signing with a cloud KMS key, hosted or customer-controlled, with key rotation. |
| Checking a Passport | today Offline, without contacting RelayOps: relayops-passport verify, or in your browser. | planned An open-source verifier and schema with a conformance suite. |
| Stale proof | today A Passport is bound to the base and head commits and an inputs hash. A new commit or a moved base makes it stale and re-verification starts. | |
| AI | today Advisory only. It classifies, explains with citations and plants test mutants; it never sets a status. It can be switched off. | |
| Sign-in and roles | today GitHub sign-in with no write scopes; the GitHub token is revoked straight after login. | planned Organisations, Owner and Member roles, SAML/OIDC SSO and SCIM. |
| Data | today Postgres in a private schema with row level security on; the database credential lives outside the code. | planned Per-organisation isolation in the hosted service, retention policies. |
| Compliance | today An audit pack maps each change's evidence to SOC 2, ISO 27001 and NIST SSDF controls, verifiable offline. This is evidence, not certification. | planned SOC 2 Type I for RelayOps itself. |
Report a security issue
Write to hello@relayops.cloud with "security" in the subject. We'll reply within two working days.