Pricing

AIIR proves one workflow locally. Hub turns that proof into team governance. Seed preserves the same proof model in offline, regulated, or operator-controlled environments.

Hub

Contact us

Hub operationalizes receipts across your organization and gives teams one review lane, one policy surface, and one reporting story across repos and environments.

  • Everything in AIIR
  • Cross-repo receipt aggregation
  • Policy enforcement and audit
  • Review and approval workflows
  • Role-based access
  • Reporting and compliance export
  • Dedicated support
Talk to us →

Seed

Contact us

Controlled deployment for offline, air-gapped, regulated, or operator-managed environments that need the same proof model without a hosted dependency.

  • Everything in Hub
  • Deployment planning for operator-controlled environments
  • Offline-capable verification and policy workflows
  • Support for constrained or regulated environments
  • Native verifier path for tighter footprint and control boundaries
  • No hosted dependency required
  • Bootstrap and rollout guidance
  • Dedicated engineering engagement
Talk to us →

How to think about this

AIIR is the adoption surface: free, local, no account required. Hub is what you reach for when local proof turns into a team workflow problem: multiple repos, multiple reviewers, shared policy, and audit export. Seed is what you reach for when the deployment boundary itself is the blocker: offline, air-gapped, regulated, or operator-controlled environments. These are operationally different offerings, 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 aggregates receipts across your organization and adds policy enforcement, review workflows, shared visibility, and compliance reporting. It is for teams that have outgrown local-only proof and need one governance surface across multiple projects.

What makes Seed different from Hub?

Hub is the centrally managed governance layer. Seed is the same proof model under harder deployment constraints: offline, air-gapped, regulated, or tightly controlled environments where rollout shape, control boundaries, and verification footprint matter as much as policy workflow.

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 control plane is not acceptable, for example in offline, air-gapped, regulated, export-controlled, or partner-managed environments, but you still need the same proof model.

Why is there no numeric pricing for Hub and Seed?

Hub and Seed deployments vary significantly by scope: number of environments, policy domains, deployment topology, and support requirements. 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 operator surface 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?

Yes. Seed is intended for environments where network access is limited or unavailable. The exact deployment shape depends on the operating constraints and control boundary in scope. 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 →