What is Evolving Edge?
The network
Section titled “The network”Evolving Edge operates a distributed computing cloud built from residential and small-business devices - Mac Minis, PCs, home servers, NAS boxes, Raspberry Pis - enrolled in the network and put to work delivering content and compute to people and businesses nearby. Instead of routing a request halfway across the country to a data center and back, the network serves it from the neighborhood. That’s how it hits sub-10ms response times where traditional cloud CDN infrastructure typically lands at 70ms or more.
The software running on each device is called the node agent - a lightweight, open-source binary written in Go. It handles content caching and serving, authenticated communication with the control plane, WebRTC NAT traversal (so it works even behind restrictive firewalls without port forwarding), and continuous performance telemetry. The whole thing is open source under the Mozilla Public License 2.0, which means anyone can read exactly what it does - what data it sends, how content is handled, how a device behaves on the network. No black boxes.
One thing worth knowing about network access: Anyone can read, modify, and compile the node software freely. But only binaries cryptographically signed by Evolving Edge are allowed to join the official network. This isn’t about control for its own sake - it’s how the network stays secure, compliant, and trustworthy for everyone relying on it. Transparency for operators, integrity for the network.
Nodes are organized into MSAs (Metropolitan Statistical Areas) and POPs (Points of Presence) - geographic groupings based on latency - and coordinated by an AI-driven orchestration layer that handles routing, workload assignment, performance scoring, and anomaly detection. See the Glossary for full definitions of these terms.
Two tiers of infrastructure serve requests: Edge Nodes - the residential and small-business devices described above - handle most delivery, with Regional Nodes (data center capacity Evolving Edge operates directly) providing overflow capacity and failover where Edge Node coverage is still thin.
Right now the network’s focus is content delivery, as it’s the foundation for all other workloads. As AI inference and general-purpose compute workloads come online, both the node software and the platform’s customer-facing capabilities will expand to support them.
Two sides of the network
Section titled “Two sides of the network”This documentation serves two audiences, because the network has two sides:
- Node Operators contribute a device’s compute, bandwidth, and storage to the network and earn a revenue share for the workloads it serves. If that’s you, start with Why Run a Node?
- Cloud Customers deploy content or workloads onto the network for fast, hyperlocal delivery to their own end users. If that’s you, start with Why Deploy on Evolving Edge?
Both audiences share the same underlying platform concepts - MSAs, POPs, the AI orchestration layer, the open-source node agent - covered in this section and the Glossary. What differs is what you do with the network from there.