Cloud architecture consulting
I am a cloud architect who also writes code. I fix what teams put off until it hurts: landing zones, infrastructure as code, identity, environment isolation and the monthly bill.
The usual story
A team builds something that works in a demo. Sometimes it is an AI system, sometimes a SaaS app. Then it needs real traffic, real data and an auditor. Nobody on the team owns that part, so it gets bolted on: one shared subscription, infrastructure code nobody reviews, admin rights for everyone.
Getting into the cloud is the easy part. Keeping governance, security and cost under control once many people are creating resources is where it goes wrong. That is the work I do.
Every control has a price. Stricter isolation means more environments to pay for and maintain. Tighter policy slows the first deployment. I will tell you what each one costs and where I would draw the line. You make the call.
What I fix
Typical situations, not a client list. Each one comes with what I would do and what it costs you, because every fix has a price.
Dev, staging and production share an account, or several teams share one. A bad deploy or a leaked credential reaches everything.
Nobody has the full picture, modules are copy-pasted, and the console no longer matches the code.
Admin rights were handed out to get things moving, and nobody remembers why.
It runs locally or in one fragile environment, and the first customer security questionnaire is on its way.
Nobody can say what the spend is for, and resources nobody owns keep running.
Approach
Pick a slot. Two lines on your stack and what hurts is enough.
We go through the setup on video. You leave with a ranked list of what to fix and what to leave alone.
If you want more: a one-off review, an architecture design, or hands-on work alongside your team. If not, that is fine too.
Who you are talking to
I lead cloud architecture for a large enterprise estate, and I have spent more than ten years between software engineering and cloud. I write code as well as diagrams, so what I recommend has to be buildable.
I work with teams in Denmark and abroad, mostly online. Advisory or hands-on, depending on what you need.
Book a session
Online, on Cal Video. Add two lines on your stack and the problem when you book. It saves us the first ten minutes.
Both. A call is advisory. If you want more, we agree a scope: a review, an architecture design, or hands-on work alongside your team.
A ranked list of what to fix and what to leave alone. No obligation to continue.
Yes. I treat your environment as confidential and I am happy to sign an NDA before we go into detail.