Pricing details
Everything behind the two plans: how placements are counted, what common sizes cost, how billing works and what a support review includes.
v1.0-RC1 is available now — signed public bundle and images, installed with one command. What v1.0 means here: expected 1 January 2027, and it does not ship before at least two customers run Stella Ops in production and the public API surface is frozen.
What each plan includes
Free
- Up to 20 managed placements, production use included
- Unlimited environments, scans and deployments
- Every capability
- All software updates, vulnerability-intelligence updates and security fixes
- Offline operation, with evidence generated and verified locally
- Documentation and automated Doctor diagnostics
Licensed
- $100 a month covers up to 100 placements
- Above 100, $1 per placement of licensed capacity, per month
- License a capacity at least equal to the placements you manage
- Above 20, every placement counts — the free 20 are not deducted
- Every capability and every update, exactly as in Free
- Support is not included: buy a review when you need one
- No per-user, environment, setup, scan or evidence fees
You can order today: email sales@stella-ops.org with your installation and the placement capacity you need, and the order is placed through an authorised merchant of record. Online checkout is coming soon.
Capacity increases take effect when you order them and are prorated from that date; decreases take effect at renewal.
If you notice you have gone over your capacity, or over the free 20, by accident, you have 14 days from noticing to reduce usage or order capacity. This does not cover deliberate or repeated excess.
Updates cover the currently supported releases under the published support lifecycle, the same for Free and Licensed; earlier releases do not receive updates indefinitely.
Prices are two fixed lists, in US dollars and in euros, with the same numbers. The page language only sets which one is shown; you choose the currency when you order.
Prices are shown excluding VAT. Any applicable VAT or sales tax is determined and charged at checkout by the merchant of record handling your order, based on your location and tax status.
Worked examples
| Managed placements | Plan | Per month | Equivalent annual cost |
|---|---|---|---|
| 10 | Free | $0 | $0 |
| 20 | Free | $0 | $0 |
| 21 | Licensed | $100 | $1,200 |
| 50 | Licensed | $100 | $1,200 |
| 100 | Licensed | $100 | $1,200 |
| 101 | Licensed | $101 | $1,212 |
| 150 | Licensed | $150 | $1,800 |
| 200 | Licensed | $200 | $2,400 |
| 360 | Licensed | $360 | $4,320 |
| 1,000 | Licensed | $1,000 | $12,000 |
Equivalent annual cost is 12 × the monthly price, shown for budgeting. It is not a separate annual plan.
What counts as a managed placement
A managed placement is one managed workload in one environment of your installation: a container service, or a digest-addressed artifact deployed to a host over SSH or WinRM; both count the same. A workload–environment relationship can count when Stella Ops deploys, gates or promotes its releases, scans its installed image or artifact, or applies an earlier scan result to that installed workload. Gating or promoting a release that another tool deploys counts the same as deploying it.
There is no per-scan charge. Scanning an installed workload's image or artifact, or applying an earlier scan result to it, can bring that workload into the placement count for each applicable environment. Each workload–environment relationship counts only once, regardless of the number of scans or reports.
Merely retaining or viewing a report solely as historical evidence does not create a placement. Presenting an earlier result as applicable scan information for an installed workload counts as applying that result.
Stella Ops establishes which workloads are installed in an environment from its deployment records, the inventory of the nodes (targets) you connect or edit, and your own declarations. Image and artifact digests identify the installed content; they do not replace the workload or environment identity.
Examples
- One workload in dev, staging and production: 3 placements
- Ten workloads in three environments: 30 placements
- A workload another tool deploys and Stella Ops gates: 1 placement per environment
- A workload another tool deploys and Stella Ops scans where it is installed: 1 placement per environment
- Applying an earlier scan result to a workload newly installed in another environment: 1 placement there, with no new scan
- A workload Stella Ops deploys, gates and scans in one environment: 1 placement
- Five replicas of one workload in one environment: 1 placement
- Restarting a workload: no additional placement
- A new image version of the same workload: no additional placement
- Scanning the same image again: no additional placement
- More vulnerability reports: no additional placement
- Scanning an image or artifact installed in none of your environments: no placement
- Keeping or viewing an old report as historical evidence: no placement
- Stella Ops' own infrastructure: not counted
Placements are counted per installation — one logical control-plane deployment of Stella Ops. Cluster nodes, database replicas and failover components of the same deployment count together; independently operated installations are separate. Environments are never priced.
A placement ends when all management of that workload in that environment actually ends, or when the workload is removed and no other management activity keeps it active. Finishing a scan does not end it, and keeping historical evidence or reports does not, by itself, create, reactivate or keep a placement.
The current release shows no placement total, so count them yourself: each workload in each environment, once, if Stella Ops deploys, gates or promotes its releases, scans its installed image or artifact, or applies an earlier scan result to it. The Estate view lists the deployments Stella Ops ran; you must also count every other qualifying workload, including those other tools deploy and any the automatic inventory does not show. How the Estate view works
One product. Every capability. Simple pricing.
Free and Licensed run the same build. The plan sets how many placements you may run in production, never what the product can do.
- Promotion workflows with approvals and policy gates
- Reachability-aware vulnerability triage
- SBOM and VEX handling
- Signed, replayable Decision Capsules
- Deployment to Docker Compose and to SSH and WinRM hosts
- Estate view with continuous drift watch
- NIS2, DORA and CRA evidence packs — they collect evidence, they do not certify compliance
- Regional cryptography profiles
- Offline and air-gapped operation
- Doctor self-diagnostics
There is no fee per scan or per deployment, and scanning the same image again never adds a placement.
Offline installations take vulnerability-intelligence updates through the Offline Kit, and feed age is reported per source, on screen.
Need an engineer? $75 per review.
One review covers one defined issue. An engineer analyses what you send and replies in writing with the likely cause and the corrective or diagnostic steps we recommend.
A review does not include unlimited engineering hours, custom development, guaranteed remediation or ongoing consultancy, and it carries no ongoing service level.
Before you buy, we give you an estimated delivery window. Once we have the information we need, we reply in writing within a reasonable time, and before we ask for logs we tell you how to send diagnostic data securely.
If the review shows that the main issue is a reproducible defect in a supported, correctly configured release, the fee is refunded — or credited, if you prefer.
Documentation, Doctor diagnostics and self-service troubleshooting are free for everyone.
Reporting a product defect or a security vulnerability never requires a paid review: report defects through the contact page and vulnerabilities to security@stella-ops.org.
To buy a review, email support@stella-ops.org with a short description of the issue.
You are never blocked waiting for us: a scoped, time-limited gate exception and Doctor's non-destructive fixes let you restore releases yourself.
Self-hosted, and still yours offline
- Your workloads, artifacts and evidence stay on your infrastructure. Routine scanning and deploying need no Stella Ops cloud service.
- The current release does not enforce the placement limit and does not check a licence, so nothing is switched off when a subscription ends. Paid capacity is licensed for the subscription term; after it, production use above 20 placements needs a renewal or a reduction to 20.
- Evidence your installation has generated stays verifiable with your installation's own trust root, with or without a subscription.
- The signed release bundle and the images download anonymously — no account, no token.
Signed releases and independently verifiable evidence
Stella Ops release bundles and container images are signed with Cosign, and the public key is published on the verification keys page. The bundle signature verifies offline.
Published vendor roots. Stella Ops publishes its vendor trust roots on the verification keys page, one per purpose, each with its key identifier. From the release after v1.0.0-RC1-20261029, release bundles carry them in config/vendor-roots/ as a pinned set; v1.0.0-RC1-20261029 predates the set and ships none. A root that arrives inside the material being verified is never trusted: stella self update in v1.0.0-RC1-20261029 verifies an update manifest only against roots you configure, and refuses a kit that brings its own.
Vulnerability intelligence you can check. Since 2 November 2026 the vulnerability database at mirrors.stella-ops.org/vuln-db/ is signed with the vendor-intelligence root. Its signed manifest lists every file with its SHA-256 digest, and the version and publication time of the advisory snapshot it was built from. From the release after v1.0.0-RC1-20261029, stella sbom check verifies that signature before it decides: it refuses an altered database, and an unsigned one unless you pass --allow-unsigned. In the same release the Vulnerabilities hub refuses an unsigned or altered mirror seed, and the CLI and the console show which snapshot a decision used and when it was published. v1.0.0-RC1-20261029 does not check these signatures.
Evidence your installation generates is signed with your installation's own keys, not ours, and verifies offline against the trust root you declare: stella evidence verify-offline <bundle.tgz> --trust-root <keys.jwks.json|key.pem>.
The two answer different questions: a release signature shows that a bundle came from Stella Ops; an evidence signature shows that a record came from your installation.
Questions about pricing
- What is a managed placement?
- Do replicas, restarts or new versions add placements?
- Is one workload in three environments one placement or three?
- Do scans or deployments cost extra?
- What happens above 20 placements?
- Why does the first paid month cost $100?
- What happens if my subscription ends?
- Does an offline installation need to contact Stella Ops to stay licensed?
- How is my paid capacity recorded?
- How can I verify Stella Ops evidence?
- Can AI agents, automation and other scanners work with Stella Ops?
- What does a $75 support review include?
Who you buy from: Paid Stella Ops plans are sold through authorised resellers acting as merchants of record. The merchant of record for your order is the contracting seller for order processing, payment, applicable taxes, invoicing, chargebacks and transactional refunds under its Buyer Terms and Privacy Notice. Legal notice
Go deeper
Pricing and licensing FAQ All capabilities Deployment targets and operations Decision Capsules and replay NIS2 · DORA · CRA packs Regional cryptography Licence and free-tier terms Vendor security review
