Atlas
A live graph of everything you own, and what depends on what.
Atlas is the current state of everything you own. Domains, servers, apps, accounts, keys, devices, and the relationships between them, held as one graph you can ask questions of instead of a list you have to maintain.
Why it exists
Most people cannot answer basic questions about their own estate. What domains do I have. What is running on that server. Which accounts hold a key that still works. If this one credential leaked, what would it reach.
The reason is not carelessness. It is that the answer lives in a dozen places — a registrar, a cloud console, a password manager, three config files, and memory — and no single place holds the relationships. So the questions go unasked until something breaks or something leaks, which is the worst possible moment to start an inventory.
How it works
Atlas builds a graph rather than a list. Assets are nodes; the edges are the relationships that actually matter — this worker serves that domain, this key unlocks that account, this app writes to that database. Collectors keep it current from the systems that already know the truth, so it reflects reality instead of the last time someone remembered to update a spreadsheet.
Because it is a graph, it answers questions a list cannot. Blast radius: if this asset were compromised, everything reachable from it. Ownership: what a given thing actually holds. Coverage gaps: what exists in the world but was never registered here, which is usually where the risk hides.
Three questions come built in, each one a query instead of an afternoon:
- owns→ what does this thing actually hold? A server's apps, a domain's services, an account's keys. inventory
- blast→ if this were compromised, what's reachable from it — one hop and every hop after. security
- unregistered→ what exists in the world that the graph doesn't know about yet. The gap is where risk hides. coverage
Where it fits
Atlas is the current-state half of the system’s own house. TELOS names where you want your life to go; Atlas names what you actually have right now. Security leans on it for blast radius, the change ledger leans on it for what shipped where, and any question that starts with “what do I own” stops being a research project.
It also changes what an incident feels like. When something leaks or breaks, the first hour is usually spent building the inventory you should have had; with the graph already current, scoping a compromise starts from the traversal, not from archaeology.
What it feels like
You stop carrying the map in your head. A renewal notice arrives for a domain and you can see in seconds what actually runs on it, or that nothing does and it can die. A new app ships and registering it is one more node with edges, not a wiki page nobody will update. And the nagging background question every builder has — “what have I got out there, and is any of it forgotten?” — has a live answer instead of a guilty shrug.