About

I make software. Software that runs in prod, handles load, and doesn't crash on a Friday evening (well, I try).

I've been at this for 15 years. I've built architectures in logistics, healthcare, cybersecurity - the kind of fields where downtime isn't just an annoying Jira ticket. It's a warehouse stuck idle, a patient record no one can open, or a SOC missing an alert. The kind of stuff that has you checking your Grafana dashboards on a Sunday morning.

I've done the rounds: consulting firms, software vendors, large enterprises. I also co-founded a startup (yes, with the sleepless nights and the pivots that come with it). At every stop, same story. Teams pile up technical debt without noticing, and one day it blows up. Sometimes it's a deploy that tanks prod, sometimes it's an entire system you have to rebuild from scratch.

So what's Fransys

In 2025, I got tired of doing things halfway. I started Fransys to work directly with engineering teams - no three layers of management between the problem and the solution. Software architecture consulting, technical transformation - the kind of work where I get my hands in the code when needed, not just slides. Rethinking a shaky architecture, hardening a system that scares everyone, navigating a cloud migration (without breaking everything in the process), unblocking a project that hasn't moved in 6 months.

This blog

I write here about what I run into day to day. Config nightmares, architecture decisions I've had to make (and sometimes regretted), tools I've actually tested. No polished marketing content, no "10 best practices to revolutionize your IT". Just honest takes for people who build stuff.