Our Story
We built the CLA tool we always needed
In 2022, Luca Bertrand was running platform tooling at an enterprise software company in Kansas City when his OSPO counterpart dropped a spreadsheet into Slack: 47 open-source contributors, 12 repos, every CLA tracked by hand. He started Cohorto two months later.
Why we exist
The pattern was always the same: engineering wanted to accept an external PR, legal needed a signed CLA first, and nobody had a clean record of who had signed what version. The OSPO — when one existed — was the triage point, working through email threads and attached PDFs to reconstruct a signature history before any M&A due diligence or IP audit.
The existing tooling had a clear gap. SAP's CLA Assistant was (and remains) free and self-hosted — it handled basic signature collection but had no compliance dashboard, no audit export, and required DevOps time to run. On the other end, full FOSS compliance platforms like Fossa bundled CLA into a much larger license-scanning product with enterprise-only pricing. Teams that just needed the CLA piece had nowhere to go.
Cohorto is not a license scanner. It does one thing: automate contributor license agreement collection and maintain the audit-ready record of every signature. It integrates natively with the version control platforms your team already uses, at a price that fits before the enterprise compliance budget materializes.
Headquarters
2345 Grand Boulevard, Suite 800, Kansas City, MO 64108
The Cohorto team
Luca Bertrand
Founder & CEO
Spent a decade in platform and developer-tools engineering at enterprise software companies in the midwest. Spent enough time rebuilding ad-hoc CLA workflows to know the problem was structural, not organizational. Founded Cohorto in Kansas City in 2022 to fix it once, properly.
Dana Osei
Head of Engineering
Full-stack engineer who spent five years building CI/CD pipeline integrations and webhook infrastructure at a mid-size DevOps tooling company. Joined Cohorto in 2023 to own the platform integrations layer — GitHub App, GitLab CI hooks, Bitbucket Pipelines, and the REST API.
Mira Chaudhary
Head of Customer Success
Seven years in enterprise SaaS customer success, including two years focused on compliance-tooling onboarding. Knows what OSPO leads and engineering counsel need during their first 90 days on a CLA program — and what gets in the way.
How we build
01
Correctness over convenience
CLA records are legal artifacts. We prioritize accuracy and auditability over shortcuts. Every signature event is immutable from the moment it's recorded.
02
Engineering teams first
Compliance tooling that engineers fight is compliance tooling that gets disabled. We obsess over PR integration UX because friction in the developer flow is a failure mode.
03
Bootstrapped, focused scope
We haven't raised external funding. That means we build for our customers, not for a growth story. We'd rather do CLA automation exceptionally well than bolt on five adjacent features.