Hosted platform

An optional control plane for run history and evidence. It never executes your cases — the CLI still runs entirely in your infrastructure.

1. Create a project and token

Sign up — self-serve, no approval step.
Create a project on the dashboard.
Issue an API token for it. You'll see the token once — store it as a secret.

2. Point the CLI at it

export RELEASETWIN_API_TOKEN=<token from the dashboard>
export RELEASETWIN_API_URL=<your hosted API URL>

dotnet run --project src/ReleaseTwin.Cli -- examples/cases

Uploads happen automatically after each case. A failed upload prints a warning but never changes a case's pass/fail result or the CLI's exit code.

3. What gets uploaded

By default, metadata only:

case ID, oracle reference, fixture hash, pass/fail, failure classification
flag-proof outcome and build identity
never fixture content, request/response bodies, or credentials — there is no field for them in the ingest contract

4. Evidence viewer (opt-in, paid)

Turn on evidence capture per project to also upload a redacted evidence document — per-step request/response summaries, assertion path / expected / observed, and UI screenshots. It renders as a per-report drill-down on the dashboard.

Redaction runs in your CLI, before upload: auth headers, credential-shaped fields, and resolved ${ENV_VAR} secrets are stripped automatically.
You add your own allow/deny rules; the redactor fails closed on any rule it can't evaluate.
Retention is a per-project window (default 30 days, max 365). A daily purge deletes expired evidence and leaves the metadata report intact.

Plans

The Free tier includes one project, run history, and 30-day retention. The evidence viewer, unlimited projects, and longer retention are on paid tiers — see pricing.