Use cases

Fourteen situations.One trusted ledger.

From a two-megawatt request to an auditor's question, from a grid emergency in Texas to an SAP takeover in Luxembourg — how a single, trusted view of capacity changes the answer. Licence scenarios — Oracle, Microsoft, the VMware exit, Red Hat and SUSE, IBM — are on the solutions pages.

Read the scenarios United States SAP and HANA

Illustrative scenarios. The cities show where such estates run; they are not customer references.

AmsterdamColocation provider

DublinFinancial services estate

OsloRenewable-powered operator

SingaporeCloud and hosting provider

TorontoEnterprise hybrid estate

WarsawGrowing regional operator

“We started in the data center. Today Rymvard follows capacity and licences wherever they run: on premises, in the public cloud and in sovereign clouds.”

Thorsten Meyer, founder of Rymvard

Capacity questions have answers.

When every number can be trusted

Amsterdam · Colocation provider

Say yes to a two-megawatt request — this week

The situation: A prospect asks for two megawatts with dual power feeds, live next quarter. Sales asks operations, operations asks facilities, facilities opens three spreadsheets. Weeks later the answer is “probably”, and the prospect has been talking to others.
With Rymvard: Fit-check tests every hall at once: free and stranded power, cooling headroom, space, network and where the recovery copy would land. It proposes a placement and alternatives, a quote holds the capacity while the customer decides, and a capacity planner approves.
The outcome: A confident, documented answer while the customer is still deciding — and no risk of selling the same kilowatt twice.

Dublin · Financial services estate

Show the auditor that recovery really works

The situation: Operational-resilience rules such as DORA expect proof that critical services can recover. Recovery commitments live in contracts, runbooks and a few people's heads — and some reservations still belong to systems that were retired long ago.
With Rymvard: Rymvard maps every protected workload to the site and capacity that backs it, flags reservations that no longer serve anything and shows coverage per recovery site — continuously, not once a year.
The outcome: Gaps are closed before the audit, not after it. The evidence trail is one export away.

Oslo · Renewable-powered operator

Make room for the AI wave

The situation: Requests for high-density AI racks arrive faster than new halls can be built. The question is always the same: where can forty-kilowatt racks go today — and what has to move to make space?
With Rymvard: The ledger joins measured power, cooling limits per hall and stranded capacity. Fit-check and bulk placement show where dense racks can land, hall by hall, and the ledger shows what reclaiming idle allocations would free up.
The outcome: Dense workloads land where power and cooling allow, and the next build is sized on real demand.

Singapore · Cloud and hosting provider

Find the megawatts you already own

The situation: New power and land are hard to come by. Meanwhile the halls hold capacity that is sold but never drawn, powered but without cooling or space, and servers that have done no useful work for months.
With Rymvard: The stranded-capacity finder compares allocations with measured draw, matches power, cooling and space per hall and lists idle servers with their owners — ready for right-sizing at renewal.
The outcome: Capacity comes back into the sellable pool without a single new build, and runway is measured in quarters, not guesses.

Toronto · Enterprise hybrid estate

Stop buying “just in case”

The situation: Two data centers and a growing cloud footprint. Every team keeps a safety margin, so hardware is ordered months early — and some of it is still in boxes a year later.
With Rymvard: Every purchase request is checked against the forecast, free stock across both sites and assets due for refresh. The procurement advisor shows what is needed now and what can wait.
The outcome: Purchases follow the plan, free stock is used first, and refreshes are scheduled instead of rushed.

Warsaw · Growing regional operator

Grow a new region without guesswork

The situation: Demand in the region is growing quickly. Build too early and capital sits idle; build too late and customers go elsewhere. Today the build decision rests on a spreadsheet forecast few people trust.
With Rymvard: Demand forecasting combines the sales pipeline, onboarding requests and growth per site, and shows when each hall runs out — with and without the capacity that can be reclaimed.
The outcome: The build decision is made early, on a forecast the whole leadership team can follow.

United States

Four US data center markets.

Grid queues in Virginia, curtailment rules in Texas, desert heat in Arizona and a new utility tariff in Ohio — four American situations, four illustrative scenarios.

Ashburn, VirginiaHyperscale colocation campus

Dallas, TexasColocation on the ERCOT grid

Phoenix, ArizonaAI campus in the desert

Columbus, OhioEnterprise and hyperscale growth market

Ashburn, Virginia · Hyperscale colocation campus

Sell megawatts while the grid catches up

The situation: Demand in the world's largest data center market keeps climbing, but new utility connections take years. Every hall on the campus is sold — yet measured draw sits well below what customers reserved, and nobody can say how much of that gap is safe to offer again.
With Rymvard: The ledger compares every reservation with its measured draw over the past twelve months, applies your contractual buffer and the A/B feed failover math, and shows per hall and per feed how many kilowatts can be offered again without breaking a single commitment.
The outcome: New deals land in the halls you already run, while the next utility connection is still in the queue.

Dallas, Texas · Colocation on the ERCOT grid

Know what to shed when the grid calls

The situation: Under Texas Senate Bill 6 (2025), sites of 75 MW and more must accept curtailment when the grid operator sheds load, new sites must allow remote disconnection, and backup generation can be called on in an emergency. When the call comes, the team has minutes to decide which racks run critical services and which can wait.
With Rymvard: Every rack carries its workload criticality, its recovery copy and its power path. Rymvard ranks the load that can be shed or moved per hall, shows what generators and batteries would carry and for how long, and keeps the plan current as workloads move.
The outcome: A curtailment plan agreed with customers before the first hot week — not improvised during a grid emergency.

Phoenix, Arizona · AI campus in the desert

Plan for the hottest week of the year

The situation: Dense AI racks are arriving at a desert campus. On paper every hall has power to spare, but on the hottest afternoons the chillers run close to their limit, and some halls cannot take another forty-kilowatt rack without risk.
With Rymvard: The ledger keeps cooling capacity next to power for every hall and checks each request against last summer's peak conditions, not the yearly average. Capacity that has power but no cooling is shown as stranded — together with what it would take to free it.
The outcome: Dense racks go where they will still be cool in July, and the liquid-cooling retrofit is sized on evidence.

Columbus, Ohio · Enterprise and hyperscale growth market

Pay only for the power you will really use

The situation: In central Ohio, new data centers above 25 MW pay for at least 85 % of the power they subscribe, for up to twelve years, whether they draw it or not (AEP Ohio data center tariff, approved in 2025). Reserving power “just in case” has become a long and expensive habit.
With Rymvard: Demand forecasting joins contracted, allocated and measured power with the sales pipeline and the growth per hall. It shows how much of the contracted power is really needed year by year — and where idle allocations can be reclaimed before more is contracted.
The outcome: The next utility contract is sized on a forecast finance and operations both sign, and paid-but-unused power stops growing.

Sources for the US scenarios: Texas Senate Bill 6 (signed June 2025); Public Utilities Commission of Ohio, case 24-508-EL-ATA (order of 9 July 2025). Scenarios are illustrative; no customer, site or outcome is implied.

SAP and HANA hosting

Europe and Asia‑Pacific.

The S/4HANA wave in Frankfurt, a DORA resilience test in Luxembourg, scarce power in Singapore and in-country SAP in Mumbai — four illustrative scenarios for SAP hosting providers. SAP and HANA hosting

FrankfurtSAP hosting provider

LuxembourgManaged SAP for financial services

SingaporeRegional SAP hosting hub

MumbaiIn-country SAP hosting

Frankfurt · SAP hosting provider

Make room for the S/4HANA wave

The situation: SAP ends mainstream maintenance for ECC 6.0 at the end of 2027, with paid extended maintenance until 2030. A hosting provider's customers are moving to S/4HANA at the same time, and every move runs the old and the new system side by side for months. Sales keeps promising go-live dates; nobody can say which HANA hosts will still have memory in the quarter each customer goes live.
With Rymvard: Rymvard reads the memory of every HANA host — the operating-system reserve, what each system may take and really uses, what is held for its replica — and sets the planned go-lives, weighted by their probability, against it quarter by quarter. A new system gets a host with room and a partner host for its replica in one step.
The outcome: Go-live dates are promised on memory that is really free, and new hosts are ordered for the quarter that runs short — not after it.

Luxembourg · Managed SAP for financial services

Prove that every SAP takeover will hold

The situation: Since January 2025 the EU's Digital Operational Resilience Act expects banks and insurers to prove that their critical services recover — including those an ICT provider runs for them. The bank's SAP runs on HANA with system replication to a second site. On the replica host, test systems have quietly grown into the memory the production system would need after a takeover.
With Rymvard: For every replicated system Rymvard checks whether the secondary host can carry the primary's allocation after a takeover — after stopping the test systems that may stop, never another customer's production. A stale replication status or memory figure counts as unknown, never as fine. The result per system is one export away.
The outcome: The gap is found and closed before the resilience test, and the auditor receives a takeover result per system instead of a promise.

Singapore · Regional SAP hosting hub

Find the HANA memory you already own

The situation: New data-center capacity in Singapore is allocated through selective calls, so a provider cannot simply add a hall. Its HANA hosts look full — yet many systems reserve far more memory than they have used in months. And the banks among its customers must bring every critical system back within four hours.
With Rymvard: Rymvard compares every system's allocation limit with its peak use over thirty days, flags hosts that are overbooked or nearly full, and lists systems that use less than a tenth of what they hold. Every replicated pair keeps its takeover check, so right-sizing never eats the room a recovery needs.
The outcome: New customers land on memory reclaimed from idle systems, and every four-hour recovery stays backed by real capacity.

Mumbai · In-country SAP hosting

Grow SAP inside the country

The situation: Indian rules require payment-system data to be stored only in India, and many enterprises now want their whole SAP estate in the country. A provider is adding customers faster than hardware arrives, replicates between two sites, and plans capacity in one spreadsheet per customer — where the same system ID appears again and again.
With Rymvard: Rymvard keeps every customer's systems apart even where system IDs repeat, shows free HANA memory per site after the replicas, and turns the pipeline of planned landscapes into a runway per quarter — including the replica each one needs at the second site.
The outcome: Hardware is ordered for the quarter that runs short, every landscape lands with its replica, and each customer's share of the memory is plain to see.

Sources for the SAP and HANA scenarios: SAP, maintenance for SAP Business Suite 7 including ECC 6.0 — mainstream until the end of 2027, optional extended maintenance until the end of 2030 (announced 4 February 2020); Regulation (EU) 2022/2554 on digital operational resilience (DORA), applicable from 17 January 2025; Monetary Authority of Singapore, Notice 644 on Technology Risk Management — a recovery time objective of no more than four hours for each critical system; IMDA and EDB, Data Centre Call for Application (about 80 MW allocated in 2023, a second call from December 2025); Reserve Bank of India, Storage of Payment System Data (circular of 6 April 2018). Scenarios are illustrative; no customer, site or outcome is implied.

Recognise one of these?

Tell us about your estate — we will show what Rymvard would see.

Write to contact@rymvard.com