Partners
Carry ADAPT into the accounts you already serve.
For an integrator, an OEM or a reseller deciding whether ADAPT is a line worth carrying: what it is, whose conversation it lands in, who answers what, and how the first account starts.
What you would carry
A licence to software on accelerators your customer owns.
Measured at up to 21% less GPU die power on NVIDIA H100 NVL, over a continuous 48 hour window, with managed and baseline arms under an equal power cap. Throughput did not change in the run.
A per-GPU runtime, software only, that installs on the host beside the driver and changes how the accelerator draws power while the customer's work runs.
It attaches to a sale that is already happening: an NVIDIA-based system going into an account, or an installed base already running in one.
What it installs, what privilege it takes and what it touches are written for your customer's own reviewer in the security review.
The asset behind the licence is the method. Filed as a UK application and its divisional, a Taiwan filing, and an international application published as WO 2026/167363, opening the national phase.
The conversation it lands in
A customer whose power is already the binding constraint.
Either a deployment will not fit the power the site has, or a running fleet has to get more work out of the same megawatts.
Headroom inside a fixed power envelope, sized on their own inputs with the headroom instrument.
A bursty fleet whose owner runs the accelerators. A saturated fleet goes to a grid flexibility conversation, and a fleet whose tenants own the accelerators starts with the tenant; name either in the first message and we set out the route.
The platform vendor
Where this sits with the platform.
ADAPT complements the platform. It steers power through the vendor's own interface, the one your customer's own tools already use, and it asks the platform for nothing that is not published.
Tell us which vendor programmes you sell under in the first message, and the route is set to fit them.
What ATHLAZ puts behind you
Evidence an engineer can check, and a document a reviewer can file.
A continuous 48 hour paired run on NVIDIA H100 NVL, under an equal power cap, inside 118 days of testing, with signed per GPU records and the method written out in full. Your customer's first engagement repeats the same paired design on their fleet.
What installs, what it listens on, what it reads and keeps, who changes an operating point and how it comes off. It is written to be forwarded without us in the room.
Who answers what
A boundary of subjects, settled before the first account.
ATHLAZ supplies the runtime and its updates. The questions divide by subject, so every one has an owner.
ATHLAZ answers
- A defect in the runtime.
- What it writes, and through which interface.
- What a log line or a published metric means.
- The removal procedure.
- The measurement and its method.
The answer comes from the people who built it, through the contact route with the partner option selected.
You answer
- Your customer's host, driver and platform tooling.
- The operation of their fleet.
- Their service commitment, and your own services.
- First contact with your customer.
Your customer controls
- Stopping the service, which releases the clocks.
- The platform vendor's own clock-reset commands, which work after a stop with nothing of ours in the path.
- Their power contract, their tariff and their accounting treatment.
- Accounts you introduce
- An account you introduce in writing is recorded as yours, and we acknowledge it in writing. How it is worked is agreed together before ATHLAZ speaks to the customer.
Terms
The shape is agreed with each partner, in writing.
Two routes are open today. How a licence itself is structured is set out on the licensing page.
A named line in your catalogue
ADAPT is carried under its own name, as a line you offer to your own customers.
An introduction
ATHLAZ contracts directly with your customer, and your part in the account is recorded in writing first.
How a partnership starts
Four steps, in this order.
Each step is small, and each settles what the next one needs.
Your onboarding
Tell us what your onboarding requires, in writing, before a line like this can be carried. That answer decides the route.
One account
Choose one account where power is the binding constraint and the customer owns the accelerators, then run the headroom instrument on their numbers.
The first engagement
The three week validation on your customer's own fleet: a baseline, a paired evaluation and a report they keep.
For your own prospects
Put the instrument on your site.
Requests your visitors send from it arrive at ATHLAZ with your name on them.
<div data-athlaz-headroom data-partner="your-company" data-campaign="your-campaign"></div>
<script src="https://www.athlaz.com/embed.js" async></script>Start the conversation
Tell us what your onboarding requires and which account you have in mind.
We will set out the route that fits.