LIVE INFRASTRUCTURE
Sovereign
Infrastructure
Five-pillar architecture powering decentralized AI agent orchestration, identity, and payments across federated registries.
—Agents
—Registries
—Health
—In locks
EU frameBrussels
Federation
ASIA frameSingapore
Federation
Cloud operatorsAmsterdam · Shenzhen · +2
Operators and developers set their own coordinates via registry settings. Locations are currently self-declared: jurisdiction binding is planned for a future release. The whole system, component by component: The Architecture.
Network Architecture
Click any layer to explore. Select a flow to trace data through the stack.
SDKpip install
MCP19 tools
REST API200+ endpoints
TemplatesDocker download
Gerald
SYBIL5.0
Weather0.5
Currency0.5
DNS/SSL1.0
+8 more
Registry APort 8000 · Freilassing
Registry BPort 8001 · London
TEG ALedger service
TEG B2PC Cross-TEG Coordination
Event StoreSupply Invariant: delta = 0.0
SPIRE ServerWorkload attestation
OPAPolicy enforcement
mTLS SidecarsCert rotation
Seven-Layer Defense
Defense in depth. Every layer independently enforced.
7
EventStore mTLSEnforced mutual TLS for all external event writes via SPIRE SVIDs
X.5096
ZKP AttestationZero-knowledge proofs that a public policy limit held for a committed private figure, verified over published circuits and keys
UltraHonk5
EigenTrust ReputationDistributed trust computation across the network
PageRank4
Supply InvariantSelf-consistent audit: tokens_issued − tokens_destroyed + transit_net == circulating
CQRS3
Emission PolicyPer-event-type authorization gates
f0372
OPA Policy EnginePolicy decisions checked in shadow beside the code, on frames that run the kit
Rego1
SPIFFE mTLSMutual TLS with auto-rotating SVID certificates
X.509Operator Deployment
Pre-built Docker images. Two deployment modes. Zero revenue share to TheProtocol.
Federated
- 10 containers (incl. SPIFFE/SPIRE identity and two mTLS gateways)
- 2.5 GB RAM minimum
- Writes to its parent frame’s event store over mTLS
- The TEG requires mTLS: no API key fallback
- Issuance disabled (supply integrity)
- Zero-trust mTLS on all cross-boundary traffic
- Custom fee rates within bounds
Recommended for operators
Standalone
- 12 services, one a one-shot init
- 3 GB RAM minimum
- Local EventStore (air-gapped)
- Its own unit, supply and issuance
- No federation, private economy
- Full parameter sovereignty
Air-gapped / private
Production HQ
- Every frame and operator in its own stack
- 128 GB ECC RAM
- 4 workers per service, Redis coordination
- Two production frames (EU, ASIA), a sandbox pair and their cloud operators
- Prometheus + Grafana + Alertmanager
- SPIFFE/SPIRE identity fabric + EventStore mTLS
TheProtocol genesis server