Recommended
Team
$49per project / month
For teams that need hosted run history and shared release review.
- Hosted projects
- Run history
- Overlay review
- MCP dry-runs
- Slack + email alerts
Start team review No credit card to start.
Plans
Pricing that follows SDK release volume.
Start with the local audit loop. Move to hosted release gates when your team needs shared history, review workflows, and usage controls.
Build
$0Open source
For local audits, OSS packages, and early TypeScript SDK parity checks.
- CLI reports
- Synthetic fixtures
- TypeScript manifests
- JSON output
- Community support
Scale
CustomAnnual contract
For organizations standardizing SDK release control across APIs.
- Private runners
- SSO planned
- Audit exports
- Usage governance
- Solution review
Compare
Pick the plan that matches your release cadence.
| Feature | Build | Team | Scale |
|---|---|---|---|
| CLI audits | Included | Included | Included |
| Hosted projects | Not included | Unlimited | Unlimited |
| Run history | 7 days | 90 days | Custom |
| Overlay review | Not included | Included | Included |
| MCP dry-runs | Local only | Hosted | Private runners |
| Slack + email alerts | Not included | Included | Included |
| SSO + SCIM | Not included | Planned | Included |
| Audit export | Not included | Self-serve | Compliance-ready |
Usage model
Meter the work that actually costs money.
The first paid moment should be a release gate your team already trusts.
Pricing is designed around reviewable run volume, not seats alone, so teams can dogfood the CLI and upgrade when hosted coordination matters.
Pricing
Common questions before you upgrade.
Can I gate releases in CI?
Yes. Reports emit stable JSON that CI workflows, release scripts, and review bots can read. Failing semver rules block merge by design.
What does pricing follow?
Plans bill per project, not per seat. Usage credits cover audit, generation, and publish dry-run runs so reviewable work is the unit you pay for.