Jobin Joseph

Sixteen years in cloud, mostly in the trenches.

I started in cloud infrastructure in 2009. Back then, "cloud" mostly meant figuring out how to make EC2 stable enough for production. Since then, I've built and migrated hundreds of workloads across AWS, watched the platform grow from a handful of services to over 200, and watched the AWS partner ecosystem grow alongside it.

The pattern I kept seeing on the buyer side was always the same: AWS-certified people on the sales call, juniors on the actual work. The big consultancies do it. The mid-tier AWS partners do it. The offshore body shops definitely do it. Every founder I talked to had been burned by it at least once.

Why the gap exists, and why it's hard to close.

The structural reason is simple. AWS-certified specialists are expensive. Junior engineers are cheap. The unit economics of most AWS partners require a 3:1 or 4:1 leverage ratio to be profitable, so they sell AWS-certified expertise and deliver junior labour. It's not malicious. It's just the model.

For most workloads, that model is fine. For compliance-heavy workloads, it breaks down. DORA-aligned FinTechs, APRA-regulated banks, NIS2-captured SaaS, IRAP-PROTECTED government suppliers: a junior engineer cannot make architecture decisions that have regulatory consequences. The cost of getting it wrong vastly exceeds the cost of paying for AWS-certified time.

Why I founded HAZERCLOUD.

HAZERCLOUD exists to be the structurally founder-led alternative for compliance-aware AWS workloads. We took an explicit decision early on. We would cap concurrent engagements at the level where I can personally engage with every one of them. We would price for that. We would document it on the website. We would operate it.

That's why we got AWS Advanced Tier Partner status. It's why we certified the company itself to ISO 27001:2022. Not because a customer required it, but because we wanted to live the standard we recommend. It's why every engagement runs through me personally: discovery call, weekly review, architecture sign-off. No exceptions, no AWS-certified-handoff-to-juniors after the SOW.

What this means for you.

If you're scoping DORA, APRA CPS 230, NIS2, or any other compliance-aware AWS engagement, what you get is the founder personally engaged on your project. Not "available for escalation." Not "involved in steering committees." Personally engaged: at every weekly review, signing off on every architecture decision, accountable for every regulatory deliverable.

It's a deliberately small market we serve, because the model only scales so far. But for the projects where it matters, where compliance is non-negotiable and your CISO is staking their job on the partner choice, this is the model that works.