Tidal Control incident

Managing risk in a fast-growing fintech: how Floryn made compliance scalable

Resolved on June 25, 2025.

resolved Jun 25, 2025, 12:00 AM UTC

Floryn, a fintech lender under De Nederlandsche Bank supervision, moved its compliance and risk processes from fragmented spreadsheets to Tidal Control after finding that recording risks and policies was not enough without systematically executing and demonstrating controls. Starting from around 120 risks built with KPMG, Floryn spread its workload across the year, linked controls directly to legislation such as the EBA guidelines, and embedded risk ownership across the whole organisation. Compliance awareness and consistent execution of internal processes have increased significantly as a result.

Started
Jun 25, 2025, 12:00 AM UTC
Resolved
Jun 25, 2025, 12:00 AM UTC
Duration
–
Detected by Pingoru
Jun 25, 2025, 12:00 AM UTC

Update timeline

  1. resolved Jun 25, 2025, 12:00 AM UTC

    Floryn, a fintech lender under De Nederlandsche Bank supervision, moved its compliance and risk processes from fragmented spreadsheets to Tidal Control after finding that recording risks and policies was not enough without systematically executing and demonstrating controls. Starting from around 120 risks built with KPMG, Floryn spread its workload across the year, linked controls directly to legislation such as the EBA guidelines, and embedded risk ownership across the whole organisation. Compliance awareness and consistent execution of internal processes have increased significantly as a result.

Your product runs on more than Tidal Control

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →