Features
Release Passport sees what an isolated pipeline usually cannot.
A build pipeline knows source, tests, and artifacts. Release Passport adds environment readiness, runtime signals, rollback posture, policy context, and evidence history before deployment proceeds.
Environment evidence before deploy
Kubernetes readiness, GitOps app state, metrics freshness, and scoped error signals.
Signed decision record
Every gate writes a release passport operators can review later.
Shadow to enforce rollout
Adopt safely without breaking production pipelines on day one.
Console for explanations
The console answers why a gate allowed, held, or blocked the release.
Arconath dogfood
Arconath runs workspace-arconath-internal on enterprise_dogfood and sends scoped pipeline/service evidence through the same gate path customers use.
Feature depth by plan
| Feature | Trial | Starter | Team | Business | Custom |
|---|---|---|---|---|---|
| Self-hosted runtime | Included for 3 days | Included | Included | Included with production controls | Included with custom rollout terms |
| Console and settings | Included | Included | Included | Included | Included |
| CLI server-mode gate | Included | Included | Included | Included | Included |
| Connector scope | Evaluation scope | Small-team scope | Team scope | Business connector depth | Custom connector depth |
| Retention | Short evaluation retention | Starter audit/report retention | Team audit/report retention | Business audit/report retention | Custom retention and compliance terms |
| SSO mapping | Basic access | Basic access | Group mapping | Advanced group mapping | Advanced identity and procurement requirements |
| Reports | Basic/sanitized | Expanded exports | Team exports | Business exports and review workflow | Custom reporting and review process |
| Commercial terms | Trial terms | Starter entitlement | Team entitlement | Business entitlement | Custom agreement |
Why it is different from a normal pipeline
The value is not that Release Passport can make a pipeline fail. Any script can fail a pipeline. The value is that it fails or holds the pipeline based on evidence the isolated pipeline usually does not have: target health, GitOps readiness, rollback availability, runtime metrics, scoped errors, previous release context, and policy history. That evidence is visible in the passport, so the team can understand the decision instead of guessing which script condition fired.