01 · AXA Group Operations · 2026Claude Code for 120+ engineers, with cost control
RoleTechnical lead, AWS platformStatusIn production, 9 teams
Context
AXA's engineers wanted Claude Code. Security required company sign-in and data kept in the EU. Finance required that every euro be traceable to a person and a team, with a hard limit.
What I did
Built the AWS platform that satisfied all three. Engineers sign in with their company account and reach Claude on Amazon Bedrock in an EU region. Every request is priced and recorded for the person and the team. Each team has a budget: alerts as it gets close, access blocked at the limit, reset each month. A new team is one entry in a configuration file. I then ran the pilot and wrote the go/no-go report.
Result
120+ engineers in 9 teams use Claude Code with company identity and EU data residency. Finance charges costs back to the right cost centre because the platform's figures match the AWS bill within 0.3%.
Figures 340,000+ requests tracked (Sep 2026) · 0.3% gap to the AWS bill
Stack Amazon Bedrock, Lambda, Kinesis, DynamoDB, CloudFormation, IAM and SAML
02 · AXA Group Operations · 2026A-Pad: evidence-based assessments of IT projects
RoleMy initiative; designed and built aloneUsersAXA project managers
Context
Before a project moves to its next stage it passes a review. The outcome depended on the reviewer, because the evidence was spread across dozens of documents nobody had time to read in full.
What I did
Proposed and built a platform where AI agents do the reading. For each criterion an agent searches the project's documents, answers, checks its own answer and retries if needed; every answer cites its source. A review passes only if each mandatory criterion is met and the score reaches 80%; a project manager can override, with the reason recorded. Templates let the same engine serve IT changes, climate reporting, application risk and vendor checks. Built for production: recovery after failure, audit log, cost control, Word and PDF export.
Result
Project managers get an assessment where every verdict points to the document it came from, and spend their time validating instead of searching. One tool covers six kinds of review.
Figures 6 review types · 10 templates · 200+ automated tests
Stack Python, FastAPI, LangGraph, PostgreSQL and pgvector, Redis, React, OpenShift
03 · LCL · Dec 2023 – nowThe bank's self-service GenAI platform
RoleArchitect and technical leadUsers90 teams, 500+ people
Context
Every team wanted an assistant that knew its own documentation, tickets and data. Each request was becoming a separate project with its own security review and costs.
What I did
Architected and industrialised the central platform. Teams create assistants in a web interface, without code, and connect them to Confluence, Jira or internal databases. A gateway applies access rights, usage limits and cost tracking to every request; every conversation is traced. I load-tested before each scale-up and delivered the first use cases with the teams.
Result
90 teams built their own assistants instead of waiting for a project each. The bank got one place to control access, cost and quality.
Figures 90 teams · 500+ users · 6 families of use cases
Stack Python, LangChain, LangGraph, Amazon Bedrock, Open WebUI, LiteLLM, Langfuse, Elasticsearch, Kubernetes
04 · LCL · Dec 2023 – nowHIBOU: one view of the bank's vulnerabilities
RoleMy initiative; designed, built and ledStatusThe bank's security standard
Context
Several scanners each reported their own findings. Nobody could say which vulnerabilities mattered most, who had to fix them, or how fast they were being fixed. The regulator was asking for proof.
What I did
Proposed HIBOU and built it: connectors and pipelines merge every scanner's findings into one model; each finding gets a risk score (severity × application criticality); teams see their ranked list, security managers see the whole bank, and a remediation-speed leaderboard made fixing something teams compete on. The history of fixes is kept as evidence.
Result
Adopted as the bank's enterprise security standard and the reference tool for security managers and compliance. Gives the bank evidence of remediation for the regulator under DORA.
Figures 700+ applications · 100+ teams
Stack data pipelines, risk scoring, dashboards by team and application
05 · AXA Group Operations · 2026A secure catalogue of AI agent extensions
RoleArchitecture and buildUsersAXA entities and developers
Context
A scan of the group's GitHub found thousands of extensions for AI coding assistants (skills, agents, plugins, MCP connectors) copied from project to project. Sharing them saves time; one bad extension can leak a secret or send data out.
What I did
Built a catalogue with a security gate: each entity publishes its own catalogue, collected nightly; every extension is scanned for secrets, unsafe code, hidden instructions and data leaks; anything executable or flagged goes to a person, and any change triggers a new review. Developers install from Claude Code or GitHub Copilot, or browse the portal.
Result
One trusted source of agent extensions for the group, and its first inventory of what was already in use.
Figures 40,000+ repositories scanned · 5,800+ AI assets found with owners · 230+ automated tests
Stack Python, GitHub Actions, Gitleaks, Bandit, ShellCheck, React
06 · KASTOR.AI · Jun 2025 – nowKASTOR.AI: a product of my own
RoleFounder and technical lead; built aloneCoversGDPR, EU AI Act, NIS2, ISO 27001
Context
Compliance reports take weeks, mostly spent finding evidence in a company's own policies and procedures. The judgement must stay with a person.
What I did
Built the whole product: hybrid search (vectors and keywords, HyDE, re-ranking) across the client's documents; AI drafting with Gemini and Claude coordinated by LangGraph; report templates per regulation with AI or human control per section; an Angular editor shipped as a PWA; accounts and roles on Google Cloud, provisioned with Terraform.
Result
A working product that proves I can carry the full chain: retrieval, agents, interface, cloud, and the decisions about what the AI should not do.
Stack Python, FastAPI, LangGraph, Vertex AI, Amazon Bedrock, Angular, MongoDB, Redis, Google Cloud, Terraform