# Graph Schema

> Map of the WhisperGraph schema: how the layers stack and join, and where the full entity, connection-type and pivoting references live.

*Source: https://www.whisper.security/docs/whisper-graph/schema*

---
WhisperGraph models the internet as **one connected graph** — every layer joined to the next, so a single query can walk from a hostname to the building that routes it. As of the latest census the graph holds **41 node labels** and **52 edge types**, across **7.5B nodes and 39.7B edges**. This page is the map; the three references below hold the names.

![The WhisperGraph schema — node labels and edge types pre-joined into one graph (a curated core of the model).](/images/docs/whisper-graph-schema-erd.svg)

The three references listed above split it apart: entities names every node label with its row count, connection types names every edge with its endpoints, direction and how populated its plane is, and pivoting examples carries the worked chains that cross layers.

Because the layers are already joined, a cross-layer question is one traversal rather than four lookups: a hostname resolves to an address, the address sits in an announced prefix, the prefix is routed by an autonomous system, and that system is present in a named facility.

## Where next

[Procedures](/docs/whisper-graph/procedures) wrap multi-step logic into a single `CALL`, and the [procedure reference](/docs/whisper-graph/procedures/reference#schema-introspection) lists the introspection calls that return the live label, edge and property sets. For the query language itself, see [Cypher](/docs/cypher).