Skip to main content
The Free plan lets you check files as you work, and run bigger whole-project jobs a set number of times each month. That monthly amount is your allowance. Your account shows how much you have, how much you have used and when it resets. Checking single files does not need an account. Sign in to get a monthly allowance of project actions and cloud scans. The browser Playground is a separate free sandbox and does not use any of your allowance.

​
Launch allowances

During the launch offer, a personal Free account gets 12 local project actions and 4 cloud scans monthly. A local project action is one whole-project job on your machine, such as a workspace scan. A cloud scan is a scan of a connected GitHub repository, run on Iris Code’s servers. A Free Team shares 36 local project actions and 12 cloud scans monthly, with room for three collaborators and three active projects. A personal Free account also has room for three active projects. These amounts are set on Iris Code’s servers, so your account always shows the current figures if the offer changes or is paused. Free allowances reset monthly, on the first at 00:00 UTC. Paid and trial allowances are kept separately.

​
What stays Free without a monthly action

  • Health scores, blockers, warnings and secrets checks for supported files.
  • Safe fixes and refactor plans for one file.
  • Import information for one file, the structure of your database schema, and how one table is used.
  • Project rules for coding agents, and the package guard, which checks a package before it is installed.
  • Opening, filtering, explaining, comparing or exporting a result you have already earned.
Signing in also lets your own settings change the checks you are allowed to run. Saving settings does not use an action or turn on a hook. Your settings keep working after your allowance runs out.

​
What uses a local project action

Each completed new scan of a folder, the whole workspace or your changed files uses one local project action. The workspace is the project folder open in your editor. A separate refresh of a dependency audit, which checks the packages your project uses for known problems, also uses one action. So does a new multi-file refactor plan. One scan can produce several views. Opening its findings, TODOs, Code Map, schema usage or report does not use another action.

​
Partial, failed and unclear results

  • Partial result: a result that is usable but incomplete can still count. It must say what it left out.
  • Failure or cancellation: if a scan is confirmed to have failed, or you cancel it, the action is given back.
  • Unclear outcome: if Iris Code cannot yet confirm what happened, the action is held as awaiting confirmation. It is not charged a second time, and it is not assumed to be refunded.

​
Reusing results

If nothing has changed since a valid saved result, Iris Code can reuse it. Choosing to refresh asks for new work. A dependency audit also depends on outside security advisories, which change over time and have their own freshness period. So a refreshed audit can differ even if your package list has not changed.

​
Separate cloud allowance

Cloud scans have their own allowance, separate from local project actions. Connecting GitHub is a deliberate choice to let Iris Code read the repository you select; checking files on your machine never does this. A dependency audit included in a cloud scan does not use a local action. Repositories start in manual mode, so they are scanned only when you ask. You can choose to scan automatically on each merge or pull request. Automatic scans come out of the same monthly cloud allowance as manual ones and stop when it is used up. Your cloud allowance shows the current amount and reset date. Free allowances reset monthly, on the first at 00:00 UTC. Buying Pro or starting a trial does not top up a Free allowance; paid and trial cloud allowances are kept separately.

​
Keep your results

Using up your allowance does not delete a finished scan or a refactor baseline, the saved starting point a refactor is checked against. Each result keeps the files and settings it captured, the exact build of the checks that produced it, the time and how much it covered. Changing your code later does not rewrite that saved result. Opening a saved result does not quietly scan your current files. Check its age and coverage before you use it to decide what to change. A good score or a passing gate does not prove that the program works correctly. Keep running your tests and reviewing changes.

​
Multi-file refactor plans

A refactor plan lists changes that restructure code without changing what it does. A multi-file plan already includes applying its approved fixes and verifying the result against the starting point the plan was made from. A different plan, or a plan made from a changed starting point, counts as new work. When fixes are corrected automatically, those attempts have their own limited count, and reopening the plan does not reset it.

​
Personal accounts and Free Teams

Personal and team allowances are separate. A personal Pro subscription does not turn a Free Team into a paid team, and a paid team seat does not buy cloud scans for your personal repositories. A Free Team shares one local allowance and one cloud allowance. Members shows how many collaborators and projects the team can currently have. The owner counts as a collaborator, and pending invitations hold a place. Owners and admins choose which members and projects can start new Free work. A member or project left outside those active places keeps its membership, saved results, history and team policies. Paid seats and Free places are separate controls. After a downgrade, choose who and what stays active rather than deleting people or records. The optional Pro trial starts only when you request or deliberately activate it. Creating a Free Team does not start a trial.

​
Offline and temporarily paused work

File checks and results you already own keep working offline. New Free project work needs a connection, so Iris Code can check your allowance. Paid plans can keep working offline for seven days after the last successful licence check. That permission is tied to your account, the server and the account or team you selected. If you upgrade from an older CLI that saved a paid licence, it must check that licence online once before the upgraded version trusts it. That check creates the record, tied to your sign-in, that later offline use relies on. If new Free work is paused for a while, Iris Code tells you. Your existing results stay readable. A pause on Iris Code’s side does not mean you now need to buy Pro.

​
Check usage from the terminal

The CLI is the set of commands you run in a terminal. Run these from the project whose allowance you want to see:
  • status shows the allowance for the account or team selected for this project.
  • results lists the results saved on this machine for your account, and result opens one without scanning again. A result’s evidence ID identifies that saved result.
  • recover sorts out actions whose outcome was never recorded, for example after a crash. It does not run a scan, guess a refund or charge a second action.
In the editor, open Account, then Usage, and choose Reconcile interrupted actions. If a request still needs a decision, the editor asks you before giving the action back. Confirm only work that has stopped without a usable result; do not give back an action that is still running. The terminal equivalent is iris usage release <request-id> --confirm-failed, using a request ID that iris usage recover lists as unresolved. Saved results are matched up first. An action that succeeded cannot be given back, and neither command starts another scan. You can open the same saved result in several CLI views:
The requests that keep count of your allowance contain identifiers and counts, not source code. They are separate from the optional account analytics. Refactor baselines can contain source code, stored privately on your machine. Treat the local account storage with the same care as your project files.

​
What Pro adds

Pro removes the Free monthly limit on local project actions where it applies. It also adds checks that run every time and can stop code at a hook, a build or CI. Paid cloud scans still have their own allowance. See Iris Code Pro for the paid features and team entitlement for how access works in each team.