Skip to content
CLEARANCE
—
Pricing

The CLI is free.
Nothing else is for sale.

A licence tool that gates its own verdict behind a paywall would be a joke the internet would make for years. So the scanner is free, under the Functional Source License (FSL-1.1-ALv2) — source-available, not open source.

There is no paid tier to buy. No accounts, no seats, no hosted API, no checkout. The free column below is the whole of it.


Capability Price
Local scan + verdict✓
Code licence layer✓
Weights + platform-ToS layer✓
Corpus bundle (signed, verified on load)✓
CI gate, SARIF and markdown output✓
Price €0

01

Not built, not scheduled, not for sale

The pages on this site that show a console, a hosted policy store, a signed PDF statement or a vetting API are interface sketches. None of them exists. None of them can be bought, and none has a date. They are listed here so the line between the sketch and the product is written down.

Hosted
Console, repositories, retention

Accounts, connected repositories, stored scans and retention policies. Nothing is hosted.

Hosted
Organisation policy store

A shared policy store with an audit trail. The local config file does the same job for one repository, for free, today.

Hosted
Vetting API

Throughput, a hosted corpus and a signed response. No endpoint exists; nothing answers a request.

Artefact
Signed PDF statement

An artefact with an accountable issuer. Only the Ed25519 corpus signature exists; no statement is signed or issued.

Enterprise
SSO / RBAC

Hosted infrastructure. There is no server to authenticate against.

Human
Support and SLA

No support contract, no response time, no SLA. There is no community forum either; issues go to the public tracker.


02

Why the CLI is free forever

This is a strategy decision, not generosity. Six reasons, and each one is a reason a paid CLI would fail.

Adoption
A paid CLI is not adopted

The install must be one command and zero friction. Every step between a developer and a verdict loses most of them.

Distribution
The CLI is the funnel

If there is ever revenue, it comes from a hosted service, not from the binary. Charging at the top of the funnel means never reaching the bottom of it.

Trust
A paywalled verdict is a punchline

In this category specifically, charging for the answer destroys the only thing being sold.

The fork
A paid CLI invites a free fork

A free CLI with a paid service does not. The moat would be the signature and the freshness, which a fork cannot reproduce.

The moat
What is actually scarce

Freshness, scale, accountability and a signature. None of those are features. All of them would be services.

The rule
Never paywall a capability

If a self-hoster can already do it, it is not for sale. That is the line, and it is written down.


03

Where the paid boundary would be drawn

At the service, not the feature. Three rules, applied consistently. These are the rules any future paid work would have to obey; no such work is on sale.

Rule 01
FSL-1.1-ALv2, never AGPL

The CLI is source-available under the Functional Source License, with the ALv2 future grant named in the same licence — free to run, free to read, and not open source. A licence checker that mislabelled its own licence would be the one joke this category could not survive.

Rule 02
CC-BY-4.0 data, FSL-1.1-ALv2 code

The corpus wants to be quoted, cited and mirrored, so it is data under CC-BY-4.0. The code is a product, so it is source-available under FSL-1.1-ALv2. Different objects, different licences.

Rule 03
Paywall the service, never the feature

Pay only for what a hosted service can uniquely do: freshness, scale, accountability, a signature.

Applied — what a paid boundary would have to be, and why each is a service
Would be paywalledWhy it is a service and not a feature
Org policies at scaleA hosted policy store with an audit trail. The local config does the same thing for one repo — for free, today.
The vetting APIThroughput, a hosted corpus, and a signed response. The engine would be identical; the scale would not be.
Clearance statementsA signed artefact with an accountable issuer. You can render the markdown yourself; you could not sign as us.
SSO / RBACHosted infrastructure. Nothing to do with licence knowledge.
Audit retentionStorage, and the liability of holding it.
Support / SLAHuman time. The one thing a solo founder genuinely cannot give away.

04

Three channels that are planned, not open

Including the one that is deliberately capped, because a service business that drifts into consulting stops being a product. None of these can be bought, booked or subscribed to today.

01planned
Platform vetting API

Registries must vet at scale. Usage-priced, so the revenue would grow with the customer's catalogue rather than with a seat count. No endpoint exists.

Pricingnot set
02planned
Clearance audits

A human-verified statement for a launch or a diligence process. Genuinely valuable, and genuinely a distraction — so the intent is to cap it at four per year. Nothing is bookable.

Pricingnot set
03planned
Corpus sponsorship

A vetted-vendor badge, low effort and modest revenue. It exists because vendors already ask for it, not because anything depends on it. There is no programme to join.

Pricingnot set
The rule is explicit about what is not for sale: the corpus itself, the verdict, and any capability a self-hoster already has. If a future version of this page breaks that rule, the rule was wrong — not the page.

Start with the free one.

The CLI answers the question. If it turns out the answer is worth attaching to a contract, you will know by then — and so will we.