Documentation menu

Plans

Start with Trial. Choose Starter or Team when the workflow fits.

Trial lets teams evaluate the real self-hosted runtime for 3 days. Starter starts from $49/month, Team starts from $149/month, and Business starts from $399/month. Custom covers larger rollout, procurement, or security-review needs.

3 days

Trial

Self-hosted core, console, API, worker, CLI, and limited scoped evidence.

$49/mo

Starter

Self-hosted release gate for small teams, basic auth, CLI gate, core evidence, and guided reports.

$149/mo

Team

Team workspaces, shared approval flow, templates, longer history, collaboration, and SSO group mapping.

$399/mo

Business

Higher limits, runtime checks, registry mirror guidance, and production-readiness controls without enterprise claims.

Contact

Custom

Manual commercial review for rollout, procurement, security review, and product-fit requirements.

License behavior

PlanTrial
Payment requiredNo checkout; expires after 3 days
Core gate availableYes, server-mode self-hosted gate is included.
Main limitations or unlocksLimited scale, retention, connector depth, and reports. Online refresh required.
PlanStarter
Payment requiredYes: $49/month USD through secure checkout
Core gate availableYes, same core workflow.
Main limitations or unlocksAdds small-team limits, guided reports, history, and online refresh.
PlanTeam
Payment requiredYes: $149/month USD through secure checkout
Core gate availableYes, same core workflow.
Main limitations or unlocksAdds workspaces, shared approval flow, templates, longer retention, and online refresh.
PlanBusiness
Payment requiredYes: $399/month USD through secure checkout
Core gate availableYes, same core workflow.
Main limitations or unlocksAdds higher limits, runtime checks, explicit mirror guidance, production controls, and online refresh.
PlanCustom
Payment requiredManual only
Core gate availableYes, scoped by contract.
Main limitations or unlocksManual fulfillment for rollout, procurement, security review, and product-fit requirements.

Install-bound licenses

Every customer runtime keeps a stable RELEASEPASSPORT_INSTALL_ID in the runtime Secret. License envelopes bind to installIdHash. Trial, Starter, Team, and Business refresh entitlement online; Custom can be fulfilled manually.

Production fulfillment states.

Checkout created only after billing is configured.
Signed successful payment webhook received for eligible purchases.
Production entitlement active for the workspace.
Production download channel ready.
Shadow rollout complete.
Enforce readiness accepted.

Checkout readiness.

Checkout and entitlement issuance run on the public commercial service, not inside the customer runtime. Webhook activation will map signed successful payment events to active entitlement; pending stays pending; failed, cancelled, or expired stays inactive.

billing checkout
curl -sS https://releasepassport.com/releasepassport/v1/billing/checkout \
  -H "Content-Type: application/json" \
  -d '{
    "planId": "starter_monthly",
    "workspaceId": "workspace-acme-prod",
    "email": "billing@example.com",
    "companyName": "Acme Platform Team",
    "provider": "polar",
    "merchantOfRecord": "polar"
  }'

# Payment and entitlement issuance stay on the public commercial service.
# Provider and merchantOfRecord are adapter metadata. No payment secret is returned here.

Payment state mapping

Payment event/statusSuccessful payment completion
Release Passport statusactive
Entitlement resultActivate eligible paid entitlement.
Payment event/statusAccepted capture or settlement
Release Passport statusactive
Entitlement resultActivate eligible paid entitlement.
Payment event/statusPending authorization or delayed payment
Release Passport statuspending
Entitlement resultNo production entitlement yet. User can wait or retry as instructed by checkout.
Payment event/statusDenied or failed payment
Release Passport statusfailed
Entitlement resultDo not activate production entitlement.
Payment event/statusCancelled or expired checkout
Release Passport statusexpired or cancelled
Entitlement resultDo not activate production entitlement.

Custom request template.

Send only public-safe implementation context. Secrets and private evidence are never required for the sales request.

custom request
Company:
Technical owner:
Commercial owner:
Target domain:
Kubernetes distribution:
Auth mode (basic, OIDC, or proxy):
CI/CD and GitOps:
Registry location:
First services:
Desired shadow-mode date:

Do not include secrets, tokens, private keys, kubeconfigs, or private evidence.