Know where you stand in a minute.
A business view writes the estate in a few sentences — capacity, runway, recovery, money at stake. Every number links to where it comes from. A board pack prints the same facts with a fingerprint.
Product
One ledger.Two ways to read it.
Leaders need the answer and what it costs. Engineers need to check how it was reached. Rymvard shows both from the same numbers — switch between the business and the technical view at any time.
The screens below are the running product on an illustrative example estate — not a customer.
For business leaders
Decisions you can defend in the boardroom.
Capacity turned into sentences, prices and dates — every figure traceable to its source.
See what needs attention — and its price.
Findings arrive with an owner, a due date and their impact in kilowatts and euros. They close themselves when the problem is gone, so the list stays short and true.
Say yes to a deal, safely.
Check a request against power, cooling, space and recovery in one step — then try it as a scenario and see how every site's runway moves before anyone signs.
Prove every recovery promise.
Each disaster-recovery commitment is checked against capacity reserved at its recovery site, with its last switchover test. The evidence pack is one download — for auditors and for each customer.
Find the megawatts you already own.
Sold-but-idle and powered-but-uncoolable capacity, idle servers and over-stated nameplates are named with their value — the fastest capacity is often the one you have.
Report and bill on time.
EED and German EnEfG figures from metered months, CUE where you set a grid factor, and a billing export per customer that matches their energy statement.
For technical teams
Every number, open to inspection.
Standard protocols in, standard interfaces out, and the method printed next to every calculation.
Live readings, in-country.
A Rust collector per site reads Redfish, SNMP v2c/v3, Modbus TCP and BACnet/IP, buffers to disk when the link drops, and sends batches with a token. Raw data stays where it was measured.
Power math you can check.
Per rack: if feed A fails, can feed B carry the peak? Side capacity is V × A × √3 × utilisation, set against the measured 24-hour peak — the calculation is on the page.
What if a hall fails?
Pick a hall or a site: the customers and workloads it takes down, whether each recovery commitment still holds when every landing is called at once, and whose recovery capacity it takes with it.
Every write, on record.
A change log records who changed what — a person, an import file, a connector — with the values before and after. Model-versus-measured checks flag ratings, contracts and nameplates that disagree with the meters.
AI that shows its work.
Ask a question in plain English: the answer names the query, the sources and how many of its numbers were checked against the ledger. Decisions are typed and logged, and stay in shadow mode until people have confirmed enough of them.
Your tools, your data.
REST and an MCP server for agents, a catalogue generated from the code, NetBox and DCIM/CMDB connectors, import previews that write nothing, and an export in the same templates — no lock-in.
What the AI does — and does not.
- It routes questions and makes typed decisions: is this the same asset, does this reservation still serve a commitment, will this deal close?
- Every decision is logged with its inputs, confidence and the person who reviewed it.
- Decisions stay in shadow mode until at least twenty reviews agree nine times in ten.
- It never produces a number. Figures come from the ledger; a sentence the model writes is checked number by number.
- It runs locally by default — nothing leaves your environment.
See it on your own estate.
Start with one site: your inventory, your meters, your commitments.