Skip to main content
The Free plan covers checking files and a monthly allowance of whole-project actions once you sign in. Pro is for when you want your standards applied every time, not only when someone remembers to look. Pro adds checks that can stop a push, a build or a CI run when code falls below your standard. It also removes the Free monthly limit on local project work, where that limit applies. Your account shows your current local and cloud allowances. Results you have already completed stay available after an allowance runs out or a plan ends, and your signed-in custom settings keep working. See Free allowances for the difference between new work and opening a result you already have. A 14-day trial unlocks everything, and does not require a card.

What you get

Everything in Free, plus local project work without the Free monthly limit where it applies, and paid automation:
  • Git and build hooks check your configured thresholds before a push or a build, and stop it if the code falls short. A hook is a small script that runs automatically at that moment.
  • CI enforcement applies the same standard in your pipeline, the automated checks that run after a push. Free accounts can also opt in to automatic cloud scans, within their cloud allowance.
  • Paid cloud allowance is kept separate from local actions; see Cloud overview and Scan allowances.
  • Git history secrets scans and batch file naming remain paid workflows.
  • Package guard before push can check lockfiles that changed, the files that record exact package versions. The package guard before installation remains Free.
Project scans, refactor plans, Code Map and schema results, dependency audits, findings, TODOs and reports are also available to Free accounts within their allowances. Opening results you have already earned is Free. Signed-in custom settings, scoring weights and Config Studio do not need an unused project action. The CLI and the MCP tools keep three things apart: looking at a project, reading a saved result and stopping code that fails. MCP is the connection that lets a coding agent call Iris Code. For example, iris check . --inspect asks for a look at the project, while iris gate checks it against your standard and fails if it falls short. Account Analytics and audit history show what ran in the past; they do not prove that your current code passes.

The trial

Request a 14-day trial from your Iris Code account. Requests are reviewed before they are activated, so signing in does not start one automatically. Once it is active you have everything listed above, with no card required. After 14 days the account goes back to Free unless you subscribe.
The most useful way to judge the trial is to install a hook and let it block a few real pushes. Then check Analytics for the pass and fail counts and how your score has changed since activation. That shows what blocking actually catches in your project, which a feature list cannot.

Upgrading

1

Open the pricing page

Visit iriscode.co/pricing. Prices adjust for your region automatically.
2

Request the trial

Click Request free trial, sign in with Google or GitHub, and submit from your account page. Pro turns on once the request is approved and you accept the invitation.

Signing in

1

Run the command

VS Code and forks: open the command palette and run Iris Code: Sign In. JetBrains: Tools → Iris Code → Sign In.
2

Use Google or GitHub

Your browser opens automatically. There is no separate Iris Code password to create or remember.
3

Return to your editor

You are sent back to the editor automatically, with no code to copy. One sign-in covers your editors and the iris CLI. JetBrains IDEs refresh in place, so no restart is needed.
4

Pro features activate

Iris Code’s server confirms your paid access. The sidebar then updates what you can run: blocking checks and local project work. Free actions and opening saved results are still counted separately.
Iris Code never stores your password. It saves only a licence key: in VS Code’s encrypted secret storage, or in a local credentials file shared by JetBrains IDEs and the CLI.

Your subscription

Visit iriscode.co/account/billing to:
  • view your current plan and renewal date
  • choose card auto-renew or a one-time bank transfer checkout
  • cancel or reactivate a card subscription
  • update a payment method if a saved card expires
If you cancel a card subscription, you keep Pro until the end of the current billing period.
If you are billed in Nigeria, Iris Code can open a Paystack bank-transfer checkout instead. Paystack creates an account number for that one payment, which you can pay from OPay, Kuda, Moniepoint, PalmPay or your usual bank app. It expires after about 30 minutes, and a new one is created for the next renewal.

If a payment fails

Paystack tries the charge again automatically, and Pro stays active for 3 days from the first failed charge. If none of the retries succeed within that time, Pro stops and the account goes back to Free. Iris Code emails you as soon as a charge fails. The email gives the reason your bank gave and the date access stops, and the billing screen shows both. Read the reason before you replace anything. If a card with money on it was refused for a repeat charge, that was your bank’s decision rather than a problem with the card, and paying once by hand usually clears it. Your licence key, settings and history survive a lapse. Paying again restores Pro on the same key, with nothing to set up.

Working with a team

Pro covers one developer. To hold a whole team to the same standard, Iris Code Teams adds a shared team account on top. A seat gives each member Pro, and the team gets:
  • one published standard your repositories are measured against
  • an audit trail, a record of what ran that a reviewer can read
  • a separate paid cloud allowance that grows with the number of seats
The pricing page shows the current plan quantities. Teams is billed per seat, from three seats up, and a 14-day trial with 3 seats needs no card. See Seats and billing.
A paid team seat gives you the editor and command-line features that apply to that team. Your own repositories use your personal cloud allowance separately, so joining a team does not cancel an existing personal subscription. See Team entitlement.