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.
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.
A private cloud is a project.
Businesses trust their own hardware. Running it like a cloud takes a team.
Your hardware is already trusted.
It just needs to work like a cloud.
Install an app. Now you have a cloud.
- 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 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.
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.
A hospital runs its own cloud.
Two hundred servers and no cloud team. Each step lights the part of the network it runs on.
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.
1contract nightly_imaging {2 // runs only on the hospital’s own machines3 image = "stmarys/dicom-batch:2"4 gpu = "a40"5 memory = "96 GB"67 network = none8 where = net("st-marys")9 bill_to = team("radiology")1011 overflow = off // or public(20) for a busy week12}
xe · st-marys-it
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.
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.