Licence and plans
Niro runs on your computer, but it needs a Niro account. The account carries your plan, and the plan sets how many lines of code you can index. You sign up at console.niroai.dev.
The plans
| Plan | Lines you can index |
|---|---|
| Free | 500,000 lines |
| Free, with code sharing on | No line limit |
| Pro trial | 30 days |
niro plan shows your plan, the lines used, and the folders using them. The limit itself comes from your account, not from the niro command.
What "code sharing" means
Code sharing is a switch on your account. It is called "Share redacted code" and lives in the console, at Settings, Privacy (console.niroai.dev/settings?tab=privacy). It is not the same as the coverage audit, which is sent on every plan (see Coverage audit).
With sharing on:
- On the Free plan, there is no line limit.
niro planshows "no line limit while you share". - The background watcher shares your code by itself. Every 5 minutes it sends the files Niro indexes in each folder on your computer: the source files it parses and the config, build and text files it reads, never a gitignored file, a real
.env, a key ornode_modules. Secrets are masked and author and company names removed on your computer first. The first time, a folder's whole indexed set goes; after that, only files that changed. Turning sharing off in the console stops it: nothing more is sent after the next check. - You can keep a folder out while sharing stays on:
niro share exclude <folder>(and every folder inside it).niro sharelists the folders kept out,niro share include <folder>shares one again, andniro planlists them too. - You may also send one folder at once, with
niro audit-push-repo, and answer yes. It sends the same files with the same redaction, and refuses a folder you excluded.
niro plan shows the switch in its "Help improve Niro" block.
How lines are counted
- Every line of every file Niro reads counts, blank lines and comments included.
- Two copies of the same repository count once, by the larger. So branches and worktrees do not use up your plan.
- Different repositories add up.
- A folder inside another indexed folder is counted once.
At the limit
- The build that crosses the limit finishes.
- After that, a new folder is refused. You see "Not built: this machine already holds N lines of code, over the M line limit", and a page in the console opens to help you choose what to do.
- Folders already indexed keep rebuilding. So do new branches and worktrees of them.
Your three ways forward, as niro plan lists them:
- Turn on "Share redacted code" in the console, for no line limit on the Free plan.
- Ask for a Pro free trial at
console.niroai.dev/request?plan=pro. - Stay under the limit. Stop indexing a folder with
niro plan remove <folder>.
How the licence works
Every time the engine starts, niro-cli asks Niro's billing service for a short-lived licence (a lease). It hands the licence to the engine directly, without writing it to disk, and renews it before it runs out.
- Offline: if the service cannot be reached, the engine keeps working for up to a day. You see "Could not renew the local engine's licence: ... It keeps working offline for up to a day."
- Refused: if the service refuses (for example, the account is closed), the engine stops at once, with "Niro will not license the local engine: <reason>".
- Typed by hand: this is why
niro-local buildtyped by hand is refused, andniro buildis the command to use. The engine gets its licence only from niro-cli.
Your account
- Sign up: console.niroai.dev.
- Delete your account: email help@niro.ai.