Pricing

Free while we build

There is no price yet, and this page says what is decided rather than pretending otherwise. Nothing to pay, no card, and no bill waiting once your codebase is mapped.

£0
during beta
No card
to get started
60 days
notice before anything changes

1. What it costs today

Nothing, and there is no card to enter.

cleap is in early beta. Connect a repository, map it, invite your team, use all of it. We are not metering anything, and we are not going to quietly start.

The reason is not generosity. We are still learning what people actually use, and charging before we know that would mean guessing at a price and then defending the guess.

2. What stays free

The part that reads your code will be open source, and the line is already drawn.

The open half

Committed, not published yet. Yours to run, fork and keep when it is.

  • The parser and every language extractor
  • Running it yourself, on your own machine
  • Reading your own repositories with it
  • Anything you build on top of it

The hosted product

Free during beta. Paid when we launch pricing.

  • The hosted map, kept in sync for you
  • Search, trace, Ask and generated documents
  • Workspaces, roles and shared annotation
  • The showcase, and public sharing

Not published yet, and we would rather say so. The repository is still private. Opening it is a planned step, not a shipped one, and a page that claimed otherwise would be the first thing you found out we were wrong about. What is decided is where the line falls, which is the part you would want to know before adopting anything.

The split is not a marketing decision made late. It is in the product's own requirements, and it exists for a reason that also serves you: the parser is the part that touches your source, so it is the part you should be able to read, run and audit without trusting us at all. It is also the part with the most ongoing work, and open extractors mean a language we have not reached yet can be added by someone who needs it.

What you pay for, when you pay, is the hosted half: keeping the map in sync, serving it fast, and everything a team does on top of it. What cleap keeps describes exactly what that hosted half holds.

3. The shape of paid

Per seat or per repository. Never a share of your revenue.

We do not have a number. We do have a shape, and the shape is the part you can plan against: when pricing arrives it will be a straightforward subscription based on how many people use it or how many repositories it maps. Probably a free tier that stays genuinely useful for one person and one repository.

Not a percentage of anything. Some developer tools price as a share of the revenue that flows through them, which makes sense when the tool sits inside a payment flow. cleap does not. Taking a cut of something we have no part in would be a number picked from the air, and you would be right to distrust it.

Not usage-metered either, if we can avoid it. A tool you consult when you are confused is a tool you should never hesitate to open.

4. What we commit to

Three things, so a decision to adopt cleap now is not a risk later.

Sixty days' notice. If we introduce a price, everyone using cleap hears it directly, at least sixty days before it applies. Not a banner, and not a change buried in updated terms.

Beta users keep something for it. People who used cleap while it was rough and told us what was wrong will not be treated the same as someone arriving after it works. We are not going to promise a specific discount we might not be able to honour, but that is the intent and we will be specific when we can be.

Your data leaves with you. If the price does not work for you, disconnect and everything derived from your code goes. The map is rebuilt from your repository, so there is nothing here you need us to hand back: your code was never the thing we were holding.

5. Why there is no number

Because we would be guessing, and you would be planning around the guess.

We could put a plausible figure on this page today. Most products at this stage do. It would be a number chosen to look reasonable rather than one derived from what the service costs to run or what it turns out to be worth, and the first time we learned something real we would have to change it.

Naming the shape, the split and the notice period is what actually answers the question underneath “how much”, which is: can I adopt this without being trapped later. If you need a firmer answer than this page gives before you can commit, write to us and say so. That conversation is more useful to us than a guessed price on a page.