Plans and limits
Free, Pro and Teams plans, how lines are counted, what happens over the limit, and what leaves your machine.
You choose a plan when niro start signs you in. Run niro plan to see yours, the lines you use against its limit, every indexed folder (largest first), and your options.
Plans
| Plan | Price | Line limit | Code shared |
|---|---|---|---|
| Free | $0 | Up to 500,000 lines of code, or no line limit while code sharing is on | Only while you turn sharing on |
| Pro | $20/month, with a 30-day free trial | No line limit | Nothing unless you choose to |
| Teams and enterprise | Custom, by request | No line limit | Nothing unless you choose to |
You can turn sharing on or off at any time under Settings, Privacy in the Niro console. Turned off on Free, the line limit applies again.
How lines are counted
The limit is the total across every folder indexed on your machine. Every line of every indexed file counts, blank lines and comments included (the same number wc -l gives). Each project counts once, by its largest folder: two checkouts of one repo are not counted twice.
Over the limit
- A build starts while you are under the limit, and the build that takes you over is allowed to finish. After that, new builds stop until you choose how to continue.
- The graph you already have keeps answering your assistant in the meantime.
niro start,niro initandniro plantell you when you are over, and open the console's /limit page with three ways on:- Unlock unlimited lines on Free by turning on sharing of redacted code.
- Request a Pro free trial (30 days, no line limit, nothing shared).
- Stay under the limit with
niro plan remove <folder>, which stops indexing a folder and frees its lines. Your code is not touched.
For scripts, niro plan --json prints the same numbers.
What leaves your machine
- Your account. Sign-in, and your plan's licence (which plan, its line limit, whether sharing is on), renewed while Niro runs.
- Which tools were used, on every plan. A record of which Niro tools your assistant called, how long each took and whether it failed, plus whether Niro helped and how many native calls it saved. No source code, no file names, no class names and no free text.
- Coverage findings, on every plan. When a file has something the graph missed (a class or a route with nothing in the graph for it), that file's path inside the repo and its source are sent so the parser can be fixed. Before sending, Niro removes secrets, author names and company names it can recognise (your email domain, the git remote's owner, copyright holders). Usually a handful of files per repo.
- A whole repository, only when you choose to.
niro audit-push-reposends a repo's full source, and only when sharing is on and your plan includes it. It asks first and never runs on its own.
Your graph, your questions to the assistant and its answers stay on your machine.