Every team has an architecture diagram. Nobody trusts it. Here's what we built instead.

The actual problem with cloud architecture visibility.

The real issue isn't that teams don't document their infrastructure. It's that cloud infrastructure changes faster than any manual process can keep up with.

A developer spins up a debug RDS instance on a Friday. A new region gets added during a scaling event. A contractor deploys a service that nobody else knows about. None of these show up in any diagram because nobody updated it.

The other problem: existing tools either give you one cloud at a time, or they give you a billing view which tells you what you're spending, but not how anything connects.

What we wanted was: open Atlas, see everything, understand how it fits together. Across all three clouds. In real time.

What Atlas does

Atlas connects to your AWS, GCP, and Azure accounts in read-only mode and auto-discovers every resource. It then builds a dependency graph, not just a flat list of resources, but how they relate to each other. Which services talk to which? What sits behind which load balancer? Where the cross-region connections are.

The view scales from global (all your clouds, all your regions, one screen) down to service-level dependencies. You can zoom into a single VPC and see exactly what's running inside it.

Here's a short demo:

The part that was harder than expected

The interesting technical challenge was reconciling three completely different resource models.

AWS thinks in terms of VPCs, availability zones, and security groups. GCP thinks in terms of projects, networks, and firewall rules. Azure thinks in terms of subscriptions, resource groups, and virtual networks. Same concepts, completely different hierarchies and naming conventions.

Building a unified topology meant building a translation layer that could map these different models onto a consistent graph structure without flattening the differences that actually matter for understanding your architecture.

We also had to decide what "connected" means across clouds. A Lambda that calls a GCP Cloud Run service over HTTPS are those connected in the topology? We landed on: yes, and we show cross-cloud connections explicitly because they're often the least-understood part of a multi-cloud setup.