I went down a rabbit hole. This is what came out.

‍

At some point I decided to catalogue every cloud resource that matters across Azure and AWS into one place. My team had questions. I didn't have great answers.

‍

The honest explanation is that the sprawl of it bothered me and I couldn't let it go. The cloud ecosystem has gotten genuinely enormous. Azure alone has hundreds of services, some of them overlapping in ways that aren't entirely clear even after you've read the documentation.

‍

AWS isn't simpler. The vendors keep shipping, the surface area keeps growing, and at some point just knowing what exists and where it belongs becomes its own problem, separate from whatever you're actually trying to build.

‍

Two hundred resources. Every icon in its place. Don't ask how long it took.

‍

Open cloudatlas.bitsummit.com and sit with it for a second before you do anything.

‍

Two hundred-plus cloud resources laid out in a grid. Every service has an icon. Every icon has a home: Networking, Compute, Containers, Databases, Security, AI, the whole stack.

‍

Azure and AWS organized the way an engineer actually thinks about them, not the way a product team arranged a navigation menu six years ago and quietly left it there. Every resource has its category, its code snippets, links out to the docs and pricing tools you actually need. Filter by service type and you get to what you're looking for in about two seconds.

‍

My team probably assumed I'd get bored around the hundredth resource and move on to something else. There are over two hundred in there now. I'm still adding things.

‍

Turns out organizing chaos is my love language.

‍

I'll be honest. I have a slightly embarrassing habit of organizing things that don't strictly need to be organized. Cloud Atlas is where that tendency finally produced something worth sharing publicly.

‍

There's something genuinely satisfying about taking something as chaotic as the modern cloud ecosystem and giving it a shape that makes sense. Not everyone gets that feeling. But if you've ever found yourself quietly reorganizing something nobody asked you to reorganize, you probably know exactly what I mean.

‍

Open it. Use it. Close it. That's genuinely the whole thing.

‍

What I like about Cloud Atlas, and I realize it's a little odd to say you like something you built yourself, is that it doesn't pretend to be more than it is.

‍

It's a reference. A fast, organized, visually clean reference for people who spend their days building in the cloud and occasionally just need a place to look something up without losing their train of thought.

‍

It's free. No account. No trial. No form asking for your work email so someone can follow up with you next Tuesday. You open it, you use it, you close it. That's the whole experience.

‍

The internet helped us build a lot of things. Feels right to leave something behind.

‍

We put it out publicly because the community has always been generous with this kind of thing. Good documentation, open-source tooling, people answering questions at odd hours on forums they don't get paid to be on. Cloud Atlas is our version of putting something back.

‍

Take it, use it, tell us what's missing.

‍

And if you're the kind of person who finds something satisfying about a well-organized catalogue of two hundred cloud resources, welcome. You're among friends here.