We built Fynrex because compliance teams deserve better than weekly PDF digests.
Founded 2024. Jersey City, NJ. Angel-backed.
Why Isabelle built this.
Before Fynrex, Isabelle led regulatory affairs at a mid-size bank where her team spent close to 40% of their working week manually tracking regulatory changes across 12 jurisdictions — reading agency feeds, flagging updates in spreadsheets, forwarding PDFs across the firm. She watched colleagues get pulled into emergency remediation projects after missing an FCA update that had been public for 60 days. The information existed. The process to surface it, assign it, and confirm it was addressed did not.
She founded Fynrex in 2024 to build that process. A system that reads regulatory sources the morning they publish, maps each change to the policies and controls it affects, and routes the action to the person responsible — with enough lead time before the effective date to actually respond.
The people behind Fynrex.
Former regulatory affairs director at a mid-size bank. Led horizon scanning across 12 jurisdictions before founding Fynrex to build the process she had been doing manually.
Former regulatory data infrastructure engineer at a fintech data provider, where he built ingestion pipelines for market data and enforcement feeds. Architect of the Fynrex multi-jurisdiction ingestion layer.
Former compliance analyst at an investment bank covering ESMA, EBA, and FCA frameworks. At Fynrex she owns jurisdiction accuracy — verifying source publications, maintaining regulator coverage, and reviewing change classification before it reaches customer feeds.
Compliance should be proactive, not reactive.
Financial regulations are public. The information exists. Our job is to make sure the right people in your firm see the right changes, mapped to the right obligations, on the day they are published — not the day someone stumbles across the update in a weekly digest.
Fynrex is not a legal interpretation service, a GRC platform, or a compliance consulting firm. It is the horizon-scanning and change-routing layer that sits upstream of all of those — the part of the process that has historically been done by hand, by compliance teams who have better things to do with their time.