ReleaseTwin

Hosted platform

An optional control plane for run history and evidence. It never executes your cases — the CLI runs in your infrastructure. Hosted evidence runners are planned, not yet available on any tier.

1. Create a project and token

A project is one system under test: the thing one API token, one set of cases, and one release label sequence describe.

  • Sign up — self-serve, no approval step.
  • Create a project on the dashboard.
  • Uploading from GitHub Actions? Bind the repository on the project's Settings page and give the job permissions: id-token: write — no token to issue or store. See CI & GitHub Actions.
  • Anywhere else: issue an API token for it. You'll see the token once — store it as a secret.

2. Point the CLI at it

From an empty directory, with a stored token. Replace the token and API URL, then scaffold and run — do not mount an examples/ folder or a floating :latest tag.

export RELEASETWIN_API_TOKEN=<token from the dashboard>
export RELEASETWIN_API_URL=https://api.releasetwin.com

docker run --rm -v "$PWD:/workspace" ghcr.io/ernestoalejowitt22/releasetwin/cli:0.4.0 init /workspace
docker run --rm -v "$PWD:/workspace" \
  -e RELEASETWIN_API_URL -e RELEASETWIN_API_TOKEN \
  ghcr.io/ernestoalejowitt22/releasetwin/cli:0.4.0 run /workspace/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)

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. The dashboard renders it as a per-report drill-down.

It is the same evidence document your CLI already writes to disk and opens locally with view, rendered the same way. What the hosted platform adds is what a local folder cannot do: it keeps the evidence for your project's retention window, lets you hand someone a read-only link to one run, and rolls results up across runs and releases.

  • 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, capped by your plan (7 days on Free, 365 on Team). A daily purge deletes expired evidence and leaves the metadata report intact.

Plans

The Free tier includes one project, run history, the evidence viewer at 7-day retention, the release-readiness rollup, the flag-proof merge gate, one active share link per run, and a 14-day trial of everything in Team that starts with your first real run. Longer retention, unlimited projects, and the trends, flag blast-radius, tracker, and team layer stay on Team — see pricing.

Next

Programmatic API — pull your own run history and evidence metadata into your own systems (Team tier).