
Inventory
Every site, hall, rack, power chain, server, cloud resource, SAP and Oracle system and licence entitlement, matched across the systems that each hold a piece of it — and resolved to one customer.
How it works
Rymvard reads the systems you already run, reconciles them into one trusted ledger, computes every figure by rule — and puts AI on top that answers the questions your teams ask every week, without ever producing a number.
The ledger
Each domain lives somewhere today. Rymvard joins them from site to hall, rack, server, HANA host, VM, cloud resource, licence and contract — and every name to one customer — so one question gets one answer.

Every site, hall, rack, power chain, server, cloud resource, SAP and Oracle system and licence entitlement, matched across the systems that each hold a piece of it — and resolved to one customer.

What each kilowatt, core and gigabyte really takes — from branch circuits to server clusters and HANA hosts. The difference between sold and used.

Which workloads matter most, so capacity and recovery follow the business, not the floor plan.

Every recovery promise, mapped from the protected site to the capacity that backs it.

Which assets leave support in the next three years, and what runs on them.

Signed deals, open requests and growth, turned into a forecast per site and hall.
Every figure traceable to its source
Each one answers a question leadership asks every week, and rules compute every figure. On top, the AI makes 26 typed decisions — from “is this the same asset?” to “which next step helps most?” — each one logged, and in shadow mode until people's reviews agree with it. It never produces a number.
“Can we land 400 kW of critical load in hall B by spring, with recovery at our second site?”
Answers by rule with a placement, the recovery landing and alternatives. A quote holds the capacity while the customer decides; bulk placement takes many requests at once.
“When does each site run out, and what should we build first?”
Contracts and the weighted pipeline per site and quarter: the first short quarter, the limit that binds first and the odds of running short.
“Is every recovery commitment backed by real capacity today?”
Continuous reconciliation of commitments against reservations; orphans and gaps are flagged as they appear.
“Where is capacity sold but idle, or powered but unusable?”
Joins allocation, measured draw and hall constraints, and suggests right-sizing at renewal.
“Which assets leave support in the next three years, and what runs on them?”
Refresh cohorts by site and criticality, so emergency replacements become planned ones.
“Do we need to buy this now?”
Idle units of the same model at every site are counted first; move, reuse or buy comes as advice, never as an order.
“What does this cluster need in Oracle processors, SQL Server cores or PVUs — and what if the VM moves?”
Each vendor counted by the rules and entitlements you enter, next to the capacity it runs on; unknown stays unknown, and placement names the new licences a host would need. Counts, never prices.
Fits your stack
Rymvard connects through standard interfaces, read-only connectors and CSV templates — no rip-and-replace, no big-bang migration.