Documentation menu

Documentation

Know if a release is safe before the pipeline promotes it.

Release Passport is closed-source, licensed release gating software that customers self-host in their own infrastructure. Trial includes the core self-hosted runtime, console, API, worker, CLI, and limited scoped evidence. Starter, Team, Business, and Custom unlock scale, retention, SSO group mapping, reports, advanced connectors, and runtime checks.

What problem Release Passport solves

A deployment pipeline usually knows the commit, build job, test result, and container image. It often does not know whether the target namespace is healthy, whether the previous revision is still reachable for rollback, whether the GitOps application is synced, whether runtime error rate is already bad, or whether the release evidence is complete enough for production. Release Passport sits before promotion and turns those facts into a passport: a durable allow, hold, or block decision with the evidence trail attached.

CI/CD sends release identity and artifact details through releasepassport gate.
Scoped connectors add orchestration, metrics, logs, CI/CD/GitOps, test, and incident/error evidence.
Policies evaluate whether the evidence is fresh, complete, and acceptable for the target environment.
A passport records the verdict, risk, blockers, timeline, and operator context.

Gate before production

The CLI asks the self-hosted API for a go/no-go verdict before promotion.

Scoped evidence

Kubernetes, metrics, GitOps, CI/CD, and error evidence are read only from configured scope.

Passport record

Every decision creates an inspectable release passport for operators and auditors.

Product boundaries

Customer self-hosted runtime

Customer installs include /console, /settings, the API, worker, CLI integration path, storage wiring, and scoped connectors. This is the product runtime that customer platform teams use inside their own infrastructure.

Owner app is not in the customer package

The Arconath owner surface for users, pricing, billing, license issuance, entitlement, and package access is separate. Customer installs must not expose owner/admin tools.

First user journey

1. Sign in to the Release Passport Portal
Sign in to the Release Passport Portal.
2. Generate a Trial install token tied to the portal account
Generate a Trial install token tied to the portal account.
3. Run the token-first installer command
Run the token-first installer command.
4. Let the installer detect Kubernetes or Docker Compose, domain, storage, and connector hints
Let the installer detect Kubernetes or Docker Compose, domain, storage, and connector hints.
5. Open the customer-owned self-hosted console printed by the installer
Open the customer-owned self-hosted console printed by the installer.
6. Upgrade later with releasepassport upgrade or the same token-first installer
Upgrade later with releasepassport upgrade or the same token-first installer.
7. Remove the runtime later with releasepassport uninstall
Remove the runtime later with releasepassport uninstall.

Quick Start

Install Trial, run the first server-mode gate.

Open quick start

Install

Self-hosted package, dashboard, and owner split.

Open install

Configuration

Runtime, OIDC, tokens, connectors, retention.

Open configuration

CLI

Server mode, local dev mode, exit codes.

Open cli

API

Gate, evidence, passport, connector examples.

Open api

Concepts

Gate, passport, evidence, mode, connector.

Open concepts

Features

Why it matters before production deploy.

Open features

Connectors

Scoped orchestration, metrics, logs, delivery, and incident evidence.

Open connectors

Policies

Evidence requirements and decision effect.

Open policies

Console

What each customer console menu means.

Open console

Plans

Trial, Starter, Team, Business, and Custom terms.

Open plans

Security

Protected routes, secrets, and public posture.

Open security

Troubleshooting

Login, redirect, gate, and connector fixes.

Open troubleshooting