Services.

Two kinds of problems keep landing on my desk. Alongside them one specialist area where I go deep, without it being a third of the business. All of it running in production today, not just on slides.

Where I come in

Systems that carry. Decisions that hold.

Most problems that land on my desk are not code problems. They are decisions that were right years ago and now cost money, speed or nerves: an AWS bill nobody can explain any more, a workflow that eats days every month, a system nobody wants to touch.

That is exactly where I work. Always with the same pattern: first understand how the system really behaves, then decide what has to be built, then deliver, in steps that each carry value and can each be turned back.

20+years in software development, more than ten of them in distributed systems
5certifications from AWS and HashiCorp, including Solutions Architect Professional
2003working remotely since that year, with no agency in between

Services

Two problem areas, one specialist area.

01

Stabilize & scale systems

When systems get too fragile or too slow for further growth.

Modernizing business-critical backends, clearing technical debt and migrating platforms to AWS, without putting live operations at risk.

02

Optimize your AWS architecture

When AWS runs, but it has become too expensive, too unstable or too hard to change.

Three symptoms of the same cause: the bill climbs, a single fault takes the whole application down, and nobody dares to change anything. I work at the places where that gets decided, and I deliver Terraform and code rather than an assessment.

Reducing AWS costs

Entry offer: AWS cost analysis, 2,400 €

I find where your AWS budget leaks away, and cut it measurably without giving up performance or availability.

Cost ExplorerSavings PlansRightsizingS3 LifecycleCURFinOps
Learn more

Improving AWS resilience

Entry offer: Outage rehearsed, 3,900 €

So that a single fault does not take the whole application with it: dependencies and single points of failure identified, recovery rehearsed rather than documented, changes delivered as Terraform.

Multi-AZFailoverRTO / RPOTerraformFault injectionRecovery
Learn more

Further specialist areas

Agentic engineering & AI integration

A competence and a way of working rather than a third pillar: I build AI and automation in where they genuinely carry a process, with identity, cost, quality and a fallback path settled. It can also be commissioned on its own.

Looking for a role?

Freelance PHP DeveloperMore than 20 years of PHP, from 5.x to 8: upgrades, modernization and taking over grown systems, while they keep running.
Freelance Go DeveloperGo services with production experience: millions of requests a day, gRPC and multi-region on AWS, alongside your existing system.
Freelance AWS ArchitectArchitecture for AWS environments that already run: cost, resilience, migration and infrastructure as code.

Not sure which one fits?

Let’s spend 30 minutes finding out whether I can help.

Book a call

How it runs

How working together goes.

The same approach across every area. No waterfall, no months without a result. You decide after each phase whether it continues.

STEP 01

First call, 30 minutes

You describe the system and the goal. I tell you honestly whether I am the right person. No pitch, no slides.

STEP 02

Analysis built on facts

I read the code, the infrastructure and the incident history. What comes out is a ranked list, not an impression.

STEP 03

Delivery in increments

Work ships in increments that can go to production individually and be rolled back individually. At a fixed price or by time spent, to suit the project and the model you prefer.

STEP 04

Handover to the team

Pairing, runbooks and documented decisions. The goal is your team, not an extension of my contract.

Common questions

Before you ask.

How does working together start?

It starts with a 30-minute call where we work out what you need and whether I am the right person for it. Then comes a short analysis phase with a concrete deliverable, a risk list, a target architecture or a plan of action, and only then implementation. You decide after each phase whether and how it continues.

Do you work remotely or on site?

Remote from Germany is the default, and has been since 2003. Workshops, kick-offs or architecture sessions on site are possible by arrangement where they make a real difference. Day-to-day work runs asynchronously with fixed times for alignment.

Do you take on smaller engagements?

Yes. Clearly bounded entry packages show their scope and price on the page, including the AI production review from 2,400 euros, the AWS cost analysis at 2,400 euros and the AI phone assistant at 3,900 euros. Not every problem needs a large project.

Do you only advise, or do you implement?

Both, and the larger part is implementation. I write code, build infrastructure and pipelines, and work alongside your team while doing it. In my experience, advice without implementation produces documents nobody reads.

What does it cost?

To suit the project and the model you prefer: a fixed price or billing by time spent. Clearly bounded work can be scoped in full beforehand, and that gets a fixed price. For longer or more open-ended work, where the order of tasks shifts along the way, billing by time spent is usually the more honest model. Which one it is we decide together after the analysis. The entry packages carry fixed prices: the AI production review from 2,400 euros, the AWS cost analysis at 2,400 euros, the AI phone assistant at 3,900 euros.

Which languages do you work in?

German and English. Several of the projects behind the case studies ran entirely in English, with distributed teams across Europe and the US. Documentation, code and reviews in either language, whichever fits your team.