Self-hosted. For Docker Compose, VMs and plain servers, not Kubernetes.

One system to approve, deploy and prove container releases outside Kubernetes

Stella Ops runs on your own servers, next to your CI. It scans each image, checks each promotion between environments against the policy you set, including reachable riskVulnerabilities whose code your application actually calls — the ones that can affect you, rather than every CVE present in the image, signs the decision, and deploys to Docker Compose projects and to servers over SSH or WinRM.

Free in production for up to 20 placements per installation. One placement is one app in one environment. Current release: v1.0.0-RC1-20261110, a release candidate.

Teams outside Kubernetes release with a scanner, a deployment tool or scripts, and approvals in tickets. Each part works, but nothing joins them, so nobody can show which image was approved, why, and where it was deployed.

Stella Ops joins those steps. For each release it records which image was scanned, why it was approved or blocked, and where it was deployed. After a Docker Compose deployment, it also checks that the running containers use that image.

Watch it run · 4 min

A promotion blocked at the gate and another approved, the deployment that followed, and the signed record behind each decision.

How it works in three steps

  1. Connect

    Connect your container registry, add a Stella Ops CLI step to the CI you already use, and run the Stella Ops agent where it can reach your servers.

  2. Decide

    No image is deployed until it has been scanned, and each promotion is checked against the policy you set and waits for your approvers where you require them. A check that could not run is shown as NOT EVALUATED, never as a pass.

  3. Deploy and keep proof

    Releases that pass deploy to Docker Compose projects or to servers over SSH or WinRM, and a failed Docker Compose deployment rolls back to the revision that ran before. Each promotion decision is signed and sealed into an evidence bundle that can be exported and verified offline.

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 a sample estate. Every promotion is in exactly one lifecycle state, and its gate posture travels with it.

See the gate model

Who it is for

  • Platform and release leads who deploy containers to VMs and servers with Docker Compose or scripts, and promote between environments through tickets.
  • Security leads who want the policy they set, not the length of a scan report, to decide what stops a release.
  • Compliance and audit owners (NIS2, DORA, CRA) who must show who approved a release and on what basis.
  • Air-gapped and sovereign operators who cannot send release data to a hosted service.

Not for you if everything you run is on Kubernetes.

Not just a scanner. Not just a CD tool.

Stella Ops is the layer between your registry and your deployment targets. It answers the question scanners can't: "Is this image safe to promote, and can I prove it later?"

Full comparisons

Check the proof first: The evidence model, the signing keys and the verification steps are public. Check 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 how verification works

Prove your next release

Free: 20 managed placements · Licensed from $100/month · every capability in both

One placement is one app in one environment. Replicas, new versions and repeat scans never add another.

Complete release control for your own infrastructure. Scan, approve, deploy and verify container releases with one self-hosted system. Every capability is included. Start free with 20 managed placements, then pay from $100/month.

Compliance packs map your custody evidence to what NIS2, DORA and CRA ask for — they gather and organise the evidence, they do not certify that you comply.

See pricing