Pilot intake
Start a Release Passport pilot.
Share public-safe rollout context so the first self-hosted gate can be planned around your deployment stack, evidence sources, and desired gate mode.
Pilot a first service
Best for teams that want a 3-day self-hosted evaluation with one production-shaped service in shadow mode.
Custom rollout
Use this for procurement, regulated environments, custom retention, or multi-team rollout planning.
What to include.
Company, role, and technical owner.
Deployment stack: Kubernetes, Docker Compose, GitOps, or another runtime.
CI/CD and evidence sources: GitHub Actions, GitLab CI, Jenkins, Argo CD, Flux, Prometheus, Sentry, PagerDuty, Jira, or Slack.
First target service, desired mode, and pilot timeline.
Recommended pilot plan.
Day 1: install Trial and open the protected console.
Day 2: connect CI plus Kubernetes or GitOps evidence.
Day 3: run a shadow gate and review the first passport.
Week 1: add metrics, incidents, reports, and missing-evidence handling.
Week 2+: consider advisory mode before any enforce-mode rollout.
Public-safe support contact.
Do not include secrets, tokens, kubeconfigs, private service names, raw customer evidence, or payment data. Use the email below for product, billing, privacy, or legal questions.