Pricing

AIIR is the public local-first path. Contact us if you need shared team workflows or restricted-environment planning beyond that baseline.

Hub

Contact us

Contact-led planning for shared team workflows around review, policy, and reporting.

  • Everything in AIIR
  • Shared receipt visibility
  • Policy and review workflows
  • Reporting exports
  • Guided rollout
  • Dedicated support
Talk to us →

Seed

Contact us

Contact-led planning for restricted, offline, or tightly controlled environments that need the same proof model without a hosted dependency.

  • Everything in Hub
  • Restricted-environment planning
  • Offline-capable verification and policy workflows
  • Support for constrained environments
  • No hosted dependency required
  • Guided rollout
Talk to us →

How to think about this

AIIR is the adoption surface: free, local, no account required. Hub is the conversation for shared team workflows. Seed is the conversation for tighter environment constraints. These are different deployment conversations, not feature-gated tiers of the same thing.

Receipts are just JSON. No lock-in at the data layer, no proprietary formats, no phone-home requirement. Hub and Seed pricing reflects deployment scope, not per-seat access.

Frequently asked questions

Is AIIR really free?

Yes. AIIR is open-source under the Apache 2.0 license. You can use it in production, commercially, forever. No usage limits, no feature gates, no phone-home telemetry.

Do I need Hub or Seed to use AIIR?

No. AIIR is fully self-contained. Receipts are just JSON files; store them however you want. The CLI, VS Code extension, CI integrations, and browser verifier cover the complete local workflow without any hosted dependency.

What makes Hub different from AIIR?

AIIR generates and verifies receipts for individual repos. Hub is the conversation for teams that need shared policy, review, and reporting workflows beyond the local-only path.

What makes Seed different from Hub?

Hub focuses on shared team workflows. Seed focuses on the same proof model under tighter environment constraints, such as offline or otherwise restricted deployments.

What devices can Seed run on?

We scope Seed around environments you already control. Exact target platforms depend on the deployment constraints, security posture, verifier footprint, and support boundary, so we confirm the supported shape during planning rather than publishing a one-size-fits-all matrix.

When should I talk to you about Hub?

Talk to us about Hub when the problem stops being "can one repo prove what happened?" and becomes "how do multiple teams share policy, review queues, reporting, and audit evidence across many repos or environments?"

When should I talk to you about Seed?

Talk to us about Seed when a hosted dependency is not acceptable or the environment has tighter operational constraints, but you still need the same proof model.

Why is there no numeric pricing for Hub and Seed?

Hub and Seed engagements vary significantly by scope, support needs, and environment constraints. We price based on deployment scope, not per-seat access. Contact us and we will scope it together.

Does the VS Code extension replace the CLI?

No. The extension is a local-first interface on top of the same AIIR CLI. It helps you initialize, receipt, verify, inspect, and automate inside one repository and one workspace.

Can Seed run in air-gapped environments?

Seed planning can include air-gapped environments when those constraints are in scope. The exact deployment shape depends on the operating constraints under review. Receipt generation, verification, and policy enforcement remain local-first.

What does "verification scoring" actually measure?

Any workflow-level scoring is about declared-policy adherence, not code quality and not mind-reading. AIIR detection is heuristic-based (see the threat model), so any derived score is an operational signal for review, not a claim that undeclared AI use can be proven from source alone.

Start receipting today

One command. Free today. Full audit trail.

pip install aiir && cd your-repo && aiir --pretty

Need help or want to engage?

Bug reports

File reproducible product bugs in the public tracker so fixes, regressions, and workarounds stay visible.

Open a GitHub issue →

Questions and ideas

Use discussions for implementation questions, rollout feedback, and community conversation around AIIR.

Join the discussion →

Security reports

Do not post vulnerabilities publicly. Use the coordinated disclosure path with our published policy and response target.

View security reporting options →