Landing zones
First Azure environment, done right
For startups outgrowing "one subscription, no structure." Subscriptions, naming, RBAC, and guardrails set up before the mess accumulates, not after.
Azure infrastructure / for growing companies
I'm Soroush. I work with startups and mid-size SaaS teams at three moments where Azure infrastructure tends to go sideways: setting up a real environment for the first time, migrating off on-prem, and reining in a cloud bill that grew faster than anyone was watching it.
Landing zones
For startups outgrowing "one subscription, no structure." Subscriptions, naming, RBAC, and guardrails set up before the mess accumulates, not after.
Cost optimization
For SaaS teams whose spend crept up unnoticed. Reserved instances, right-sizing, and waste elimination — usually with savings visible in the first billing cycle.
Migration
For companies moving workloads off self-managed hardware. Staged migrations with rollback plans, not a risky weekend cutover.
01
A reusable Terraform module for standing up a baseline Azure landing zone — subscriptions, policy, networking — in an afternoon instead of a month.
02
A small script that pulls your Cost Management data and flags the highest-impact savings opportunities, ranked by effort to fix.
03
A portfolio and blog, served by Gunicorn and Nginx on a small Hetzner Cloud box — proof that "the right tool" doesn't always mean the obvious one.
If any of the above sounds like where you're at — a first real Azure environment, a migration on the horizon, or a bill that's gotten away from you — reply with a bit about your setup and I'll tell you honestly whether I can help.
hello@example.com