The missing layer
for hybrid computing.

Existing methods infer a model of the device and compute a correction from it, so their cost tracks the device's dimension. TrueLoop measures the residual and corrects it directly, so the maintenance loop is decoupled from the dimension of the state it maintains. Confirmed on 96 natively drifting qubits of IBM hardware: nine hours in spec, zero maintenance downtime.

Free for 90 days · no credit card
Abstract blue, cyan, and gold field
IBM HERON · HARDWARE

Hardware evidence.

96 qubitsnative drift maintained 9 h live50 / 50 CYCLES · PUBLIC CLOUD
+25.7 ptsusable output on the drifting qubits34 / 96 QUBITS · MEASURED
0 smaintenance downtimeRESIDUAL 0.27× DRIFT · 2-CYCLE LOCK
See the registered run

One layer.
Three jobs.

TrueLoop checks whether the hardware can be maintained, keeps it within tolerance, and records whether the contract held.

Explore the maintenance layer
Qualify

Know whether the interface can run.

Maintain

Keep the device inside its declared tolerance.

Prove

Close each run with a signed record.

Digital systems orchestrate.
Physical hardware computes.
TrueLoop keeps it usable.

The maintenance work stays beside the physical device, so control does not erase the reason for using analog or wave hardware in the first place.

DIGITAL HOSTApplications, logic, and orchestration
TRUELOOPLive stability contract
PHYSICAL COMPUTEAnalog and wave transforms

Time to contract

Read the evidence
TRUELOOP2 ms20 acquisitions
SCHEDULED SWEEP9.77 s97,660 acquisitions
FINITE DIFFERENCE2.78 h100,000,004 acquisitions

96 channels · 9,730 bytes per cycle · 97 µs of bus at 100 MB/s Control-plane ledger measured on IBM Heron; the projection ladder lives on the Scaling page.

One layer.
Many devices.

Designed for hardware that can read each relevant channel in parallel and correct it before the reading goes stale.

Add the layer.
Keep the application.

Connect the readout you already have. TrueLoop maintains the hardware underneath your existing workload.

Open quickstart
PYTHON / MAINTENANCE LOOPCLIENT 0.6.0
opt = StabilityContract(key, n=len(x0), mode="regulation", target=target)
x = opt.start(x0)
for _ in range(budget):
    x = opt.step(measure(x), target=target)
opt.end()

measure(x) is your existing readout. opt.state reports the live contract.

A physical device
the system can trust.

The application sees usable hardware and a clear contract state.

Application unchanged

Contract state live

Safe hold when needed

Signed record after the run

Can your hardware read and correct every relevant component in time?

Check the actual interface before you integrate.

Check compatibility