Skip to content

Overview

OpenInfra is an open-source hosting network (DePIN) where hosts provide compute and storage resources, earn rewards, and — at the vision’s end state — participate in a peer-to-peer network with no central authority. Users browse a catalog and deploy services onto host hardware.

It is built centralized-first, decentralized-by-design: a working centralized control plane ships today, with the architecture deliberately shaped so the trust-bearing pieces (host registry, rewards, governance) can migrate on-chain as the network matures.

  • Control plane API — REST for users (chi router), gRPC + mTLS for host agents, JWT auth, role-based access, rate limiting, OpenAPI spec.
  • Service catalog + workload lifecycle (deploy / stop / restart).
  • Score-based scheduler placing workloads on hosts by capacity & reliability.
  • Host agent — registration, heartbeat, metrics, and a container runtime path for workloads today (Firecracker microVM path in progress).
  • Centralized credits ledger — double-entry billing, hourly metering, reward epochs.
  • React web portal served by the API server.

These are aspirational and deliberately deferred until the platform matures:

  • Firecracker microVMs for VM-level workload isolation (~125 ms boot).
  • WireGuard mesh for encrypted host-to-host networking.
  • IPFS for decentralized content-addressed storage.
  • On-chain layer (Cosmos SDK / CometBFT) for host registry, OINFRA token rewards, staking, and DAO governance — currently deferred in favor of the centralized ledger.

ChessLabs Coach runs its chess-analysis worker as an OpenInfra workload — a real application served from the network today.