Software Development
Software you can still operate in five years. Sustainable solutions instead of quick money.
Focus areas
PHP ecosystem
TYPO3 and Symfony — from a single extension to a complete platform. My core territory for over 23 years.
Cloud-native & CI/CD
Cloud-native architectures on Kubernetes and AWS, plus automation and tooling around CI/CD.
Open source
Many of my tools are publicly available on GitHub. So you can check how I work before you hire me.
How I work
The problem first, then the code. And when an existing solution fits better than a custom build, I will say so.
Documented, tested, reproducibly deployable. Security is part of the architecture from day one, not an afterthought.
Code your team can keep developing without me after the project ends. No lock-in — not even with a freelancer.
Got a project idea or
a concrete problem?
Software you can still operate in five years — best discussed directly. A short message is enough, I will get back to you personally.
What I work with
- PHP ecosystem: TYPO3 and Symfony — from a single extension to a multisite installation.
- Cloud-native operations: Kubernetes and AWS, container images, CI/CD pipelines, deployment without downtime.
- Integration: interfaces to the systems you already have, instead of rebuilding everything.
How handover works
The most common reason external development goes wrong: what remains at the end is code nobody on the team understands. So handover means your team can carry on — documented decisions, a structure people can follow, no constructions only I can maintain.
If you do not need me afterwards, it worked.
Look at the code before you hire me
I publish the building blocks I use in projects under Open Source — from a cache backend for TYPO3 in a cluster to the FrankenPHP integration. So you can check how I build rather than take my word for it.
On the blog I describe the same decisions in operation: why I ship TYPO3 as an OCI artifact, how fileadmin runs on S3, what actually holds up in cluster operation.