Architecture Overview

The Geo Web is an open information network. It's conceptually (and philosophically) similar to the World Wide Web in many ways. Just as several underlying protocols and components create the experience of "surfing the web," the Geo Web is defined with a multi-layer technology stack.

While not 100% analogous, we can compare the Geo Web stack to the more familiar web stack as a starting point for deeper technical exploration. Check out the table below to start building your mental model of the Geo Web:


Traditional Web

Geo Web



Domain Name System (DNS)

Geo Web Smart Contracts

Geo Web coordinates are like IP addresses. Parcels are like domain names.


DNS Servers

Geo Web Subgraph

The Graph network allows the Geo Web subgraph to scale and perform like DNS without centralization or an extensive infrastructure buildout.

Namespace Registration

Domain registrars

(eg GoDaddy)


The Cadastre also includes functions similar to a CMS on the traditional web. It won't be the exclusive way to register or trade Geo Web land.

Content Transfer

Hypertext Transfer

Protocol (HTTP)


IPFS is a peer-to-peer transfer protocol, so concepts around file storage differ from HTTP's client-server assumptions.

Content Formatting

Hypertext Markup

Language (HTML)

Ceramic Network

Ceramic can additionally be used to define identities on the Geo Web via IDX


Wayback Machine


Filecoin is used as the archival complement to IPFS & Ceramic's "hot storage" for Geo Web content.

Browsing Interface

Web Browsers

(eg Chrome)

Spatial Browser

Competition across browsers will be encouraged on the Geo Web as on the WWW.

In the remainder of this section, we'll explore these components first from a functional perspective then at a detailed technical level. This section is targeted for developers and technical users, but non-developers can benefit from this information as well.