Pricing
Clear pricing. No per-seat surprises.
Free for open-source projects. Affordable for growing teams. Custom for enterprise OSPOs.
Open Source
Forever free
Public repos, personal projects
Up to 5 active repos · Unlimited contributors
- GitHub integration
- Standard CLA template
- Email notifications
- 30-day audit history
Team
per month
Growing engineering teams
Up to 20 repos · Unlimited contributors
- All integrations (GitHub, GitLab, Bitbucket)
- Custom CLA templates
- Slack notifications
- Full audit history + PDF export
- Priority email support
Enterprise
Contact for pricing
Enterprise OSPOs and in-house engineering counsel
Unlimited repos · SSO · SLA
- All Team features
- SAML/SSO
- Custom SLA
- Dedicated support
- API rate limit increase
- IP allowlist
- Audit log retention 7 years
Common questions
An active repo is any repository where Cohorto has processed at least one CLA-related event in the billing month. Archived repos and repos with no PR activity don't count toward your limit.
Yes. You get 14 days of the Team plan with no payment information required. At the end of the trial, you can upgrade or downgrade to the free Open Source plan — no automatic charges.
Yes. Cohorto works with private repositories on all plans. The Open Source plan is intended for publicly visible repos, but you can configure CLA workflows for private inner-source programs on Team and Enterprise plans.
No. Contributors sign through a lightweight hosted portal using their existing GitHub, GitLab, or Bitbucket identity. No account creation required on their side.
Enterprise is priced based on the number of repos and the specific features your OSPO needs (SSO, custom SLA, extended audit retention). Contact us and we'll scope a contract that fits your program — most enterprise agreements start at a fixed annual fee, not per-seat.
Yes. We have migration guides for CLA Assistant (SAP), CLAhub, and manual spreadsheet setups. For Enterprise migrations, we provide white-glove onboarding to import historical signature records.
Cohorto focuses on CLA workflows. We don't enforce DCO (Developer Certificate of Origin) sign-offs — DCO is handled at the Git commit level via signed-off-by trailers, which most platforms check natively. If your repos mix DCO and CLA requirements, Cohorto handles the CLA repos; your existing Git tooling handles DCO. See our DCO vs CLA guide if you're still deciding which model fits your program.