The arrangement
Two counterparties who cannot reach each other.
Power sits where nobody will build. Compute needs capacity now. Nawa signs with both and carries the deployment between them.
Who this is for
Find your side.
-
You hold power
Idle capacity earns nothing.
A service sits under-drawn, or generation gets curtailed because the lines out are full. The capacity is real and it earns nothing while it waits.
Nawa places a load on it. The units arrive built. The site provides power, a pad, and a fibre path, and carries no construction and no capital.
Tell us what your service carriesWhat the arrangement gives you
- A hosting fee per kilowatt-month against capacity made available
- Each deployment held in its own entity, so one site carries no other site risk
- Electricity passes through at tariff, and the supplier stays outside the deal
- No build obligation, and no construction risk on the site owner
What Nawa needs to start
- The service capacity and the tariff it sits on
- Whether the agreement permits an added load of this size
- Land for a pad, and a route a permit load can reach
- Fibre at the property, or the nearest path to it
-
You need compute
Capacity where the power already is.
Queues for large loads run years in the markets everyone is bidding into. A compliance date or a launch does not move to match a queue position.
Nawa deploys against services that already exist. The configuration follows what a site holds, and the schedule follows freight and civils.
Tell us what you need to runWhat the arrangement gives you
- A term commitment, with firm capacity covering the fixed cost of the deployment
- Nawa on the contract, holding the site and hardware agreements behind it
- A stated redundancy model, and a bounded service obligation
- Deployment inside a named jurisdiction, where data residency requires one
What Nawa needs to start
- The capacity you want to reach, and by when
- Jurisdiction, and any residency constraint on where it can sit
- Workload shape, since inference and training want different sites
- Whether you bring silicon or want it sourced
-
You own silicon
An idle accelerator is a melting asset.
Accelerators lose a large share of their value across three years. Every month one sits unpowered, a slice of that value goes with no work done against it.
Nawa gives the hardware a powered home and operates it. Title stays with the owner, and the arrangement is a fee for hosting and operation.
Tell us what you are holdingWhat the arrangement gives you
- Title stays with the owner throughout
- A fee for hosting and operation, with no transfer of ownership
- Racks integrated and tested before they ship
- Metering at the service entrance and again at rack distribution
What Nawa needs to start
- What the fleet is, and how much of it is unpowered
- Where it sits today, and what moving it involves
- Power and thermal envelope per rack
- How long you want it placed
Structure
How the deal is put together.
Structure is public here. Price and term stay in the contract.
- 01
Nawa signs both sides
The site agreement and the capacity agreement both carry the Nawa name. Neither counterparty contracts with the other, and neither takes the other as credit risk.
- 02
Every obligation has a mirror
What Nawa promises on one side is held against a matching commitment on the other. A capacity obligation is written against secured power, and a hosting fee is written against a signed offtake.
- 03
One entity per deployment
Each site sits in its own vehicle. A problem at one deployment stays there. It reaches no other counterparty and no other lender.
- 04
Electricity passes through
Power is billed at tariff and passes to the offtaker. Nawa takes no position on the price of electricity and no margin on it.
- 05
What Nawa earns
Origination, integration, operation, and a carry on the deployment. The company holds no debt against the fleet, takes no title to silicon it did not buy, and signs no uncapped service obligation.
Next