Nothing here can be bought today.
There is no compute rental, no operator onboarding and no checkout. This page exists so that what we intend to sell is legible before it is for sale, and so that the shape of it is settled while it is still cheap to change.
The availability figures below are placeholders. The prices are not — they are the published rates from Pricing, which stays the source of truth for anything anyone could be charged.
What you can rent
Four tiers. Three you can rent, one you cannot yet.
A tier is defined by what its hardware can prove about itself, not by how fast it is. You choose a tier by choosing what you need to be true.
Attested Mobile
Android phones and tablets with hardware-backed key attestation
$0.0000 per node-hour
0 available · 0 busy
What the evidence proves
- The device is the hardware it claims to be, signed by a key the manufacturer put in silicon.
- The bootloader is locked and Android is the maker’s official build.
- Which security patch level it reports, and whether a separate secure chip signed the statement.
What it does not
The workload runs in the ordinary operating system. Nothing separates it from the rest of the phone, or from whoever holds the phone.
Measured Host
Servers, workstations and laptops with a TPM 2.0
$0.0000 per node-hour
0 available · 0 busy
What the evidence proves
- What the machine loaded at boot, measured into the TPM and quoted against a pinned vendor root.
- That the endorsement key belongs to the certificate presented with it — possession, not merely a claim.
What it does not
The person who administers the machine is an administrator on it. A measured host proves what was loaded; it does not hide the workload from its own operator.
Isolated VM
AMD SEV-SNP confidential virtual machines
$0.0000 per node-hour
0 available · 0 busy
What the evidence proves
- The workload runs in a hardware-isolated virtual machine whose memory is encrypted against the host.
- What was loaded into that machine at launch, signed by the processor itself.
What it does not
Isolation is not correctness. The code you send still does what you wrote, and a verified launch says nothing about whether that was a good idea.
Confidential GPU
UnavailableNVIDIA H100, H200, B200, HGX B300 and RTX PRO 6000 Blackwell Server Edition
Not priced
Not available to rent
What the evidence would prove
- The GPU’s own security processor signs a report about itself, checked against NVIDIA’s device identity certificate for that exact card.
- That confidential computing mode is switched on, so the host cannot read the card’s memory while your work is in it.
- That the firmware on the card matches NVIDIA’s signed reference measurements for that firmware version.
- That the CPU it is attached to is itself a confidential VM — the pairing is checked, because an attested GPU bolted to an unprotected host protects nothing.
What it does not
No consumer card can do any of this. GeForce and consumer RTX hardware has no confidential computing mode, no device identity certificate and no security processor to sign a report. That is the silicon, not our software.
Availability counts machines currently enrolled and attesting, not machines that exist somewhere. A device whose attestation has gone stale is not available, however powerful it is.
The one that is not for sale
Confidential GPU
We will sell this when we have verified one, and not before.
The verifier is written. It checks a GPU attestation report against NVIDIA’s device identity certificate and its signed reference measurements, and it refuses anything it cannot chain. What has not happened is running it against real hardware in a real datacenter and publishing what the result proves and what it leaves open.
Until that has happened there is nothing here we would be willing to charge for, and a price on this page would be a promise we had not earned.
What is missing is one afternoon on a rented H100, not a year of engineering. When that afternoon happens this tier opens and the grey comes off.
How each root is checked
How work moves
What happens after you post a job
You describe the hardware you need as a policy, not as a machine name. The coordinator finds something that satisfies it, or tells you plainly that nothing can.
- queued — Accepted and waiting. If no machine in the network could ever satisfy your policy, the job is refused here instead of waiting forever.
- placed — Matched to a machine whose evidence satisfies your policy. The decision that placed it is recorded.
- running — The machine has claimed the work and started it.
- complete — Finished. A signed evidence bundle is issued, saying what ran, on what hardware, and what that hardware proved.
A job that fails is not silently retried somewhere else. Re-running your code on another machine could repeat whatever it already did, so a failure comes back to you with the reason rather than being quietly papered over.
What you would need
To post a job, when this opens
An account and an API key
Sign in by email link; no password to lose. The key authenticates your jobs and is shown once. Every job is scoped to the account that submitted it, in the database query rather than in a filter afterwards.
API referenceA policy, and an image pinned by digest
The policy says what must be true of the hardware — boot state, isolation, security level. The image must be named by its content digest rather than a tag, because a tag can be moved under you after you asked for it.
What a bundle containsInert until the store opens. It is here so the step is legible before it is possible, which is the same reason the rest of this page exists.
What renting here does not buy.
Attestation establishes what was loaded and on what hardware. It does not establish that the code is correct, and it does not make a machine trustworthy — it makes a machine legible. Evidence can verify perfectly against a pinned root and still fail your policy. That is the system working, not a fault in it.
Read the full list of what we cannot do