IRONHIDEPlans & pricing
Ironhide is priced on usage: how many agents you protect and how many runs you execute each month. Every tier gets the same grader and the same verdicts — nobody gets a weaker grader for paying less. Bigger tiers get more protected agents, more monthly runs, and heavier tooling around the verdict.
Data rights are not a pricing axis and not a feature you toggle. Every
run, on every tier, is owned — there is no privacy tier to buy and no
per-agent opt-out. What Ironhide keeps and reuses is the scrubbed
environment your agent ran against, never your agent's own trajectory;
the mechanics are on the data rights page.
The four tiers#
| Tier | Price | Protected agents | Runs / month | What it adds |
|---|---|---|---|---|
| Developer | Free | 1 | 100 | GitHub Action, ironhide CLI, the standard attack battery, local repro of every finding |
| Team | $199/mo | 10 | 2,500 | Full attack library, statistical CI gating, team workspace, API access |
| Business | $999/mo | 50 | 15,000 | Custom mock environments, Customer-Isolated Spec Vaults, Compliance Audit PDF export, SSO/RBAC |
| Enterprise | Custom (contact us) | Unlimited | Unlimited | Private VPC runners, custom environment twins, SIEM/Jira/ServiceNow integrations, dedicated SLA |
Tiers are cumulative: each includes everything below it. Enterprise has no self-serve checkout — email hello@ironhideai.com.
The free Developer tier#
Every new account starts on Developer: 1 protected agent and 100 runs a month, free, no card. That is enough to wire the gate into a PR and see real verdicts before paying anything. Two things to know:
- Every run is owned-data. This is true on every tier, free and paid alike: the shared library is built from the scrubbed environments your agent runs against, not from your trajectories, and there is no opt-out to manage (data rights).
- Quotas are enforced by the server, not the honor system. The run meter counts against your tier's monthly quota, and the agent cap counts registered agents. When a quota is reached, new runs return a clear refusal that names the quota and the tier; your agents stay registered and every past report stays readable. The built-in demo agent is exempt from the meter.
The catalog API#
GET /plans returns the live catalog — the same four tiers this page
describes, cheapest first: developer, team, business, enterprise.
Each entry carries the tier's id, name, price_monthly (dollars;
0 for Developer, null for Enterprise's contact-only pricing),
agent_quota and run_quota (null = unlimited), and the tier's feature
entitlements. The web UI and this page show the same catalog; if they ever
disagree, GET /plans is the truth.
Choosing and changing plans#
GET /planslists the catalog.- Selecting a paid plan routes through checkout
(
POST /account/checkoutwith{"plan_id": "..."}). Selecting a plan grants nothing until the subscription is active — until checkout completes you are metered on the free Developer quotas, so a half-finished upgrade can never grant paid entitlements. - Upgrades go through checkout at the higher price; the price difference is stated up front.
- Downgrades apply against the lower tier's agent and run quotas; if you are over the target tier's caps, reduce your agent count first.
Why the numbers look like this#
- Free is a real tier, not a trial. 100 runs a month is enough to gate a small project's PRs indefinitely. The front door is a developer seeing a real verdict in CI, not a countdown.
- $199 stays inside a team's tool budget. An engineering lead can approve it from an existing budget without opening a procurement cycle.
- $999 is where isolation tooling lives. Custom mock environments, per-tenant Spec Vaults, and the compliance export are operationally heavier, and the 50-agent / 15,000-run quota matches an org running the gate across many services.
- Data rights are never the upsell. Every run is owned on every tier. What you pay for as you go up is capacity and tooling, never a change to how your data is handled.