The services
I design, build and automate the software behind your product.
From analysis and architecture choices to the actual build, all the way to the automated processes that keep quality high. Whether it starts from scratch or from a system that has grown rigid over time, the team is left able to go on without me.
How I work
The goal is to make myself unnecessary
Every engagement ends with a handover doc, runbooks and an internal owner I train. The system should not depend on me to keep working.
One active goal at a time
No parallel tracks stealing attention from each other. What is open gets closed, then the next one opens.
Decisions stay written down
The choices made, the alternatives rejected and why. The same format the public case studies are told in.
What we can do together
In the order things have to be faced: design first, then verify, then automate. Automation amplifies everything sitting above it, mistakes included.
01
System Design & Architecture
Designing scalable software architectures. From the requirement to the diagram, from the diagram to the code.
- › Microservices and event-driven systems
- › CQRS and domain modelling
- › API design
- › .NET, Go, Kafka, PostgreSQL
02
Observability & Security
Knowing the system actually works: under load, under attack, over time.
- › Observability stack with OpenTelemetry and Grafana
- › Loki, Tempo, Mimir
- › Identity management with Keycloak
- › OAuth 2.0 and OpenID Connect
03
Pipeline & Automation
Cutting time-to-production and raising reliability, without amplifying mistakes.
- › CI/CD and GitOps
- › Infrastructure as Code
- › Jenkins, GitHub Actions, ArgoCD
- › Terraform, OpenTofu, Ansible, Kubernetes
04
Training for the team
When the problem is not building but knowing how: a path run with the team, on your stack.
- › AI agents in Python
- › Observability
- › End-to-end testing with Playwright
- › Modules chosen during the discovery call
Technical assessment in 5 days
A week inside your system, to see where it gets stuck and where it pays to start.
I look at architecture, release pipeline, tests and monitoring, talk with the people who work on it every day and read the code where it matters. At the end you get:
- › a report with the problems ranked by impact and cost of intervention
- › a 90-day action plan, with the first three moves
- › a walkthrough session with the team
The report is yours: you can carry it out with me, with your internal team or with whoever you prefer.
How it goes
01
Discovery call
30 minutes, free. Tell me what the system looks like today and which decision you are stuck on. It is there to see whether there is a problem I can be useful on.
02 · optional
Assessment
Five days at a fixed price, for those who want a clear picture before committing. It ends with a report and a 90-day action plan.
03
Ongoing engagement
If the problem calls for continuity. Month to month, one active goal at a time, with everything the system needs included.
04
Exit
Handover doc, runbooks and a trained internal owner. From there the team goes on by itself.
Frequently asked
How does the first call work? +
Thirty minutes, free, no commitment and no slides. You tell me where the system is and what is blocking you, and we work out whether and how it makes sense to work together.
Do I have to start with the assessment? +
No. It is meant for those who want to see where to act before committing to an ongoing engagement. If the problem is already clear, we start straight from there.
What is left at the end of an engagement? +
A handover doc, the runbooks and an internal owner I have trained. Plus the code, the tests and the documented decisions: the system should not depend on me to keep working.
Got a technical decision that deserves clarity?
Thirty minutes are enough to see where the problem sits and whether I can be useful. No commitment, no slides.