ONLINEBILLING:Metered every 15 min · Automatic shutdown, no idle machines · Data egress includedONLINESOURCING:Multi-cloud GPU sourcing across multiple infrastructure suppliersONLINEROUTING:Automatic provider failover on refusal or failureONLINESECURITY:Super Intelligence continuous auditONLINEPAYMENTS:x402 agent payments settling on BaseBILLING:Full-cost pre-authorization before dispatch · Data Egress: $0.00/GB
ONLINEBILLING:Metered every 15 min · Automatic shutdown, no idle machines · Data egress includedONLINESOURCING:Multi-cloud GPU sourcing across multiple infrastructure suppliersONLINEROUTING:Automatic provider failover on refusal or failureONLINESECURITY:Super Intelligence continuous auditONLINEPAYMENTS:x402 agent payments settling on BaseBILLING:Full-cost pre-authorization before dispatch · Data Egress: $0.00/GB

Sourcing & orchestration

We don't own the racks. We own the routing.

Kilawatt Cloud is an orchestration layer, not a datacenter operator. We hold no owned hardware and no power contracts. What we run is the control plane: live cost-based pricing, atomic pre-authorization, automatic provider failover, 15-minute metering and an append-only audit trail of every attempt.

Every 15 min

Usage metering

100% up front

Job pre-authorization

4

Providers in routing path

30 req/min

Default rate limit

$0.00/GB

Data egress

Append-only

Attempt ledger

The path of a job

Request to teardown

01

Quote against live provider cost

Every job is priced at request time from the real current cost of the provider that will actually run it, plus a fixed margin. No synthetic rate card is applied after the fact.

02

Pre-authorize, then dispatch

The full estimated cost is held atomically before any provider is contacted. Insufficient balance returns a 402 and nothing is provisioned. Unprofitable routes are rejected before you are charged.

03

Meter, then reclaim

Running instances are metered every 15 minutes and terminated at the provider when the paid window or the balance ends. Every attempt is written to an append-only ledger.

Where the compute comes from

Supply in the routing path

Thermal design, rack density and power efficiency are the responsibility of the underlying infrastructure that serves your job. Figures below are from our own recorded test runs, not vendor marketing.

Live supply

Every quote is checked against live stock for the exact card you asked for. A different model is never substituted; if an exact match is not available, the job fails over to another source or is declined before you are charged.

Provisioning time

Measured provisioning in our own recorded runs ranges from a few seconds to a few minutes depending on the source selected at request time.

Automatic failover

If a source refuses or fails a job, the routing layer re-places it on replacement Kilawatt infrastructure without a second charge.

One identity

Whatever source serves a job, you see one platform, one API and one bill. Machines are always presented as Kilawatt infrastructure.

Contact

Questions, quotes or support: one address, every team.

hello@kilawattcloud.dev