XE MACHINES

XE Machines

The whole machine, paid by the second.

Rent a CPU or GPU machine with root access, in the country you choose. Paid per second from escrow, finished the moment you disconnect.

THE MACHINE ITSELF

XE Machines lets you rent a whole CPU or GPU machine, with root access, in the country you choose, and pay for it by the second.

Not a job running on someone else’s machine: the machine itself. Owners list the hardware they have, from a single consumer card to data-centre GPUs. You pick one, fund an escrow and SSH in as root. Payment goes to the owner for every second you’re connected, and stops the moment you leave.

RootAccessThe whole machine over SSH, not a slice of one.
1sBilling incrementYou pay for the seconds you use, from escrow.
0Quotas to requestNo approval, no waitlist, no sales call.
988LocationsMachines in the countries you pick.
THE PROBLEM

A GPU shouldn’t take a quota and a sales call.

A cloud rents you a slice of its data centre, on its terms. XE rents you someone’s machine, on yours.

To get startedA typical cloudAn account, a card on file, often a quota requestXE MachinesA funded key. No account, no approval
Time to a GPUA typical cloudDays, when a quota has to be approvedXE MachinesSeconds, from the machines available now
Where it runsA typical cloudAbout thirty regions the provider choseXE MachinesThe country you choose
What you getA typical cloudA virtual machine, within the provider’s limitsXE MachinesRoot on the whole machine
BillingA typical cloudRounded up to the hour, or a monthly commitmentXE MachinesPer second, from escrow
When you stopA typical cloudForgotten instances keep billingXE MachinesDisconnect, and billing stops that second
CHOOSE A MACHINE

Pick by memory.
Pay by the second.

Every listing shows the card, memory, cores, storage, country and price per second before you rent. Owners set the price, and you see it up front.

Built on
IdentityDiscoveryPaymentComputeMessaging
Country
Card memory

Good for: image generation and LoRAs, smaller models, video encoding.

2 machines fit in Germany
  • fra-9dRTX 4090
  • fra-3aH100 80GB
BILLING

Pay for the seconds you use.

Clouds round every job up to the hour. XE Machines bill to the second, from escrow, and stop the moment you disconnect.

4m 12s
Billed by the hour1 hour
93% of the bill is time nobody used.
Billed on XE4m 12s
Every second you’re connected, and not one more. The rest of the escrow comes back to you.
ROOT ACCESS

Root means root.

You get the machine, not a managed slice of it. Everything you’d do on a server you own, you can do here, for as long as your budget lasts.

01
Install anythingDrivers, CUDA versions, kernels, your own container runtime. Nothing on the machine is off limits to you.
02
Keep it as long as you needMinutes for a test, weeks for a training run. The escrow is the only limit, and you can top it up.
03
Choose the countryPut the machine next to your data, next to your users, or inside the border your rules require.
04
Pay for delivered secondsIf a machine drops off the network, payment stops with it. Escrow only releases for work actually done.
05
See it before you rent itHardware, location, price and the owner’s record are on the listing. Nothing changes after you connect.
06
Start from an imageBoot a checked XE Image, like a model server or a node, instead of a bare operating system.
HOW A LEASE WORKS

From “I need a GPU”
to root, in seconds.

Escrow · fra-3a · 1× H100 80GB · Germany
Connected
00:00
Rate
0.00061 XE/s
Paid to the owner
0.000 XE
Held in escrow
—
TRUST

Why root is safe to hand over, and when it isn’t.

Nobody pays by the second for a GPU to send spam. The network settles every lease on attested time and measured hardware, and says plainly what it isn’t for.

What every lease is held to
Paid for delivered secondsIf a machine drops off the network, payment stops with it. Escrow only releases for work actually done.
A clock the owner can’t bendA lease’s start and end are witnessed by XE Timekeepers, independent nodes on the network, not read off the owner’s clock.
Hardware that’s been measuredEvery machine carries an XE Benchmark certificate of what it can really do, timed by those same XE Timekeepers.
An owner with something at stakeOwners lock collateral against every lease they accept, and get it back when the lease settles.
When a cloud is still the better fit
Anything with secretsThe owner of a machine can read what runs on it, as with any server you don’t own. For work that must stay on hardware you control, use XE Nets.
A server for the whole monthIf it runs every hour of every day, a plain monthly host costs less.
The lowest price per tokenXE Machines competes on access: the whole card, today, with no quota. Not on inference price.
FOR BUILDERS

Rent from a terminal, a script or a pipeline.

The CLI, the SDK and the API all do the same four things: list, rent, connect and release. A lease is a few lines in whatever you already write.

FilterBy memory, cores, country and price per second
BudgetA hard limit, held in escrow, never exceeded
EndOn release, on disconnect, or when the budget runs out
1# find a machine: 24 GB or more, in Germany, cheapest first
2xe machines list --gpu-mem 24 --country de --sort price
3
4# rent it, with a budget held in escrow
5xe machines rent fra-3a --budget 5
6
7# root, for as long as the budget lasts
8ssh root@fra-3a.xe
9
10# done: billing stops, the rest comes back
11xe machines release fra-3a
FOR AGENTS

An agent can rent its own machine.

No card, no login, no person approving it. An agent with an XE account and a budget finds a machine, pays for it by the second and hands it back when the job is done.

The budget is the ceilingEscrow can’t be overspent, so an agent can’t run up a bill nobody agreed to.
Every lease on its recordFinished jobs build the agent’s history, which machines and other agents can check.
Nothing to clickThe same API a person uses, answering in JSON, with no dashboard in the way.
Page