Your estate,
on one globe.
Most teams cannot name every region they are paying for. The globe plots each one, coloured by provider, sized by what is running there. Click a region and the architecture canvas opens already filtered to it.
A map you can act from.
The globe is a way into the estate, not a screensaver.
Plot
Discovered resources are mapped to their region's real coordinates. Counts stream in as discovery completes, so the picture fills progressively instead of blocking on a full load.
Filter
Narrow to one provider or to a tag. AWS, GCP and Azure each carry their own colour, so a region running all three reads at a glance.
Open a region
The detail panel breaks the region down by resource type and cloud account. This is usually where the forgotten staging environment turns up.
Hand off to the canvas
Jump from a region straight into the architecture view, pre-filtered to that provider and region. The globe's own cache is reused, so the canvas paints immediately instead of re-fetching.
Regions are where the surprises live.
Estate sprawl is geographic before it is anything else.
- Coverage
- AWS, GCP and Azure, plus Snowflake, Databricks and Kubernetes on EKS, GKE, AKS and OpenShift. The discoverer enumerates every one of them.
- Read path
- Discovery is read-only against your cloud. The globe never mutates anything, so it is safe to hand to anyone who needs the picture.
- Filters
- Provider and tag, applied server side. The selection carries through to the architecture canvas rather than resetting when you navigate.
- What it is not
- The globe is a discovery surface. Cost lives in Cost Reports, dependencies live on the architecture canvas. It hands off to both rather than duplicating either.
Find the region you forgot about.
Connect a read-only role. The globe fills in as discovery runs.