Documentation menu

Download

Trial lets users install the real self-hosted product.

Trial is not just a local CLI demo. It includes the self-hosted runtime, customer console, API, worker, CLI, and limited scoped evidence so users can experience the core value before buying production features.

Trial

Install and run the first server-mode gate.

The 3-day trial license is created during setup. Starter, Team, Business, and Custom add scale, retention, SSO group mapping, advanced connectors, reports, and runtime checks.

Trial install
# Sign in to https://releasepassport.com/portal first.
# Customer runtime images are pulled only from the official Release Passport registry.
# The installer creates or preserves RELEASEPASSPORT_INSTALL_ID in the runtime Secret.
curl -fsSL https://releasepassport.com/install.sh | bash -s -- \
  --install-token <portal-install-token>
Production packages

Upgrade when the team needs production scale.

More services and environments.
Longer audit and report retention.
SSO group mapping and advanced policy.
Advanced connectors and runtime checks.

Download and install flow

User intentTry the product
What they doDownload a 3-day Trial license.
What they receiveCLI, checksums, Helm chart, values example, console/API/worker runtime.
Next stepInstall chart and run server-mode shadow gate.
User intentUse more services/connectors
What they doChoose Starter, Team, or Business and complete payment checkout.
What they receiveProduction entitlement after a valid successful payment event for eligible purchases.
Next stepApply entitlement material and enable production features.
User intentCustom rollout
What they doRequest custom review with public-safe implementation context.
What they receiveProcurement/security path, custom terms, and licensed package process.
Next stepPlan rollout, evidence scope, retention, and operating model.

What trial users download

CLI archives, checksums, Trial Helm chart, values file, install script, and docs for the core self-hosted runtime.

What production customers receive

The same install path plus production license material, licensed image/package channel, and plan-specific values.

What never gets installed

Source packages, owner app, billing controls, license issuance, pricing, package entitlement, and sales operations.

Use this decision rule.

If you are evaluating the core value, install Trial now. If you need production scale, retention, SSO groups, advanced connectors or runtime checks, request a production license and use the entitlement token when the download channel is ready.

download path
# Trial: token-first, checksum-backed bootstrap package
curl -fsSLO https://releasepassport.com/install.sh
curl -fsSLO https://releasepassport.com/install.sh.sha256
if command -v shasum >/dev/null 2>&1; then shasum -a 256 -c install.sh.sha256; else sha256sum -c install.sh.sha256; fi

bash install.sh --install-token <portal-install-token>

# Production: use the entitlement channel after subscription activation
export RELEASEPASSPORT_DOWNLOAD_TOKEN="rp_dl_..."
curl -fsSL https://releasepassport.com/install.sh | bash -s -- \
  --install-token <portal-install-token>

After download, what does a user do?

1. Install chart
Install Trial into the customer cluster using the chart and values file.
2. Open console
Sign in through the customer runtime OIDC/basic/proxy auth and confirm /console and /settings work on the customer-owned domain.
3. Create token
Create a gate token and store it as RELEASEPASSPORT_TOKEN in the pipeline.
4. Connect source
Configure one scoped evidence source and wait for connector freshness.
5. Add CI gate
Run releasepassport gate after build and before deploy promotion.
6. Inspect passport
Use the passport detail to understand allow, hold, or block reasons.
7. Expand
Add more services/connectors/policies after the first service has trustworthy evidence.