Open ecosystem · no lock-in, by interface
Your servers, your choice — enforced by open interfaces, not promises.
ORv3 REV 1.0 · 2024-04UQD · OCP SPECPG25 · POST-PFAS
The cabinet speaks the interfaces the rest of the industry converged on for AI racks. Anything that speaks them too, fits — this year’s H100 nodes, 2027’s whatever-wins nodes, mixed vendors in one cabinet.
Interface ledger
What "open" concretely means here
| Interface | Standard | What it guarantees you |
|---|---|---|
| ORv3 | OCP ORv3 Rev 1.0 · 2024-04 | Trays mate on insertion; the rack interface is specified in public, not by one vendor’s parts book |
| UQD | UQD · OCP | Self-sealing both halves — the same couplings hyperscale AI racks use; multi-vendor sourcing |
| PG25 | PG25 · H₂O/glycol | Cheap, non-flammable, outside PFAS regulation — no dependence on the discontinued fluorinated-fluid era |
| Telemetry | Alarms + export | Loop temperature/pressure, leak status — visible to your NOC, not just ours |
How we verify a server fits
Send your model list. We check each against the manifold/UQD interface spec and reply in writing, per model: confirmed / needs an adapter plate / not compatible. No vague "should work".
The anti-lock-in test
Ask any cabinet vendor: "Can I rack a different OEM’s liquid-ready server in year three without your permission?" If the answer is a contract instead of an interface spec — that’s your answer.
Start with your serversUQD reference table ↗Liquid-ready server landscape ↗