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
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.
“Hosting providers lose money in the gaps between their data centers, their cloud bills and their licence audits. Rymvard closes those gaps. It reads an estate as it is — read-only, nothing to migrate — and shows what is used, what is paid for and what is licensed.”
For business leaders
Capacity turned into sentences, prices and dates — every figure traceable to its source.

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.
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. Alerts reach Teams, Slack, e-mail, PagerDuty or Opsgenie — and on-call incidents close by themselves.
Check a request against power, cooling, space and recovery in one step, try it as a scenario, then turn it into an offer that holds the capacity for up to 30 days — won, it becomes the contract. Every hold is counted once, so two offers can never sell the same kilowatt.
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.
Sold-but-idle and powered-but-uncoolable capacity, idle servers and over-stated nameplates are named with their value. A refresh plan dates each end-of-life cohort with its cost and the kilowatts it frees.
EED and German EnEfG figures from metered months, CUE where you set a grid factor, and draft statements per customer from meters and versioned tariffs that reconcile with your ERP — the invoice stays yours.


Every workspace home — and Overview, Runway and Halls — opens with two bars. Physical: the measured peak against what is commissioned. Allocatable: what is left after recovery reserves, contracts, held quotes and power without cooling. What remains is what you can really sell.
A customer signs in to a tenant view of their own contracts, recovery coverage and test status, energy statements, draft billing lines and the compute their workloads use — never another customer's.

Per cluster: servers with their support status, vCPU, RAM, storage and GPUs — what is installed, what you can still promise after the failover reserve, and how many compute units are free per profile, with the resource that runs out first. Holds in compute units reserve it until the deal closes.
People and AI agents propose a change — a hold, a release, an incident. A second person approves exactly that change, and it runs once. Licences, runway per resource and right-sizing advice come with the same numbers.

For SAP hosting: per HANA host the OS reserve, what each system may take and really uses, what is held for system replication — and what is free for the next system. A new system, by size or by profile S, M, L or XL, gets a host with room and a partner host for its replica; administrators get a billing basis per customer in weighted HANA hosts — counts, not prices.
SAP basis, hosting sales, customer management, capacity planning and resilience each open on their own figures — what still fits by profile, the weighted pipeline, every customer's protection, the S/4HANA wave and every takeover. Customer names stay with planners; SAP findings never name a customer.
Every replicated pair is checked: can the secondary host carry the production system after a takeover, once the test systems on it stop? Read-only from the SAP Host Agent, the HANA monitoring views and your landscape tools — Focused Run, ServiceNow, LaMa and Solution Manager. Where they disagree, a ranking you set decides.

Oracle processors and middleware, SQL Server and Windows Server cores, Broadcom per-core subscriptions, Red Hat and SUSE subscriptions and IBM PVUs — counted by the rules and entitlements you enter, next to the capacity they run on. Counts, never prices.
Database and Oracle placement name the new processor licences a host would need; the monthly SPLA and provider reports come from nightly records, and a missing night is named, not guessed.

The customer registry holds each customer with its aliases and a tree of business groups; every row that names a customer resolves to it, and billing and energy statements count it once. A name nobody knows waits as an unconfirmed customer.
AWS, Azure, Google Cloud, OCI and OpenStack — sovereign partitions included — and on-prem sources discovered with their identities; tag rules give each resource its customer, business group and contract, and an ambiguous identity is quarantined, never merged by a guess.
Workspaces
Sales, finance, the NOC, the board and the teams of every solution — SAP, Oracle, licences and subscriptions, private cloud, databases, GPUs, recovery, sovereign cloud, platforms, hyperscaler hosting, transition and cloud commitments — each open Rymvard on their own home: their question, their figures, their findings. A solution's homes appear once the ledger holds its data. Underneath, the numbers are the same for everyone.

An admin gives each person a default workspace, or your identity provider does through SCIM. Its home answers the team's question with its own figures and only the findings that concern it — the rest of the ledger stays one click away.
A workspace only hides pages; it never grants access. Money is for admins: everyone else sees the same home without the euros, and a note says so.
What changed for your team — new and resolved findings, edits to the records you care about — phrased in a few sentences, every number checked.
Each number on a home explains itself: how it is computed and where it comes from, in plain words.
The rules list the open findings; the AI picks the one that helps most. One click turns it into a proposal that a person approves — accepting or dismissing teaches the AI.
Energy invoices, capacity requests and switchover test reports are read in. Rules find every value in the document; the AI only picks among them; you confirm.


For technical teams
Standard protocols in, standard interfaces out, and the method printed next to every calculation.

A Rust collector per site reads Redfish, SNMP v2c/v3, Modbus TCP and BACnet/IP — and, for SAP, the Host Agent and the HANA monitoring views; for Oracle databases, Oracle REST Data Services with a fixed list of read-only queries — buffers to disk when the link drops, and ships signed batches over HTTPS or MQTT. Raw data stays where it was measured. In a customer's network a collector is bound to the sites and accounts it may write for, installed with Terraform or Helm.
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.
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. Runway per constraint shows whether power, cooling or rack positions run out first.
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.
Ask a question in plain English: the answer names the query, the sources and how many of its numbers were checked against the ledger. Engines run locally by default; Anthropic, OpenAI, OpenRouter or your Codex subscription only on your opt-in, with customer names pseudonymised — and each engine earns its own track record in shadow mode.
REST and MCP for agents, OIDC single sign-on and SCIM provisioning. Read-only connectors for NetBox, openDCIM, vCenter, Proxmox, Prometheus (Kubernetes, vSphere, NVIDIA DCGM), DCIM, CMDB and CRM — for SAP landscapes Focused Run, ServiceNow with SAP options, LaMa and Solution Manager — and Oracle Enterprise Manager. ServiceNow incidents on opt-in, Docker install on any Linux, the interface in English with a German switch, a handbook in seven languages — and an export in the same templates, no lock-in.
Contracts, recovery reservations and holds are claims on a resource in its own unit — kW, cross-connects, Gbps, vCPU, GiB, GPU — for a time window. A new claim is checked under lock against everything that overlaps, so parallel deals cannot oversell.
Power and liquid-cooling paths are traced from each rack to the utility. Shared UPS, chillers and failure domains are named, and the surviving path must carry the load at its derated rating. A missing rating makes the verdict unknown, never green.
The collector reads each server's Redfish inventory — CPUs, cores, threads, memory, drives, GPUs, BIOS and BMC firmware. vCenter, Proxmox, Kubernetes and NetBox add clusters and workloads, read-only. Where a declared value disagrees with the hardware, you decide.
A snapshot freezes a calculation's inputs and result with SHA-256 and replays them later. Background jobs run on one worker at a time with fencing tokens. Each nightly backup is copied to a second machine, its SHA-256 compared at the target and kept 30 days — a failed copy, or one older than 26 hours, is named on the Operations page — and a restore drill brings a backup up in isolation and measures how long it takes.
New in 0.28 · Enterprise access
Scopes, tenant views and sessions are enforced where the data is — so one ledger can serve many customers and many teams without showing everything to everyone.
A staff user can be limited to customers, business groups or sites — enforced by the database's row-level security, not just the screen. Everyone sees their own scope on My scope.
SCIM groups map to scopes; a user that SCIM creates sees nothing until an admin or a group mapping gives it a scope.
A customer's tenant view can be pinned to one business group; a value that names another customer is hidden whole.
Signing out ends every session; an admin can sign a user out everywhere, and a role change or a deactivation ends a user's sessions at once.


Start with one site: your inventory, your meters, your commitments.