Documentation
Guardrail Ledger documentation
Everything here describes what Guardrail Ledger does today. Start with the first page and follow the steps in order.
- Getting startedStart a Guardrail Ledger trial, sign in to your workspace and find your way around the console.
- Connect your pipelineRun Trivy, Gitleaks, Checkov and Opengrep on your agents and send the SARIF to Guardrail Ledger from Azure DevOps or GitHub Actions.
- The gate and exceptionsChoose the severity that fails a pull request, read the gate result and record an exception with an owner and an expiry.
- IntegrationsAzure DevOps, GitHub Actions, any CI through the SARIF API, and Microsoft Entra sign-in.
- API keys and scopesIngest tokens: what they allow, how to mint and revoke them and where to store them.
- Team and rolesWho can sign in to Guardrail Ledger and what owners, admins and members can change.
- Plans and limitsWhat the Team, Business and MSP plans include: prices, contributors, repositories and trial terms.
- Security and dataWhat Guardrail Ledger stores, where it is stored, how the audit log works and how to choose the region.
- TroubleshootingFixes for common Guardrail Ledger problems: failing scanner steps, ingest errors, missing pull request comments and refused changes.