releasetrail

Approve one exact hash. Deploy, verify, get a receipt, roll back.

One payment of $99, plus sales tax where it applies, and every future update. Delivered as a private GitHub repository you're invited to.

See it work

releasetrail 1.0.1demo mode

$ releasetrail demo
plan       rel_d2b1b1913503e247  8 passed, 0 warnings, 0 blockers
approve    plan hash de6d949269e4afcf...
apply      VERIFIED
receipt    VERIFIED, content hash 7e2216cd1f02e660... (intact)
rollback   ROLLED_BACK  (live file now: <h1>Previous release</h1>)
demo passed: planned, approved, deployed, verified, receipted and rolled back

Demo mode, not a live system: releasetrail 1.0.1, run on 2026-10-05. The tool's own demo on our test machine, in a throwaway project in a temporary folder; the "deploy" copies one HTML file, and nothing outside that folder is touched.

What it does

releasetrail turns a change into a release you can defend: your own gates and scans run first, you approve one exact SHA-256 hash, it deploys, checks the live result, writes a receipt and keeps a rollback one command away. It has a command line and a local web desk.

Exact-hash approval: Approve one SHA-256 of the plan. The files, symlinks and the Git commit are re-checked before the deploy runs.
Gates and scans: Your own tests plus a credential scan, a forbidden-text scan, a swallowed-error scan and an environment-name check. Each can block, warn or be off.
Verified deploy: Command and URL checks after the deploy, with retries for pages that need a moment to come up.
A receipt: A JSON or HTML record of the plan, the checks, the approved commands and the timeline, with a content hash you can re-check.
Reversible: A source safety archive before the deploy and a rollback command. A deploy or rollback that times out is never retried: it stops for a person and goes to a written reconciliation.
A local desk: A loopback-only web page for the same flow, plus a full command line.

What you get

releasetrail 1.0.1: the Python package and the releasetrail command, the local web desk, an example contract, and the full test suite, with 152 automated tests.

A commercial license. Use it and change it in your own projects and your clients' projects. Don't share or resell the source. Read the license.

Every update. New versions land in the same repository; git pull to get them.

Requirements

Python 3.10 or newer. Python 3.10 or newer and Git, no other dependencies. Built and tested on macOS; Windows is supported only by a fallback that is not tested.

How buying works

Enter your GitHub username. You'll see the account before you pay, so you can check it's yours.
Pay $99, plus any sales tax shown at checkout, on Stripe's checkout page.
Accept the invitation GitHub emails you. Signed in as that account, you'll also find it at github.com/dominares-tools/releasetrail/invitations. Invitations expire after 7 days; you can get a new one any time.
Clone and install:
```
git clone https://github.com/dominares-tools/releasetrail.git
```
Private repo: sign in to GitHub on this computer first. Run gh auth login and choose HTTPS, or give git a personal access token when it asks for a password. To use an SSH key instead, clone git@github.com:dominares-tools/releasetrail.git.
```
python3 -m venv .venv && . .venv/bin/activate
pip install ./releasetrail
```

Questions

Do I need GitHub?

Yes. Access is a read-only invitation to a private repository, sent to the GitHub account you choose.

Can I get a refund?

Yes, within 14 days, no questions asked. Access ends when the refund goes through. Refund policy.

Who takes the payment?

Payments are handled by Stripe, which works out sales tax. Your receipt and card statement show Link (LINK.COM*), Stripe's checkout service.

Something wrong?

Email support@dominares.org. Every buyer of a tool shares its repository, so support happens by email rather than in GitHub issues.