Release control for VMs, Docker Compose and plain servers

Signed evidence, from source to environment.

One self-hosted control plane scans your images, gates each release on policy and reachable risk, deploys what passes, and watches what runs. Every artifact carries proof of what is inside it, what is reachable, and who approved it — verifiable long after the release.

Built for technical teams under audit pressure

Reachable vulnerabilities | Source to environment | Signed evidence | Compliance packs | Offline-ready
v1.0-RC1 — release candidate. v1.0 is expected on 1 January 2027; pre-orders are open now. Signed v1.0.0-RC1 images and the install bundle are both public — download and pull anonymously, no account needed.

Decision

Gate evaluation: reachable risk, not raw counts

Every allow or block traces to its inputs: SBOM, reachability verdicts, VEX status, policy snapshot, approvals. “Why was this blocked” is a lookup, not an investigation.

Promotions screen in the Stella Ops console: six lifecycle states from awaiting approval to retired, with per-promotion status and risk signal
Promotions in the Stella Ops console, shown with demo data. Every promotion is in exactly one lifecycle state, and its gate posture travels with it.

A check that could not run is reported as NOT EVALUATED and recorded in the verdict. It is never counted as a pass.

See the gate model

Chain of custody

Source → Build → Scan → Verdict → Decision → Deploy → Watch

Every release moves along this seven-stage spine. Each stage carries one of three evidence states. A stage without evidence stays visibly empty — nothing is inferred to fill the gap.

Chain of Custody screen: seven stages from Source to Watch, each marked Missing, Recorded, or Signed
Absent evidence is shown as Missing, never faked. Stella Ops console, demo data.

MISSING

No evidence captured for this stage yet. The stage stays a visible gap.

RECORDED

Evidence captured and linked to the release digest, not yet signed.

SIGNED

Evidence sealed with a verifiable signature, made with a key generated inside your own installation — the product ships none. Checked against a trust root you configure, never against a Stella Ops service.

What you get

See the gap, the moment it opens

After deploy, Watch compares the running digest against the approved one — every service, every environment. A mismatch means an unapproved or altered image, flagged with the evidence that shows it.

A release is proven at deploy time. Watch is how that proof stays current afterwards — drift detection is a first-class stage of the custody spine, not an add-on.

See the estate view
Estate screen: a matrix of services against environments, above an open deviations panel listing running containers whose digest is not an approved one
Estate view: every running container whose digest is not an approved one, flagged as drift. Stella Ops console, local development stack.

Check the proof first: The evidence model, the signing keys and the replay workflow are public. Verify them before you trust anything else on this page.

Customer references are coming soon — results from our internal beta.

Review evidence model Verify signing keys See replay workflow

Prove your next release

Free tier: 3 environments, 999 new-digest scans per rolling 24 h.

Start free and self-hosted. Move to a paid plan when you need more environments or scan volume — every capability is in every tier.

Compliance packs map custody evidence to NIS2, DORA and CRA obligations — evidence-only mode; they do not claim regulatory compliance. A published example capsule can be verified with stock cosign, no Stella Ops install required.