Give coding agents your project rules, check every change independently, and stop work that falls below the standard before it reaches review. Local analysis runs without sending your source to Iris Code or another model.
2 blockers across 14 changed files.
pre-push hook - exit 1Runs in the editors you already use. Understands the stack you already have.
Start with immediate file feedback, choose the limits that fit your project, then use the same configuration in the editor, hooks, and CI.
Open a file and Iris Code checks complexity, size, duplication, security patterns, and committed credentials on save. Every finding points back to a rule you can inspect.
Preview six presets against your own repository before enabling one. The selected limits live in a committed .irisconfig.json that developers and coding agents can share.
Applying a preset writes one .irisconfig.json.
Use the same configuration for editor diagnostics, pre-push and build hooks, and the CI gate. When a change crosses the line, Iris Code names the rule, file, and location that failed.
Review staged, unstaged, and untracked files together. Iris Code puts security blockers first and links every finding to the line that caused it.
Change review is free, and the diff never leaves your editor.
Iris Code writes your configured limits into the instruction files coding agents already read. Through MCP, an agent can also request the real findings and gate result instead of guessing what your project considers acceptable.
iris_checkFindings with rule ids and linesFree / Proiris_configThe project's resolved limitsFreeiris_fix_safePreview, then apply, safe fixesFree / Proiris_explainThe rule detail behind a findingProiris_gateWhether the gate would passProiris_check_dependencyOSV advisories for a packageProAGENTS.mdCodex, Cursor, CopilotFreeCLAUDE.mdClaude CodeFreeCursor rulesCursorFreeCopilot instructionsGitHub CopilotFreeIris Code checks security, complexity, duplication, dependencies, naming, and maintainability. It shows the rule and underlying evidence instead of asking a model for an opinion.
Every file scored out of 100 from complexity, size, smells, and security signal. The same file always produces the same number.
API keys, tokens, and passwords caught in source and in configuration files, with the value masked everywhere it is reported.
eval and exec, SQL built by string concatenation, insecure randomness, weak hashing, and unchecked process execution.
Every function listed with its cyclomatic complexity and exact line numbers, so a long function is a line reference, not a feeling.
Repeated logic matched across the workspace after comments and formatting are stripped, so a copy is found even when it was retyped.
Eight package ecosystems audited against OSV advisories, with the nearest fixed version and a CycloneDX 1.5 SBOM export.
Path-aware snake_case, kebab-case, camelCase, or PascalCase rules with framework exemptions and baseline-aware rollout.
Recurring workspace issues ranked by density and impact, with the raw counts kept visible instead of rolled into one grade.
Scan read-only against six presets and see exactly which files would fail before any threshold is switched on.
The same analysis core produces consistent findings in VS Code, JetBrains IDEs, the CLI, and CI. Each language uses its own parser, and unsupported checks are omitted instead of approximated.
Complexity, functions, smells, secrets, naming, and duplicates, with language-specific rules where the language earns them.
Per-language matrixLockfiles where a lockfile exists, declared manifests where one does not, and the report says which it read.
Commit one .irisconfig.json for the CLI, pre-push hook, build hook, and CI. A failed gate names what crossed the limit and returns the exit code your pipeline expects.
Every seat includes Pro. The team workspace adds shared configuration, repository evidence, analytics, activity, roles, billing, and an audit log of what ran under each policy version.
One standard for the organisation, built in the workspace Config Studio and committed beside the code.
Repositories report their audits into the workspace, each keeping its own findings, dependencies, and trend.
Health score, files scored, and pushes blocked across the organisation, with the delta against the previous period.
A daily signal chart, the longest active streak, and the mix of what your team actually ran.
Every recorded event, filterable by signal, showing who ran what and under which version of the policy.
An exportable report with per-project tables, for the review that happens outside the tool.
Owner, admin, and member roles, invitations with expiry, and a seat limit the workspace enforces.
Seats billed to the organisation at your region's resolved rate, starting with a 14-day trial.
Team evidence records execution outcomes and aggregate counts. It never contains source, file paths, repository URLs, snippets, or finding text.
Start a Teams trialThe Playground runs the same analysis and gate engine on a seeded multi-file project. Inspect the evidence, fix the findings, and see how the configured gate responds.
Free covers file analysis and core agent guidance. Pro adds workspace checks, enforcement, dependency intelligence, advanced configuration, and cloud audits. Teams gives every member Pro and adds the shared workspace.
Forever. Measurement is not the paid part.
Install freeNo credit card, no sign-in
Included in Free
Enforcement: the half that can stop a push.
Start free trial14-day trial by request, no card
Everything in Free, plus:
One shared standard, and a record of who changed it.
Create a teamBilled monthly at your region's rate
Everything in Pro, for every member, plus:
Clear answers about privacy, supported languages, pricing, editors, and AI-generated code.
Editor, CLI, hook, and CI analysis run on your machine or your own runner; Iris Code does not upload that source for analysis or send it to a model. Cloud audits are a separate, explicit opt-in workflow: Iris Code temporarily fetches the connected repository, scans it, deletes the working copy, and retains the report. Limited network requests also support sign-in, licensing, dependency lookups, and optional product-use events.
TypeScript and JavaScript (.ts, .tsx, .js, .jsx, .mjs, and .cjs) get the full metric set, including TypeScript-specific type-safety signals where applicable, and the script blocks inside Vue and Svelte components go through the same checks. Go (.go), Python (.py), Ruby, C# (.cs and .csproj), Java (.java and .properties), and Rust (.rs) are scored for complexity, smells, and secrets. Ruby covers .rb and the Ruby DSL extensions, extensionless files such as Gemfile and Rakefile, and .erb templates. Secrets detection runs across these supported source-file types.
Free covers per-file analysis, secrets detection, Gate Preview, project rules for coding agents, and core CLI and MCP workflows. Pro adds workspace analysis, hooks and CI enforcement, advanced configuration, dependency intelligence, and metered cloud audits. Teams gives each member Pro and adds a shared workspace, seats, repository evidence, analytics, and audit history.
Files are scored incrementally on save in well under a second. The pre-push hook only scans changed files, so a typical push adds a beat - not a coffee break. The same engine powers the editor, CLI, and CI, so results never disagree.
Commit one .irisconfig.json so developers, coding agents, hooks, and CI work from the same limits. A Teams workspace adds seats, shared configuration, repository evidence, analytics, roles, and audit history across the organisation.
VS Code and every VS Code-compatible editor (Cursor, Windsurf, VSCodium) via the Marketplace extension, and JetBrains IDEs (IntelliJ IDEA, WebStorm, PyCharm, GoLand, PhpStorm, Rider, RubyMine, CLion, Android Studio) via the JetBrains Marketplace plugin. Both hosts run the same analysis engine, so a file scores identically in either one, and one sign-in covers your editors and the CLI. Everything else runs from the iris CLI in any terminal or pipeline.
No. Iris Code does not guess who or what wrote the code. It independently checks the result against deterministic rules for secrets, duplication, security smells, complexity, and maintainability, whether the code was written by a person, an AI assistant, or both.
File analysis is free and starts without configuration or sign-in. See the findings, inspect the rules behind them, and decide whether Iris Code belongs in your workflow.