Cloud migration
Get onto AWS or GCP without a scary big-bang weekend. We move what's worth moving, skip what isn't, and keep everything running while we do it.
I make production fast, cheap, and boring — AWS, Kubernetes, and zero-downtime deploys that don't wake anyone up.
Get onto AWS or GCP without a scary big-bang weekend. We move what's worth moving, skip what isn't, and keep everything running while we do it.
Kubernetes — but only if you actually need it. Set up to grow when traffic spikes and shrink (with the bill) when it doesn't, minus the thousands of lines of YAML nobody understands.
Find the line items quietly draining your budget and cut them — then make deploys boring enough that nobody gets paged at 3am. Boring beats clever.
Make shipping a non-event: you push, it deploys, everyone moves on. The whole setup lives in Terraform — reviewed, versioned, and rebuildable from scratch.
Where this leads: infrastructure you can stop thinking about — so your team gets back to building the product, not babysitting servers.
Beyond ops, I also review architecture, audit AI-built apps, and take ideas to production.See all services →
A free call and a look at your stack. I find the quick wins and the real risks — no jargon, no upsell.
A clear, prioritized roadmap with effort, cost, and expected impact. You decide what gets done and when.
I implement alongside your team, document everything, and leave you able to run it without me.
Chatter is a privacy-first encrypted messenger I'm building on the side — one Rust client (Slint) that runs on Linux, Windows, and Android today, with iOS and macOS planned, on a Go backend with Signal Protocol end-to-end encryption. It's still in development, but it's how I stay hands-on across the whole stack, from cryptography to deployment.
I'm a DevOps engineer with 6+ years shipping cloud infrastructure on AWS, Kubernetes, and Terraform — that's the day job, and the main spin. On the side I build Chatter, an encrypted messenger, from one cross-platform codebase — which keeps me hands-on across the whole stack. So I can also review your architecture, de-risk an AI-built app, or help take an idea to shipped. Either way, I care about boring, reliable systems and explain the trade-offs in plain language, not buzzwords.
I find what's slow, expensive, or fragile in your infrastructure and fix it — then set things up so your own team can run it after I leave. The goal is to make myself unnecessary, not to lock you into me.
No scary big-bang weekend. We move one piece at a time, keep production running the whole way, and roll back the moment anything looks off. Most migrations finish without users noticing.
Honestly, often not. If a handful of containers or managed services do the job, that's what you get. Kubernetes only goes in when your scale or complexity actually earns the extra moving parts.
It starts with a free call and a look at your stack. From there you get a fixed-scope proposal or a day rate — your choice. You approve the plan and the cost before any work begins.
Usually within a week or two. I work alongside your engineers rather than over them, document everything as I go, and hand it over so nothing depends on me being around.
Book a free 30-minute call. We'll find the quickest wins in your infrastructure — no commitment.
Book a free discovery call
A Windows build of my chat app crashed with no Rust panic—just an access violation deep in C. Tracking it down meant learning how compilation, symbols, and linking actually work underneath cargo.
Read full article: Two Cryptos, One Binary: How Rust Links With C (and How I Got Heap Corruption) more →
The 'just read the code' advice is dead. From weaponized VS Code tasks to clipboard-hijacking CAPTCHAs, here is how state-sponsored actors like Lazarus have evolved their tactics to compromise even the most cautious developers.
Read full article: The Cat-and-Mouse Game: How Developer Recruitment Scams Mutated in 2026 more →
Building a chat app taught me that every abstraction layer has a cost—and some costs only become clear when you're deep in development.
Read full article: From React to Rust: Why I Switched to Native Mid-Project more →