Skip to main content
Free explains findings in the code you are reviewing. Pro adds repeatable project-wide checks and enforcement at push, build, and CI boundaries. Free gives you unlimited file scores, clickable findings, secrets detection and one saved workspace scan, which is enough to review your own work properly. What it does not give you is the ability to rescan the whole project whenever it changes, or to put a gate in front of a push. A 14-day trial unlocks everything, and does not require a card.

​
What you get

Everything in Free, plus:
  • Cloud scans - connect a GitHub repository and it is audited without your editor open, with every report pinned to the commit that produced it. Includes 50 scans a month; see Cloud overview and Scan allowances
  • Fresh workspace reviews - rescan the whole project whenever it changes, rather than relying on one saved snapshot
  • Folder analysis - scoped scans for any directory in your project
  • Gate Preview drilldown - which files fail each preset, with their scores
  • Git hook enforcement - blocks a push when any file falls below your threshold
  • Build hook enforcement - stops a failing build before compilation begins
  • Dependents table - version audit and CVE scanning for every dependency
  • Issues tab - every blocker and warning from the latest scan, filterable
  • TODOs tab, aggregating every TODO, FIXME and HACK in the project
  • Custom .irisconfig.json - override individual thresholds, detections and severities per rule
  • Custom enforcement limits - hard caps on secret count, complexity, file size, smell density and security smells
  • Custom scoring weights - control how many points each finding type deducts
  • Config Studio - build, preview and sync a config visually
  • Unlimited trend history, rather than two rolling snapshots
  • The full CLI: iris gate for CI, iris deps and iris cve for dependencies, iris sbom, iris todos, iris hook install, and iris check on directories and staged files
  • Account Analytics - your health trend plus a private timeline of scans, hook results, blocked pushes, completed cloud scans and other recorded signals
  • Personal audit history - one commit-pinned history of cloud scans across all repositories connected to your account

​
The trial

Request a 14-day trial from your Iris Code account. Requests are reviewed before activation, so signing in does not start one automatically. Once active you have everything listed above with no card required. After 14 days the account reverts to Free unless you subscribe.
The most useful way to evaluate the trial is to install a hook and let it block a few real pushes, then check Analytics for the pass/fail counts and the score delta since activation. That gives a concrete picture of what enforcement is catching, which a feature list cannot.

​
Upgrading

1

Open the pricing page

Visit iriscode.co/pricing. Pricing adjusts 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: command palette, 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 redirected back automatically, with no token 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

Pro unlocks immediately. The sidebar updates, and workspace scans, hooks and the Pro tabs become available.
Iris Code never stores your password. Only a licence key is saved: 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
Cancelling a card subscription retains Pro access 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 generates a transaction-specific account number you can pay from OPay, Kuda, Moniepoint, PalmPay or your usual bank app. It expires after about 30 minutes, and a fresh one is generated for the next renewal.

​
If a payment fails

Paystack retries the charge automatically, and Pro access stays active for 3 days from the first failed charge. If none of the retries land inside that window, Pro stops and the account reverts to Free. Iris Code emails you as soon as a charge fails. That email quotes the reason your bank gave and names the date access stops, and the billing screen shows both. The reason is worth reading before you replace anything: a card with money in it that was refused for a recurring charge is a decision by your bank 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. If you want the same standard held across a team, Iris Code Teams adds a shared workspace on top: a seat gives every member Pro, one published standard your repositories are measured against, an audit trail a reviewer can read, and 100 cloud scans per seat per month. 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 team seat grants Pro in your editor, so most members need nothing else. A personal Pro subscription is still the only thing that cloud-audits your own repositories, which is why Iris Code does not cancel one when you join a team. See Team entitlement.