FIDIS
Internal control and regulatory compliance for UEMOA banks and microfinance institutions.
- My role
- Full-stack, end to end: product design, data model, back-end, front-end, deployment and security.
- The problem
- Our pilot bank ran its controls on Excel sheets and e-mail threads. When the supervisor asked for evidence, someone rebuilt it by hand.
- What it does
- FIDIS carries a control from its mission to the signed report. Control points are tested on a sample, non-compliant items raise anomalies, anomalies lead to action plans, the rulebook is imported from the regulator's texts, and reports are drafted on the bank's own templates, by hand or with AI.
- How it is built
- Python with Django REST Framework on the back-end; TypeScript with Next.js and React on the front-end. PostgreSQL keeps one schema per bank, so a query cannot reach another client's data. Celery workers and Redis run the recurring controls, escalations and notifications. The whole platform ships with Docker Compose behind nginx and gunicorn on a Linux VPS. Report drafting and the regulatory assistant call Claude through Anthropic's API. Delivered in numbered lots. Each lot lists its goals and my business decisions, ships with its tests, gets deployed, then committed.
- Languages and tools
- PythonDjango RESTTypeScriptNext.jsReactPostgreSQLCeleryRedisDocker ComposenginxClaude API
Real FIDIS screens from the test environment, recorded on 27 Oct 2026. Data is fictitious. Click a screen to enlarge it.

