Cloud architecture
Multi-cloud and disaster recovery designs: AWS as the primary site with Azure for recovery, active/passive across zones, Kubernetes at scale, a 99.999% availability target.
Freelance cloud architect · available January 2027
An architect on your team, with cost as a design constraint.
I join teams for architecture, migration and performance work on AWS, Azure and Google Cloud. Every design choice comes with its monthly cost.
Available fromJanuary 2027
CapacityUp to 20 days / month
WhereParis · remote
Daily rateOn request
The same terms as the FinOps engineer, by the day: FinOps · régie.
What I do
Four kinds of work, one constraint: the monthly cost.
Migrations and performance
Rewriting the parts that cost the most, with the legacy system as the reference for every test until the numbers match.
Infrastructure as code and security
Terraform, Terragrunt, Bicep and Ansible, with plan reviews, automated tests, policy as code and drift detection. Identity with Entra ID, OAuth/OIDC and SAML.
Cost from day one
FinOps at the design stage rather than after the bill arrives: each option is priced before it is built.
Case · EDF Power Solutions
A simulation engine rewritten from C# to Rust.
99%
faster: from about 7 h 30 to under 30 seconds per run
−50%
cloud costs, approximately
÷40
peak memory at the results stage
Data extracted once to object storage as frozen columnar files. Short single-purpose steps that talk through storage, not to each other. Independent slices run in parallel on short-lived serverless functions on ARM, sized step by step.
Case · Energy, real time
A real-time IoT platform built to scale and update without downtime.
1M+
real-time IoT sensors
< 3 min
for the platform to recover on Azure if AWS goes down across zones and regions, a recovery owned by a separate team
NIS2
conformant security framework, now the reference for adjacent systems
An elastic ingestion and processing pipeline on AWS, designed to keep data intact and available at large scale, with the whole infrastructure replicated 1:1 on Azure, where a separate team owned disaster recovery. FinOps and DevOps were part of the design from the start, with infrastructure as code in Terraform, containers on Docker and Kubernetes, and CI/CD. Elasticity and zero interruption were bought with a much larger operational and security surface, which made NIS2 conformance load-bearing.
Case · EDF Power Solutions
A file ingestion chain built for very high throughput and delivered to production.
50 TB
of data a day: the volume the chain was sized for
In the same engagement, a high-performance computing platform on AWS, designed and implemented as code: managed SLURM, FSx for Lustre, MPI and tightly coupled parallel jobs on an auto-scaled EC2 cluster.
Governance · ISALYS Group
Architecture standards built into the delivery contract.
3
countries under one architecture method
5
client contexts under one development governance charter
Technical director of the engineering entity of a group of about 350 people. Standards, reference integration patterns and a development governance charter with three stated criteria: explicitness, simplicity, maintainability. ADRs made a habit rather than a mandate: teams got the format, the charts and protected time to write them. C4 introduced as the shared vocabulary across domains.
Decision · ISALYS Group
A two-tier LLM runtime instead of one vendor.
Managed frontier models for reasoning-heavy features, self-hosted lightweight Mistral models where data residency or per-token cost dominates. The trade-off: two runtimes and two security baselines, against lock-in and a token bill nobody could attribute. Cost per feature became a design input, and the reach of each data-processing agreement is decided at the boundary, per capability.
1 / 5
From the CV
Experience
- Jun 2026 – Dec 2026
Solutions architect and DevOps engineer, AI and LLMOps
Pierre & Vacances Center Parcs · via ISALYSA self-service AI platform for developers and non-developers: more than 50 apps shipped to production, about 15 citizen developers onboarded. I run the technical architecture boards.
- Jun 2026 – today
DataOps engineer, data architect
Nature & Découvertes · via ISALYSA support contract of about two days a month: took over an on-premise Hadoop data lab (6 nodes, about 40 daily data flows) and rebuilt the marketing ingestion.
- Oct 2025 – today
Head of digital engineering, technical director
ISALYS Digital Lab · ParisTechnical director of the engineering entity of a consultancy of about 350 people. More than 15 pre-sales, about ten of them won.
- Dec 2024 – Oct 2025
Head of digital R&D, simulation tech lead
ISALYS Consulting Belgium · BrusselsAn R&D team of 15 people; 5 prototypes taken to production.
- Aug 2024 – Jun 2026
Rust system engineer, data and fullstack engineering
EDF Power Solutions · via ISALYSSuccessive engagements, ending with the rewrite of a simulation engine from C# to Rust: one run went from about 7 h 30 to under 30 seconds, and cloud costs fell by about half.
- Jan 2024 – Jun 2024
System quality analyst, rail
Televic GSP · Izegem, Belgium · via ISALYSHardware-level test benches and automated test plans in Python to validate rail safety systems such as tilting and emergency braking.
- Nov 2021 – Dec 2023
Independent software engineer and architect
MKDevs · freelanceMore than 50 short expert engagements: space and embedded systems, high-performance computing for finance, blockchain.
Architecture and cloud
- AWS and Azure platforms, multi-cloud
- Real-time IoT, high availability
- HPC: SLURM, ParallelCluster, FSx
- HLD, LLD, ADRs, architecture boards
- IAM, mTLS, NIS2 compliance
Performance and cost
- Rust rewrites of critical workloads
- Parallelism, bounded memory
- Serverless and ARM (Graviton)
- FinOps: audits, costed savings
- Regression tests, benchmarks
Platform, data and AI
- Platform engineering (Backstage, GitLab CI)
- LLMOps: gateway, costs, guardrails
- Claude Code tooling, golden paths
- DataOps: Airflow, Dataiku, Hadoop
- Taking over legacy platforms
Education
BSc in Computer Science (Licence), Université de Bretagne Occidentale, 2021 – 2023. Self-taught before that: first paid code in 2019, in C++.
Membership
Member of the FinOps Foundation.
Languages
French, native. English, C1: daily work in English-speaking teams. Spanish, B1.
Stack
RustC / C++PythonAWSAzureGoogle CloudKubernetesPostgreSQLTerraformTerragruntBicepAnsibleEntra IDHPC
Next step
Tell me about the mission.
Pick a slot and tell me the context, dates and team. Prefer writing? contact@mathieukerbel.com