Google Cloud, Kubernetes and CI/CD, built so a small team can run them. I design it, ship it, and stay on call for it. Błażej Lubecki, Lead DevOps Engineer.
Live · my own hardware
this page is served from a machine in my flat
Clusters, Cloud Run, Cloud Functions and networking, built so a small team can run them. Migrations off click-ops and legacy lift-and-shift, with a plan you can roll back.
Pipelines, GitOps and release automation that make shipping routine. Build once, deploy anywhere, roll back fast, so a small team ships like a big one.
Terraform and Ansible that turn infrastructure into versioned, reviewed code. Reproducible environments, auditable changes, and nothing that exists only in someone's browser history.
Metrics, logs and alerts that stay quiet until something is genuinely wrong. SLOs you meet, and on-call that doesn't burn people out.
Architecture that degrades gracefully instead of falling over.
CI/CD that removes the fear of releasing. Smaller, safer, more frequent deploys.
Resources fitted to real load, plus the FinOps evidence to back the bill.
I run the infrastructure. You only hear from me for decisions only you can make.
Stand up a Kubernetes platform on GKE with GitOps and a real pipeline, so a small team ships daily instead of weekly, with a rollback path you have tested.
Move a system off legacy hosting to Google Cloud with a zero-downtime cutover plan, IaC from day one, and an escape hatch the whole way through.
Add SLOs, alerting that pages a human only when needed, and right-size cloud spend so uptime climbs while the bill comes down, and you can prove both.
You tell me what's running and where it hurts. I look at the real state and what it is costing you. No sales deck.
A short written proposal: what I'd change, in what order, and what it maps to in time and spend.
Small, reviewable increments you can see and roll back. No big-bang cutovers, no surprises on the invoice.
Handover and docs so your team can run it, with the option of me staying on call.
Tell me what you're running on and where it hurts. I'll reply with how I'd tackle it. Concrete, no obligation, no jargon.