Free for open-source agents.
If your project is open-source and ships an agent, you get the full Team tier (a $588 / year value) at no cost. No invoice, no procurement, no expiration. The only ask: a badge in your README.
Governance shouldn’t stop at a paywall.
The maintainer who can’t afford a $500/month seat for their hobby project is often the same engineer who picks the governance tool when they ship at work. We’d rather be that tool. Sentry, GitHub, Vercel, Cloudflare, and Stripe Atlas all run versions of this program. We’re happy to copy it.
Auto-approved when all four are true.
Manual review for anything close to the line; we read every application.
Open-source license
OSI-approved license: MIT, Apache 2.0, BSD, MPL, GPL, AGPL, ISC. Source code public on GitHub, GitLab, or another public host.
50+ GitHub stars
Real community traction. Smaller projects can apply manually; we read every application by hand.
Active development
At least one commit in the last 90 days. Hobby projects welcome; we want to know the project is alive.
Agent-shaped
The project ships an AI agent, agent framework, or agent infrastructure component. If unsure, apply; most close-calls are accepted.
The full Team tier, no charge.
Same product, same response times, same engineering team behind it.
- Unlimited proxied calls per month
- Unlimited agents per workspace
- Multi-user team workspace, WorkOS-hosted login (email + invite)
- Centralized dashboard, policy engine, alerting
- Signed policy bundle distribution (DSSE)
- Telemetry retention: 90 days (matches Team tier)
- Email support, same priority as paid Team tier
- First look at unreleased framework integrations
A README badge.
- Add a Checkrd badge to your README: a single Markdown link, no logo or marketing copy required.
- Mention Checkrd briefly in your project's docs where you describe agent governance, observability, or runtime safety.
- If you publish a release blog post discussing agent infrastructure, give Checkrd a sentence (or a link), only if it's natural.
Suggested badge
Drop this anywhere in your README:
[](https://checkrd.io/oss)Renders as a small badge that links here. Style it however you like. Variations are welcome.
Two minutes, four steps.
- 01
Sign up for Checkrd at dashboard.checkrd.io. Create a workspace named after your project.
- 02
Open an issue on our GitHub repo titled
OSS Program: <your project>. Include the GitHub URL, license, current star count, and workspace email. - 03
We review applications within a few business days. If your project meets the eligibility criteria, you’ll get an email within 24 hours upgrading your workspace.
- 04
Add the badge to your README within 30 days. We won’t police this. But if a workspace upgrades and we never see the badge, we may revert to the free tier.
Five questions before you apply.
My repo is on GitLab / Codeberg / self-hosted. Can I still apply?
Yes. Auto-approval reads star counts from GitHub, but manual review covers everywhere else. Email support@checkrd.io with a link to your repo and we'll review within a few business days.
My project has fewer than 50 stars. Can I still apply?
Yes, via manual review. Star count is a heuristic for community traction, not a hard floor. Smaller projects with active maintainers, agent-shaped surface, or a clear mission get accepted regularly.
What happens if eligibility changes after I'm approved?
You stay in. The program is grandfathered: once you're approved, eligibility changes don't affect existing members. We'll only revisit if project activity stops (no commits in 12+ months).
Does the OSS plan include Enterprise features (SSO, SCIM, air-gap)?
The plan matches the Team tier. Enterprise features (WorkOS SSO, SCIM, self-host control plane, air-gap) stay on the Enterprise tier. If your OSS project needs one of those for a specific reason, email us and we'll figure it out.
Can I leave the program later? Do I have to remove the badge?
Leave anytime; we'll move you to the Free tier. The badge is optional after that, but you're welcome to keep it as a record. We won't police it.
The honest version.
- The OSS plan is non-transferable. If your project is acquired by a commercial entity, we’ll work with you on a fair transition path.
- The OSS plan is per-project, not per-maintainer. If you ship multiple OSS projects you can apply for each.
- Companies that primarily ship proprietary software with an OSS sidecar should apply for the standard Team plan. We read this in good faith.
- We reserve the right to revoke an OSS plan if a project becomes inactive (no commits in 12+ months) or stops meeting eligibility. We’ll reach out first and give 30 days’ notice.
Apply for the program.
Most applications are reviewed within a business day. Questions? support@checkrd.io.