What runs on XE
Every industry. One network underneath.
From CDNs in forty countries to robots paying their own chargers: what teams and agents build on XE, and which parts of the network each one uses.
XE use cases are the jobs teams, agents and machines run on the XE network. Every one is built from the same five primitives and four products.
Serving a CDN from forty countries, renting a GPU for ninety seconds, running validators on independent machines, turning a hospital’s servers into its own cloud, or letting a robot pay its own charger.
Each one is built from the same parts: five primitives (Identity, Discovery, Payment, Compute and Messaging) and four products on top of them (XE Machines, XE Contracts, XE Images and XE Nets). Every entry below says which parts it uses, what it may reach on the network, and how the work is paid for.
- Use cases in the library
- 26
- Industries
- 6
- Products, five primitives
- 4
- Locations on Edge today
- 988
Start from what
you want to do.
Every use case begins with one of five things. Pick the one closest to yours, see the part of XE that does it, and a use case that already does.
Find what you’re building.
Filter by industry or by what it’s built with. Point at a use case to see what it may reach on the network, how it’s paid and what it’s made of.
- Add a hundred CDN locationsWithout building a single rack.Contract
- Transcode video overnightThousands of idle machines, file in, file out.Contract
- Check uptime from every countryReal connections in Brazil, Nigeria, Vietnam.Contract
- Rent a GPU by the secondThe whole card, root access, no quota.Live
- Deploy anything in one clickChecked images, no account.Live
- Vision models near the fleetSmall GPUs, in the cities your robots drive in.Contract
- Machines that pay machinesCharging, handoffs, access, per use.Emerging
- Firmware over the CDNUpdates delivered from the nearest machine.Contract
- Robot identity and reputationEvery robot, its own account and history.Emerging
- Encrypted storage near the robotsTerabytes of sensor data, kept close.Contract
- Serve a fine-tuned modelOne click, for a model no API serves.Contract
- Fine-tune without a quota40 hours of training, paid for 40 hours.Contract
- Agents that pay per callFractions of a cent, settled in under a second.Emerging
- Agent-to-agent communicationEncrypted, with no platform in the middle.Emerging
- Agents that rent their own computeFind a machine, pay for it, run.Emerging
- Pay per second of workEscrow that releases as the work happens.Live
- Agents that pay per callFractions of a cent, settled in under a second.Emerging
- Machines that pay machinesCharging, handoffs, access, per use.Emerging
- Bill every team for what it ranUsage billing inside your own net.Contract
- Buy compute at a fixed pricePay in XE, priced in compute units.Live
A CDN publishes a contract and adds a hundred locations in the countries it chooses. Machine owners there opt in and are paid per second.
- Reaches
- Behind the XE gateway
- Paid
- Per second, from escrow
- Built with
- DiscoveryPaymentXE Contracts
Every use case,
the same parts.
Live, contract or emerging.
Every use case carries one of three labels. They say how far along it is, and how the work in it gets paid.
A whole cloud, already running on it.
Edge Network is a decentralised cloud built entirely on XE: CDN, compute, storage, DNS and security, served from machines owned by thousands of people. The CDN and uptime-check use cases on this page are things Edge sells today.
Use cases, answered.
What teams ask before they build on XE.
What can you build on XE?
Anything that needs machines to do work and be paid for it: CDN locations and transcoding across countries, GPU rental by the second, one-click nodes, private clouds on your own servers, and agents and robots that pay each other per call or per use. This page lists 26 of them across six industries.
Where should I start?
With the product that fits the job. XE Contracts runs one job on many machines, XE Machines gives you a whole machine, XE Images publishes a setup anyone can launch, and XE Nets turns your own servers into a cloud. Agents and machines call the primitives directly.
What do Live, Contract and Emerging mean?
Live is one of the four products, used as it is. Contract is a job built on a product today, such as a CDN or a validator set. Emerging is built on the network’s primitives directly: earlier, and still taking shape.
Is anything running on XE today?
Yes. Edge Network, a decentralised cloud, runs on XE with 5K+ machines in 988 locations, serving 3K+ paying customers with 100% uptime.
Can an agent use these without a person behind it?
Yes. An agent has its own account on XE, so it can rent a machine, take or publish a contract, and pay per call or per second with no card, login or API key borrowed from a person.
How is a use case paid for?
By the work it does. Budgets sit in escrow and are released per second as the work happens, or paid per call and per use between accounts. Moving value costs nothing, and payments are final in 300ms.
Is it safe to run work on someone else’s machine?
Every job declares what it may reach, and a machine only takes the jobs its owner allows. Contracts and images are checked before an owner ever sees them, and private data is encrypted so the owner can’t read it.