The landscape, made visible.

From an office floor to the product.

The head of operations walks into the IT room and asks: “If the Berlin office goes dark, what do our customers lose?” The map answers it. It is built in 3D: floors go from physical locations up to the products you deliver, and towers next to them hold people, equipment and requirements. The admin follows the line from a rack in Berlin to the customer portal that would stop.

Cloud servers get a place too. A region code like “eu-central-1” becomes a country and a city on the world map, a dot you can point at.

Red means down. Orange means planned.

A red ring around an object is an outage. An orange ring is maintenance in progress. The rings come from the recorded state of the product, not from a colour somebody picked to look urgent. When the manager asks what is down right now, the admin turns the screen around.

Find what was forgotten.

Every company has them: a virtual server somebody set up for a test two years ago, a licence that supports nothing. The map finds objects with no connections and objects whose links never reach a product. A daily check lists what has newly become disconnected, so cleanup is a ten-minute routine, not a yearly audit.

Why a picture helps.

A table is good for finding one thing. A map is good for seeing the whole picture: a product that rests on a single server, an office with far more equipment than people, a link between two clients that should not exist. Those are the things that turn into outages later.