About us
Kalipso exists because a buried filing in a 200-page FCA update cost one compliance team weeks of remediation work that should have taken two days. We built the tool we needed.
Origin story
Before founding Kalipso, Pierre Ferran spent several years running compliance monitoring at a UK-regulated financial firm. His team had a rigorous process: subscribe to FCA and PRA email digests, triage them each morning, flag anything relevant, pass it to legal for review. The process worked, until an update came through in a PRA policy statement that buried a material change on page 197 of a 214-page document.
The change affected the firm's capital buffer calculation. Nobody caught it on the first read. Three weeks later, a counterparty's compliance team flagged it in a deal call. The remediation work took six weeks.
In March 2025, Pierre founded Kalipso Ltd. He brought in Amara Osei-Mensah, an NLP engineer with a background in large-scale document processing, and Lena Brauer, a regulatory analyst who had spent years reading FCA and EBA primary documents professionally. Together they built Kalipso: a system that reads the full text of every regulatory document, identifies what changed and what it means for a given firm's obligations, and drafts the remediation steps so the compliance team can review and act rather than read and interpret.
Kalipso launched in April 2026. The founding team remains lean and owns the platform entirely.
The team
Kalipso is built by people who spent years inside the problem they are now solving.
Pierre Ferran
CEO and Co-Founder
Built and ran compliance monitoring programmes at UK-regulated financial firms before founding Kalipso. Experienced firsthand the cost of regulatory change management done by hand. Now focuses on product direction and client relationships.
Amara Osei-Mensah
CTO
Builds and leads Kalipso's technical infrastructure. Background in large-scale document ingestion pipelines and NLP for structured information extraction from dense regulatory text. Responsible for the reliability and speed of Kalipso's regulatory feed parsing.
Lena Brauer
Head of Regulatory Affairs
Spent years reading FCA, EBA, and ESMA primary documents as a regulatory analyst, developing practical expertise in what a compliance team actually needs from a remediation memo. Trained Kalipso's drafting model on plain action verbs, obligation traceability, and urgency framing. Oversees ongoing model calibration and feed quality.
How we work
Read the full document
Material changes hide on page 197. Kalipso reads the full regulatory source, not the headline summary. Every word of every update from every covered feed, every time.
Draft, do not decide
Kalipso produces the first draft of a remediation memo. The compliance officer reviews, revises, and signs off. The AI does the reading and the first draft. The human retains accountability and judgment.
Data stays in the UK
All customer data is stored and processed in UK data centres. No exceptions. Financial firms have regulatory obligations about where their data lives. We designed Kalipso to respect them from day one.
Traceable reasoning
Every remediation action item Kalipso drafts links back to the specific section of the regulatory source that triggered it. You can trace the reasoning from action to rule. Audit-ready by design.
Work with us
We start with a 30-minute session where we walk through a real regulatory update from your jurisdiction and show you the alert and memo Kalipso would have produced.