Inventory
Sites · racks · servers · licences
Know your capacity.Count every licence.
The capacity and licence ledger for enterprise hosting
Rymvard joins power, racks, IT compute and HANA memory with the licences of Oracle, Microsoft, VMware, Red Hat, SUSE and IBM into one ledger every team can trust — on premises, in the public cloud and in sovereign clouds — so every go-live, takeover and audit starts from the same true number. Where a VM lands decides what is owed; Rymvard shows it before it lands.
Running on an example estate · early access and SAP pilots open
Six data domains
Power & compute
Measured, not assumed
Workload criticality
Tier 0 to Tier 3
DR reservations
Who protects whom
Lifecycle
What ages out, when
Demand
What comes next
RYMVARDthe capacity and licence ledgerrymvard.com
Every record: source · owner · timestamp · confidence
Better decisions
Onboard
Can we land it — where, and when?
Protect
Every DR promise backed by capacity.
Procure
Buy on evidence, not on worry.
Reclaim
Idle capacity back to work.
Refresh
On your schedule, not in a hurry.
Connect
Start with the systems you already run — DCIM, CMDB, metering, hypervisors and Kubernetes, SAP and Oracle landscapes, licence entitlements, contracts and pipeline. Nothing to rip out.
Reconcile
Every asset, kilowatt, licence and commitment is matched into one ledger, each with its source, owner and confidence.
Decide
Ask a capacity question and get an answer you can defend. The AI recommends; a person approves.
For business leaders
Answers your board can follow.
Where the estate stands in a few sentences, what needs attention with its cost and date, whether a deal fits, which licence positions are short, and proof that every recovery promise holds.
See the business view For technical teamsNumbers your engineers can check.
Live readings over Redfish, SNMP, Modbus and BACnet; discovery in AWS, Azure, Google Cloud, OCI and OpenStack; A/B feed failover math; licences counted by the rules you enter; a change log of every write; AI that shows its work; REST and MCP for your own tools.
See the technical viewWorkspaces
Forty-four teams. One ledger.
Sales, finance, facility, the NOC and the board — and the teams of SAP, Oracle, licences and subscriptions, private cloud, databases, GPUs, recovery, sovereign cloud, platforms, hyperscaler hosting, transition and cloud commitments each get their own home, with AI that explains every figure and suggests the next step. See the workspaces
- IT infrastructureWhat can the clusters still take, and what is coming?
- SalesWhat can I sell today, and does this request fit?
- ManagementWhere does the estate stand?
- FacilityDoes the infrastructure hold, and where must I go?
- C-LevelWhere do we grow, and what must we invest?
- FinanceDo we earn money, and where is money lying around?
- Capacity planningWhen does it get tight, and where?
- Account managementHow are my customers doing?
- Sustainability / ESGHow efficient and clean are we?
- Compliance & auditCan we prove it?
- NOC wallIs anything burning right now?
- ProcurementWhat must be ordered, and when?
- SAP & HANA · five homesOperations, sales, customers, capacity and the S/4 wave, resilience.
- Oracle · four homesOperations, sales, customers, upgrades and lifecycle.
- Licences & subscriptions · five homesMicrosoft and SPLA, the VMware exit, Red Hat and SUSE, IBM, Licences & Audit.
- Private cloud · four homesOperations, migration and onboarding, platform and licences, sales.
- Databases · four homesOperations, licences and audit, customers, capacity and placement.
- GPU & AI · four homesGPU operations, sales, AI facilities, customers.
- Recovery ServiceCan all customers recover together — and can we prove it?
- Cloud, platform & takeover · five homesSovereign cloud operations, platform engineering, hyperscaler hosting, transition, cloud commitments.
Confidence, not just capacity.
Most estates are not short of capacity. They are short of a number everyone believes. When the truth is spread across tools, regions and spreadsheets, every decision starts with a reconciliation — and ends with a safety margin. Rymvard ends the reconciliation.
Say yes in days, not weeks.
A capacity request no longer starts a hunt through spreadsheets. Fit-check tests space, power, cooling, criticality and recovery in one step, a quote holds the capacity while the customer decides, and your team signs off with confidence.
Prove every recovery promise.
See, site by site, which disaster-recovery commitments are backed by real, reserved capacity — and keep the evidence ready for customers and auditors.
Buy on evidence.
A forecast your teams believe replaces buying “just in case”. Hardware arrives when the ledger says it is needed, not months before.
Find the megawatts you already own.
Capacity that is sold but idle, or powered but unusable, becomes visible — and sellable again. Often the fastest new capacity is the one you have.
Refresh ahead of time.
Assets that leave support are planned three years out, grouped by site and criticality. Emergency refreshes become the exception.
One number for every team.
Sales, operations, finance, licence management and continuity planning work from the same ledger. Fewer meetings about whose spreadsheet is right.
“Every enterprise runs its infrastructure in several places at once: its own halls, two or three hyperscalers and, more and more, a sovereign cloud. Nobody has one honest ledger across all of them. Rymvard is that ledger — capacity, contracts and licences in one place, from the rack to the cloud account.”
Every kilowatt. One ledger.
Across halls, sites and borders
Use cases
Where Rymvard makes the difference.
Fourteen situations every operator knows — illustrative scenarios from thirteen cities: four in the United States, four for SAP hosting in Europe and Asia-Pacific.
Amsterdam · Colocation provider
Say yes to a two-megawatt request — this week
A prospect needs two megawatts with dual feeds next quarter. The answer used to take weeks.
Dublin · Financial services estate
Show the auditor that recovery really works
Resilience rules ask for proof that every recovery promise is backed. Rymvard keeps that proof current.
Oslo · Renewable-powered operator
Make room for the AI wave
High-density GPU requests arrive faster than new halls. Rymvard shows where they can land today.
United States
Four US markets, four hard questions.
Grid queues in Virginia, curtailment rules in Texas, desert heat in Arizona and a new utility tariff in Ohio — where a trusted capacity number pays off first.
Ashburn, Virginia · Hyperscale colocation campus
Sell megawatts while the grid catches up
New utility power in Northern Virginia can take years. The capacity you can sell this year may already sit inside your fence.
Dallas, Texas · Colocation on the ERCOT grid
Know what to shed when the grid calls
Texas now expects large loads to curtail in a grid emergency. Rymvard shows which load can go first — and what must stay on.
Phoenix, Arizona · AI campus in the desert
Plan for the hottest week of the year
At 115 °F, cooling — not power — sets the limit. Rymvard shows the headroom that is left on the hottest afternoon.
Columbus, Ohio · Enterprise and hyperscale growth market
Pay only for the power you will really use
New utility tariffs make data centers pay for most of the power they reserve. Reserve what the ledger says you need.
SAP and HANA hosting
Every HANA gigabyte. Every takeover.
For SAP hosting providers and SAP operations teams: HANA memory per host, a takeover check for every replicated system and room for the next go-live — in the same ledger as power and racks. With five homes for SAP teams and a four-week, read-only pilot on your own landscape.
Frankfurt · SAP hosting provider
Make room for the S/4HANA wave
SAP ECC leaves mainstream maintenance at the end of 2027. Every move to S/4HANA needs HANA memory — for a while, twice.
Luxembourg · Managed SAP for financial services
Prove that every SAP takeover will hold
Under DORA, banks must show that critical systems recover. For SAP that means a takeover the replica host can really carry.
Singapore · Regional SAP hosting hub
Find the HANA memory you already own
New data-center power is allocated in selective calls. The fastest new HANA capacity is memory that is reserved but never used.
Mumbai · In-country SAP hosting
Grow SAP inside the country
Payment data must stay in India. Every new SAP landscape needs in-country HANA capacity — and a plan for it.
New in 0.28 · Cloud, sovereign and takeover
Wherever the estate runs.
Public and sovereign clouds, Kubernetes platforms, the hyperscaler racks in your halls and the commitments you buy — and a takeover carried from the contract to the exit, without migrating anything first.
Cloud and sovereign cloud
Every cloud resource, owned. Every sovereign zone, checked.
Discovery across five clouds and their sovereign partitions, every resource with its owner, OpenStack zones and flavors, cloud databases, storage, SAP and licences.
Takeover without migration
Take over the estate as it is. Every step to go-live, recorded.
One customer registry, on-prem and cloud discovery, contracts with scope and billing basis, go-live checks, exit with export and purge.
Cloud commitments
Every commitment used. Or brought back in time.
Reservations, savings plans and committed-use discounts against FOCUS cost: used, unused or unknown, showback and a bring-back comparison.
Kubernetes platforms
Every namespace counted. Every idle request found.
Capacity per cluster, node pool, team and namespace: requests, limits and use — and the teams holding capacity they never use.
Hyperscaler hosting
Every hyperscaler rack. Every promise, kept.
Racks hosted for a hyperscaler against the power, cooling, space and network you promised — and a place for the next delivery.
Since 0.27 · Ecosystems
Every ecosystem. One ledger.
Oracle, Microsoft, the VMware exit, Red Hat and SUSE and IBM — licences counted by your own rules, next to the capacity they run on. Private cloud, databases, GPUs and recovery are on the solutions page.
Oracle hosting
Every Oracle processor counted. Every application, ready to recover.
Applications and databases: recovery ready per system, processors and middleware counted by your rules, upgrades and placement.
Microsoft licensing
Every core licensed. Every SPLA month reported.
SQL Server and Windows Server per core with their minimums, and the month's peak for the SPLA report.
VMware exit
Every core you must renew. Every wave that leaves before.
Cores at their minimum per CPU, the renewal date against the migration waves, staying or leaving.
Red Hat and SUSE
Every node subscribed. Every provider month reported.
RHEL, OpenShift, SLES and SLES for SAP by their own units, and the month's peak for the provider programmes.
IBM Power
Every PVU counted. Every LPAR, every quarter.
PVUs by licensable cores, LPARs as they run, full capacity unless ILMT proves less, Db2 HADR checked.
Built for sovereignty and scrutiny.
Capacity data is sensitive. Rymvard is designed so it never has to leave the place it belongs.
- A federated ledger — detailed records stay in their country; only the aggregates you allow travel.
- Runs in your own data center or your sovereign cloud.
- Every figure traceable to its source, owner, timestamp and confidence.
- Staff can be limited to customers, business groups or sites — enforced by the database, not just the screen.
- The AI recommends; a person approves every commitment.
- No data goes to a third-party AI model by default — a hosted engine only on your opt-in, with customer names pseudonymised.
Questions
Good to know.
What operators usually ask first.
Does Rymvard replace our DCIM or CMDB?
No. Rymvard sits on top of the systems you already run and joins what each of them knows into one ledger. Your DCIM stays the place where the floor is managed; Rymvard is where capacity decisions are made.
Where does our data live?
Where you decide. Rymvard is designed as a federated ledger: detailed records stay in the country and environment you choose, and only the aggregates you allow travel between sites. It runs in your own data center or your sovereign cloud. A collector can run inside a customer's network, bound to the sites and accounts it may write for.
What does the AI actually do?
It answers capacity questions from the ledger — placement, recovery, failure impact, forecasts, stranded capacity — and shows its work: which query it ran, on which sources, and that every number it wrote was checked against the ledger. Its decisions are typed, logged and reviewed, and none acts on its own until people have confirmed enough of them. By default no data goes to a third-party AI model; a hosted engine runs only if you opt in, and sees customer names only as pseudonyms.
Does Rymvard work for SAP hosting?
Yes. For SAP hosting providers and SAP operations teams, Rymvard shows HANA memory per host and how many more systems of each profile — S, M, L, XL — still fit per site, checks every system-replication takeover, places the next system with a partner host for its replica and gives administrators a billing basis per customer in weighted HANA hosts. Five homes give SAP basis, hosting sales, customer management, capacity planning and resilience their own figures; SAP findings never name a customer. It only reads — from the SAP Host Agent, the HANA monitoring views and SAP Focused Run, ServiceNow, SAP LaMa or SAP Solution Manager. See SAP and HANA hosting.
How do we get started?
With one site, one SAP landscape or one licence estate. We map the capacity and licence sources you already have, confirm what is really free, stranded, reserved and short, and build from there. For SAP hosting providers there is a four-week, read-only pilot: one landscape, one or two sites, and in week four you decide on figures from your own estate.
Does Rymvard work beyond SAP and the data center?
Yes. Since version 0.26 the same pattern serves private-cloud providers — migration and onboarding waves week by week, maintenance one host at a time, licence positions and VM packages — managed database hosting — a takeover check per replication group, licence positions from your own rules, placement with a standby partner — and GPU and AI hosting — a fit that knows models and slices, pods against power, feeds and liquid cooling, GPU use per customer. Recovery is checked across all of them. Since version 0.27 Oracle applications and databases, Microsoft, the VMware exit, Red Hat and SUSE and IBM follow as ecosystems with their licences. Since version 0.28 Rymvard follows an estate into AWS, Azure, Google Cloud, OCI and OpenStack — their sovereign partitions included — onto Kubernetes platforms and into the hyperscaler racks in your halls, and sets cloud commitments against their cost. Cloud, sovereign and takeover.
Can we take over an estate without migrating it?
Yes. Since version 0.28 Rymvard reads a customer's estate where it runs — cloud accounts in AWS, Azure, Google Cloud, OCI and OpenStack, and on premises Nutanix, Red Hat Satellite, SUSE Customer Center, IBM ILMT, Hyper-V inventories and CMDB exports — and resolves every resource to one customer in its registry. A contract carries the scope and the billing basis, a transition plan the go-live checks and baselines, an exit the export and purge. Nothing writes to the customer's systems. Takeover without migration.
Does Rymvard count licences?
Yes. Since version 0.27 Rymvard counts Oracle processors and middleware, Microsoft SQL Server and Windows Server cores with the SPLA month, Broadcom per-core subscriptions for the VMware exit, Red Hat and SUSE subscriptions and IBM PVUs — each by the rules and entitlements you enter, next to the capacity they run on, so the licences a placement needs are visible before the VM lands. Since version 0.28 the same positions include the cloud: bring-your-own-licence rules per cloud and the software declared on each cloud resource. It counts; your contract decides, and Rymvard never shows prices of its own. Licence-aware placement.
Is Rymvard available today?
Yes. Rymvard runs today: version 0.28 has been live since 14 October 2026, and the screens on this website are the running product on illustrative example data. Early access is open to operators who want to run it on their own data first and shape what comes next, and SAP hosting providers can start a four-week pilot. Write to contact@rymvard.com.
What does it cost?
Pricing will be set with the first early-access partners. Nothing on this website is an offer.
Start with one site or one estate.
We map your capacity and licence sources and show what is really free, stranded, reserved — and short.