Built from a specific frustration, in a specific place
CollabVyn started in Lyon in 2025, after Claire Moreau watched a six-week onboarding drag out because nobody had written down why the codebase looked the way it did.
Where it started
It was early 2025. Claire was leading engineering at a logistics technology company in Lyon when a new staff engineer joined the platform team. Over the following six weeks, the engineer spent most of her time scheduling 1:1s with anyone who might know why the service was built the way it was — why they had split the monolith when they did, why they picked that queue implementation, why the API contract looked strange in one corner. All of that context lived in Slack threads from 18 months prior and in the heads of two engineers who'd since moved on.
The code was there. The why had disappeared. And Claire had seen this loop enough times to know it wasn't a discipline problem — it was a tooling problem. Every existing solution required engineers to consciously write a decision record. Nobody does that consistently when a sprint is on fire.
CollabVyn is not a documentation tool
That distinction matters. We don't ask your team to write more. CollabVyn watches where decisions already happen — Slack threads, Notion pages, Loom recordings — and captures them without adding a step. The decision log fills itself. The next engineer who joins in six months finds the why they need without scheduling a single meeting.
CollabVyn is not a replacement for Slack, Notion, or any tool your team already uses. It's the decision-aware layer that sits on top of them — making their contents durable and searchable in a way those tools were never designed to do.
We're based at 18 Rue de la République, Lyon 69002, France. Bootstrapped. Three people. Building the tool we always wished existed.
The founding team
All engineers. All lived the problem.
Claire Moreau
CEO & Founder
Former engineering lead at a Lyon-based logistics technology company. Watched institutional knowledge walk out the door too many times before deciding to build the fix.
Thomas Lefebvre
CTO
Infrastructure engineer background. Previously built data pipeline tooling at a growing B2B SaaS. Responsible for CollabVyn's capture and search architecture.
Amira Benali
Head of Product
Product engineer who has sat on both sides of the onboarding table. Shapes CollabVyn's decisions about what goes into the product — and logs every one of them.
We eat our own dogfood
Write it down
Every decision at CollabVyn goes into CollabVyn. Our own ADR log is the first real stress test of the product. If something annoys us as users, it's the first thing we fix.
Async-first
We don't schedule a meeting when an async Loom or Slack thread will do. Decisions made async go into the log immediately. We have a standing rule: if you can't find the decision in CollabVyn, it didn't happen.
Show, don't label
No AI buzzwords. No claims about what the product "is capable of." We describe what it actually does, in plain terms an engineering manager would use to explain it to their team.
Decisions are first-class artifacts
Code, tests, and docs are treated as artifacts worth preserving. Decisions are the reason code looks the way it does. They deserve equal status — and a searchable home.
You own your data
Full export, any time. If CollabVyn shuts down tomorrow, your decision log leaves with you. We don't hold institutional knowledge hostage behind a subscription.
Privacy by design
Engineering decisions are sensitive. We're incorporated in France, GDPR-compliant, EU-hosted, and built with data minimization as a design constraint — not a checkbox.
We're building this for teams like yours.
Start with the free plan. Tell us what's missing. We read every email.