Railway

Connect Railway to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Railway:

   1. In Railway, open the tokens page in your account settings (https://railway.com/account/tokens).
   2. In the workspace dropdown, select the workspace Safeguard should read, so the token is scoped to that workspace (not No workspace, which creates an account token).
   3. Create the token and copy it.

   Railway's public documentation does not cover every step.

   A workspace token has access to all of the workspace's resources; Railway issues no read-only token. The docs checked do not name the create button or say whether the token is shown only once, and do not say where the dashboard shows the Workspace ID.

   Source: docs.railway.com, checked 2026-10-07.

   The permissions Safeguard needs: workspace token. Railway issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.

2. On Compliance › Connectors, open Railway, click Connect, choose API token and fill in:

   Field	What to enter
   API token	Required. Stored encrypted and never shown again.
   Workspace ID	Required.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Railway and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks