Pricing
$50 per project.
Per month.
Then $40 a month for every project after the first. One plan, no seats, no tiers to compare.\n\nReading your code is free. Changing it is what you pay for.
What one licence covers
A project, and the capacity to work on it
These are the four things the platform measures. A project inside all four is one licence, whatever it is written in and however many files it has — file count is not the cost, size is.
| Per licence | Why this is the number | |
|---|---|---|
| Your code | 2 GB |
The working tree — not git history. Check it yourself with du -sh --exclude=.git. |
| Repositories | 5 | A front end, an API, infrastructure, and room for two more. |
| Tasks at once | 3 | What your work occupies on our machines while it runs. |
| Deployment targets | 2 | Staging and production, or two environments of your choosing. |
Everything else is uncapped: requests, agent runs, team members, history, investigations. There is no monthly allowance to use up.
Projects bigger than one licence
A large project uses as many licences as it needs
Rather than a separate enterprise tier with a conversation attached, a heavy project simply consumes more of the same unit — and every axis scales with it.
Worked example
A 6 GB monorepo is three licences
$50 for the first, $40 and $40 for the next two — $130 a month. With it comes 15 repositories, 9 tasks at once and 6 deployment targets, because the capacity multiplies too.\n\nMost projects are one licence. This is what happens when yours is not, and it is arithmetic rather than a sales call.
If you outgrow it mid-month
Nothing is cut off
Work already running finishes — a build mid-flight, a deploy mid-flight, an investigation mid-flight. What pauses is new work, until you add the capacity.\n\nWe are not going to stop your deploy over a gigabyte.
Free, and not a trial
Reading is free. Changing is paid.
Point Capy at your repositories and it reads the project and writes back what it found: what the system is, what it is built from, how the parts relate, and where the sharp edges are.
What free covers
The assessment, on our account
That read costs real money in AI work and we pay for it, on our own keys, before you have paid us anything. No card, no countdown, and the document is yours whatever you decide next.
Where paid starts
The first change
The moment you want something built, tested, reviewed and shipped, that project needs a licence. It is a clean line: you know exactly what you are buying, and you have already seen what Capy makes of your code before you buy it.
The AI work
Your subscription, at no mark-up
Connect your own Claude or Codex subscription, or an API key, and the work runs on it. We add nothing to it.\n\nThat is deliberate, and it is why the price above is a flat figure. If compute were folded in, a month where you shipped a lot would arrive as a bigger invoice — a price rise for doing more of exactly what you bought the thing for. Capacity is ours to price; consumption is yours to control.\n\nIf you would rather not manage a provider account, you can buy credits and spend from those instead.
The questions this raises
What $50 is actually paying for
If I bring my own AI subscription, what am I paying you for?
The standing capability around the work. We pay for the assessment that reads your codebase, on our own account, before you pay us anything. Your project then occupies disk continuously — the repository plus an isolated copy per task in flight — and its runs, tests and builds execute on our machines. And it is watched: health checks, automatic rollback and an investigation that opens itself happen whether or not you filed a request this month.
Why is a dormant project still charged?
Because dormant is not idle. The understanding of the codebase is kept current, the deployment is still watched, and the capacity is still held. A project you did not touch this month is one you can touch tomorrow without a fortnight of re-learning first.
Why measure storage rather than files or lines?
Because size is what costs us and file count is not. Ten thousand files of Python is a small project; ten thousand images is not. Storage tracks how heavy a project actually is to hold and to work in.
Does my git history count toward the 2 GB?
No. The measurement is your working tree — the code as it stands — and you can check it yourself with du -sh --exclude=.git. We keep the full history because the agents need it, and we absorb that cost. A repository with a decade of commits can be more than twice its working tree, and charging you a second licence for 2019 would be indefensible.
What happens if my repository grows past 2 GB?
Work already running finishes. New work waits until you add capacity, which is one more licence at $40. Nothing is deleted and nothing is cut off mid-flight.
Is there a discount for many projects?
Yes — the first project is $50 a month and every project after it is $40. Fifteen projects is $610 a month rather than $750. Annual billing is ten months for twelve on top of that.
Do you charge per user?
No. Viewers and collaborators are free, however many of them there are. Put your whole team and your client in to watch; it changes nothing about the price.
What is not included?
We hold no SOC 2 and offer no contractual uptime SLA today, and say so on the security page rather than in a footnote. If you need either contractually, we are not your platform yet.
Something not answered here? Ask us — a person replies.
Find out what you own before you pay for anything
Point Capy at a repository and read what comes back. The assessment is free, on our account, and commits you to nothing.
Free · no card · $50 a month when you want the first change made