DELIGHT — p2p protocol for AI agents
One clean home for the whole project: product story, architecture, docs, roadmap, risks, ecosystem, and founder narrative — without turning DELIGHT into a generic SaaS landing page.
Protocol · P2P mesh · LLM router · Compute farm · Local core
Voice · Orchestration · Memory · Browser farm · Local compute · Cloud routing · Automation · API
Alpha → public docs → network layer → ecosystem → tokenless economy → open protocol
Not a wrapper. A protocol-shaped stack for self-hosted AI agents.
A public layer that matches the architecture
DELIGHT should read like a real infrastructure project: clear enough for newcomers, serious enough for developers, and honest enough to build trust.
Protocol-first identity
The site explains DELIGHT as more than a product UI: it presents transport, compute, routing, and ecosystem direction as one coherent story.
Docs as trust
Documentation is part of credibility. Architecture, install flow, risks, and roadmap should be easy to inspect.
Global audience
The public layer should be readable across regions, which is why multilingual structure matters for DELIGHT from the start.
Launch-ready shell
This site should be good enough for GitHub release, Show HN, community sharing, and early protocol narrative.
Build the global public layer first
The stronger the public surface becomes, the easier it is to explain DELIGHT to developers, privacy communities, protocol builders, and future contributors.