Skip to content
Gao Internet
Architecture

Eight layers. One system.

Gao Internet is built from eight layers with one job each. Apps and agents combine them — so identity, payments, communication and AI permissions behave the same way everywhere.

System map

PeopleBusinessesDevelopersAI agents

Access & build

Shared services

Infrastructure

Numbers name the layers; they are not a call order.

All layer relationships

  • Gao Workspace uses Gao Domains: Signs people, teams and agents in with their own identity.
  • Gao Workspace uses Gao Payment: Receipts, invoices and billing settle through Gao Payment.
  • Gao Workspace uses Gao Network: Messages and notifications reach customers and teammates.
  • Gao Workspace uses Gao AI OS: Agents assist with operations under granted permissions.
  • Gao Browser uses Gao Domains: Resolves .gao names and verifies apps and merchants.
  • Gao Browser uses Gao Payment: Presents payment prompts for the user to approve.
  • Gao Browser uses Gao AI OS: Surfaces AI actions behind policy checks.
  • Gao SDK exposes Gao Domains: Identity and .gao resolution for third-party apps.
  • Gao SDK exposes Gao Payment: Payment intents and receipts for third-party apps.
  • Gao SDK exposes Gao Network: Messaging and notifications for third-party apps.
  • Gao SDK exposes Gao AI OS: Scoped agent permissions for third-party apps and agents.
  • Gao Payment uses Gao Domains: Payments are tied to the payer's own identity and wallet.
  • Gao AI OS uses Gao Domains: Agents are bound to the identity they act for.
  • Gao AI OS uses Gao Payment: Agent-initiated payments still need the user's approval.
  • Gao Network runs on Gao DePIN: Community nodes contribute relay and storage capacity.

Three tiers

Access, shared services, infrastructure.

The numbers name the layers; they are not a call order. What matters is where each layer sits and what it shares.

How Gao Internet works

From intent to receipt.

One identity, one set of permissions, one trail of receipts — across every app, agent and device.

  1. 01

    A person, business or AI agent

    Every action starts with someone — or an agent acting for them.

  2. 02

    Signs in with their own identity

    A .gao identity they own, with keys that stay on their device.

  3. 03

    Opens a Gao app

    Gao Workspace, Gao Browser or any app built with Gao SDK — same identity everywhere.

  4. 04

    Communicates privately

    Messages, notifications and relays travel over Gao Network.

  5. 05

    Approves payments and actions

    Sensitive steps wait for the user's approval. Payments settle without custody.

  6. 06

    Lets agents help — within limits

    AI agents act only inside the permissions granted, with an audit trail.

  7. 07

    Runs on community capacity

    Independent DePIN nodes contribute storage and relay capacity underneath.

  8. 08

    Gets the result — and the receipt

    The outcome is delivered and the record stays with the user.

Illustrative flow. Each Gao app uses only the layers it needs.

Authorization

Sensitive actions follow one path.

Whether a person, an app or an agent starts it, a sensitive action is approved by the user, checked against policy, scoped, and recorded.

Trust model
  1. 01RequestAn app or agent asks to act.
  2. 02Your approvalConfirmed with keys on your device.
  3. 03Policy checkRules run before anything executes.
  4. 04Scoped permissionOnly what the task needs.
  5. 05ReceiptA record you can review later.