Infrastructure shouldn't be the scariest part of shipping.
I'm Przemysław. I spend my days in Kubernetes, GitOps pipelines, and other people's cloud bills. If your infrastructure has quietly become the thing nobody wants to touch, that's the part I'm good at.
What people actually hire me for
Getting off the lock-in treadmill
Your workloads should be able to leave. I build on open-source tooling and portable abstractions, so moving between Azure, AWS, or your own metal is a migration, not a rewrite.
Kubernetes that fails politely
Every cluster breaks eventually. What matters is whether you hear about it from your dashboards or from your customers. I build for the first one.
Deploys nobody dreads
Declarative pipelines where shipping infrastructure feels like shipping code: reviewed in a PR, merged, done. And easy to undo when it turns out you were wrong.
Notes I keep so I don't relearn things twice
It's just me. That's the point.
sawczuk.dev is a one-person practice. The person who designs your infrastructure is the person who builds it — no account manager in the middle, no quiet handoff to someone junior after the kickoff call. I take on a small number of engagements at a time, because that's the only way that stays true.
Something gone sideways?
Send me the messy version — the 3am pages, the pipeline nobody understands, the bill that keeps climbing. If I'm not the right person for it, I'll say so and try to point you at someone who is.