SOLUTIONS · ENTERPRISE & RESEARCH

Your hardware, turned into a cloud.

Your cloud, on hardware you trust.

Businesses trust their own hardware. XE turns it into a cloud, and opens the doors when you want them open.

XE FOR ENTERPRISE

A private cloud, without the private cloud project. Install the app on each server, enrol it with your key, and you have storage, identity, scheduling and billing on machines you already own. Nothing leaves the building unless you decide it should.

THE PROBLEM

A private cloud is a project.

Businesses trust their own hardware. Running it like a cloud takes a team.

Today
Too complex to runOpenStack proved the demand, and was too complex for most to operate.
On XE
On hardware you trustYour servers, yours or rented, enrolled in minutes. No special chips.
Today
Rebuilding S3 by handTeams leaving AWS rebuild storage and scheduling themselves.
On XE
Only your key schedules workEvery machine enrols with your key, and nobody else can run on it.
Today
Billing by spreadsheetOne shared GPU cluster, and no fair way to charge each department.
On XE
Billing built inEvery team is billed for exactly what it runs.
Today
Data that can’t leaveHospitals and labs can’t move their data to someone else’s cloud.
On XE
Open the doors when you wantPublish services to the network, or pull public capacity in.

Your hardware is already trusted. It just needs to work like a cloud.

ENTERPRISE ON XE

Install an app. Now you have a cloud.

Storage, identity, scheduling and billing on the machines you already own, with public capacity one switch away.

  • Built for · 01Hospitals and healthRun your own cloud where the data already lives.
  • Built for · 02Universities and labsShare one GPU cluster, billed department by department.
  • Built for · 03Teams leaving public cloudStorage and scheduling, without rebuilding them by hand.
WHAT YOU CAN BUILD

What your own cloud does on XE.

Each one is built from the same products and primitives. Pick one to see what it may reach, how it’s paid and what it’s made of.

  1. Reaches
    Your own rulesYour own rules. It’s your hardware.
    Paid
    Per second, billed to each team
THREE MODES

Private by default. Open when you choose.

A net starts closed. Open it one way to take in public capacity, or the other to offer your own services to the network.

ONE JOB, END TO END

A hospital runs its own cloud.

Two hundred servers and no cloud team. Each step lights the part of the network it runs on.

Your side
Your departmentsRadiology, research, finance
Your serversOwned or rented, enrolled with your key
Products · this step needs none, it’s the network itselfPrimitivesThe network
Every account has its own chainFinal in 300ms · Zero fee · 1M+ TPS
FOR BUILDERS AND AGENTS

Jobs that stay inside your walls.

A contract can be pinned to your own net, billed to a team, and allowed to spill over to public machines only when you say so.

For builders
nightly_imaging.xeXE Contract
1contract nightly_imaging {
2 // runs only on the hospital’s own machines
3 image = "stmarys/dicom-batch:2"
4 gpu = "a40"
5 memory = "96 GB"
6
7 network = none
8 where = net("st-marys")
9 bill_to = team("radiology")
10
11 overflow = off // or public(20) for a busy week
12}
01Pinned to your net: no other key can schedule it.
02Billed to the team that ran it, by the second.
03Public capacity is off until you turn it on.
For IT
Two hundred servers, one afternoon.Create the net, enrol the machines with your key, see what each team used, and open the doors only when you choose.
WHAT YOU GET

Install one app. Get the whole cloud.

Everything teams usually rebuild by hand after leaving a public cloud comes with the app, on hardware you already trust.

Storage
On your own disksStore files and objects across your servers, without rebuilding S3 by hand.
Identity
Every machine enrolled with your keyPeople, teams and machines are accounts. Only your key admits a machine, and only your key schedules work on it.
Scheduling
Work goes where there’s roomJobs find free machines in your net, with the GPU, memory and storage they asked for.
Billing
Per team, per secondEvery department sees exactly what it ran. The cluster pays for itself fairly.
Opening up
One switch, both waysPublish services to the network, or pull public capacity in. Off until you say otherwise.
PROOF · LIVE ON XE

The same network, already at scale.

Edge Network runs on XE with 5K+ machines and 100% uptime. XE Nets runs your servers on the same network, kept private to your key until you choose otherwise.

Nodes online5K+
Paying customers3K+
Edge locations988
Network uptime100%
ShipsCDN · Compute · Storage · DNS · Shield
MachinesOwned by independent people, each an account on XE
Page