About CloudMonitor

Built by someone who's been paged at 2 AM for an expired certificate.

CloudMonitor exists because infrastructure failures that should never happen — still happen constantly. Expiring secrets, idle VMs silently burning budget, certificates nobody noticed were 3 days from expiry. I've lived every one of these. So I built the tool I always wished existed.

Background

I'm a cloud architect and infrastructure engineer with 20+ years of experience in IT. My career spans hands-on roles across network engineering, systems administration, cloud migration, and platform architecture — the kind of career path that builds a deep appreciation for what breaks and why.

My deepest hands-on experience is in Microsoft Azure, but the work has spanned AWS, GCP, Kubernetes, and a long tail of SaaS platforms — helping organizations migrate legacy workloads, design secure cloud architectures, and build operational processes that scale across every cloud they end up on. That work gave me a front-row seat to a consistent problem: teams are great at building things in the cloud, and terrible at watching them afterward — regardless of which cloud they pick.

Not because they didn't care — but because proper monitoring tools were expensive, complex, and built for teams of 10, not for the 1–3 cloud engineers actually running the show at most companies.

Why I built this

The recurring problem
Expiring credentials nobody was watching
Every few months, something expired that shouldn't have. A Key Vault secret. An API key. An SSL certificate. Each one caused an outage that was completely preventable with a simple alert 30 days earlier.
The cost problem
Idle VMs nobody noticed
Every cloud makes it easy to spin things up and easy to forget them. I've audited Azure, AWS, and GCP environments with thousands of dollars per month in idle or orphaned resources — VMs, EC2 instances, disks, snapshots, public IPs — all quietly billing on autopilot.
The solution
A monitor that works like a second engineer
CloudMonitor was built to be the patient, never-tired infrastructure reviewer that most teams can't afford to hire — covering every cloud, cluster, and SaaS platform they actually run, in one place. It walks the whole estate in turn, scanning, classifying, and surfacing the things that matter before they become incidents — so the rounds get made whether or not anyone is awake to make them.

What I believe

⚡
Prevention over reaction
The best incident is the one that never happens. Good monitoring means knowing about problems days before they become emergencies.
Simplicity is a feature
Enterprise monitoring tools are bloated. CloudMonitor shows you exactly what you need, in plain language, with a link to fix it.
◑
Cost visibility matters
Where a finding is costing you money, it shows the estimated monthly cost. Because telling you there's a problem is only half useful — you need to know if it's worth fixing now.
◎
Security by default
CloudMonitor reads metadata only — never secret values or key material. Read-only access, credentials encrypted at rest, a secretless connection where we have built one, and tenant isolation always.

Technical background

My core expertise spans cloud infrastructure architecture, identity and access management, network security, and DevOps automation. I've designed and operated multi-cloud environments — Azure, AWS, GCP, and Kubernetes — from small startups to enterprise platforms with thousands of cloud resources and tens of thousands of containers across hundreds of deployments. Much of my 20+ years in IT has been operations: the pager, the runbook, and the 2 AM escalation.

Microsoft Azure Amazon Web Services Google Cloud Kubernetes Cloud Architecture Infrastructure Security Identity & Access Management DevOps / Automation Network Engineering Python / PHP / Bash PostgreSQL / Monitoring Systems

Want to see it in action?