DevOps consultant for software and health-tech teams
I help teams ship software safely and often. That means pipelines that check every change, infrastructure that is described as code, and monitoring that shows problems before users report them.
Or call me: +49 156 78 737 565
Where teams often stand
- A release is an event someone keeps the evening free for.
- There is no test environment that really matches production.
- Servers and cloud resources were set up by hand, and only one person still knows how.
- Monitoring says whether the site answers, but not why it is slow.
- The cloud bill keeps rising and nobody can say exactly what for.
What I do
- CI/CD pipelines in GitLab or GitHub that build, test and check every change.
- Infrastructure as code with Terraform or OpenTofu and Helm, so every environment can be rebuilt the same way.
- Containers and, where it pays off, Kubernetes, with separate environments for staging and production.
- Monitoring with OpenTelemetry and the Grafana stack that brings metrics, logs, traces and profiles together.
- Safe releases, with database migrations before the rollout, rollbacks and one-click approvals.
- Documentation and handover, so your team can carry the platform on by itself.
What changes afterwards
Every change takes the same path. It is built, tested, rolled out to staging and, after an approval, taken to production. Whoever writes a change sees within minutes whether it breaks something. A release can go out on an ordinary afternoon, and if something does go wrong, the previous version is one step away.
Because the infrastructure is described in code, a new environment can be set up quickly, for a load test or after an outage. The knowledge lives in the repository and the documentation, so new colleagues find their way faster. When something breaks, the monitoring shows which service is affected, which request was slow and which release the problem came with.
For teams handling health data
Teams that process health data have to be able to trace their changes. A pipeline that every change goes through provides that record along the way. It keeps track of who changed what, which tests ran and who approved it. I plan access rights, encryption and hosting in the EU from the start.
How it works
- First callfreeBy video or phone. You describe the situation, I ask questions.
- AssessmentSystems, dependencies and risks, written down.
- PlanTarget picture and steps, with priorities and effort.
- ImplementationStep by step, without disrupting daily operations.
- Operations and handoverDocumented, tested and handed over to you or your team.
Why work with me
I have worked in software since 2004. Today I lead infrastructure and DevOps at hessnatur; before that I was head of platform infrastructure at Calida Group Digital. So I know both sides, the code that gets shipped and the platform it runs on.
For Nun Pirat, an app for learning Arabic, I built the whole platform, with Kubernetes, shared pipeline templates and monitoring across everything. The case study shows how it is put together. From the first assessment to the handover you deal with the same person. More about me in the CV.
Related
Frequently asked questions
Do we need Kubernetes?
Not necessarily. Kubernetes pays off when several services have to scale and roll out independently. For a single application, containers and a good pipeline are often enough. We settle this in the assessment, before anything is built.
Do you work with our existing team?
Yes, that is the usual case. I build pipelines and infrastructure together with your developers, write the decisions down and hand over so your team can carry on without me.
GitLab or GitHub?
Both. I go with what you already use. What matters more than the tool is that every change takes the same path through tests and approvals.
Which cloud do you work with?
I work provider-agnostic, with the major clouds, German providers and your own servers. I keep the provider-specific part small so that a later move stays possible.
How do we know it is working?
Calmer releases, a shorter time from change to production, fewer failed deployments and faster recovery after errors. We measure these before and after.
Let's talk about your setup
In a free first call we look at where you stand and what the next sensible step would be.