RYMVARD

SAP and HANA hosting

Every HANA gigabyte.Every takeover, checked.

For SAP hosting providers and their SAP teams — basis, sales, customer management, capacity planning and resilience: Rymvard shows the memory of every HANA host, checks every system-replication takeover and plans room for the next go-live — in the same ledger as power, racks and compute.

Read-only. The screens show a simulated landscape of 200 HANA hosts — not a customer.

Memory, not megawatts, decides.

An SAP hosting estate rarely runs out of power first. It runs out of HANA memory — on the wrong host, at the wrong site, in the quarter a customer goes live. And the one moment that matters most, a takeover, is the one nobody has tried.

Memory, not megawatts.

A HANA host is full long before its power is: the operating system takes its share, every system reserves an allocation limit, and replicas wait for a takeover. Rymvard counts all of it, host by host.

A takeover nobody has tried.

System replication looks healthy until the day it is needed — and the secondary host turns out to be filled with test systems. Rymvard checks every replicated system before that day.

The S/4HANA wave.

SAP ECC leaves mainstream maintenance at the end of 2027. Every move to S/4HANA needs HANA memory, often twice for a while. Rymvard names the systems whose maintenance ends in the next 24 months, the memory their double run needs, and sets planned go-lives against the memory that is really free.

What Rymvard shows

One view of every HANA host.

The same numbers for the five SAP teams and the board — each traceable to the host, the system and the moment it was observed.

Rymvard's SAP and HANA view: memory per HANA host split into OS reserve, used, allocated, held for replication and free, with an overbooked host flagged
Memory per HANA host — and the takeover check for every replicated system.

Memory per host.

Operating-system reserve, used (thirty-day peak), allocated but unused, held for replicas and free — for every HANA host, every site and the whole estate. Allocations beyond physical memory are shown, never hidden.

A takeover check per system.

Can the secondary host carry production after a takeover, once the test systems that may stop have stopped? Fits, fits after stopping, does not fit — or unknown when a figure is stale.

Placement and runway.

A new system gets the host with the best fit and a partner host for its replica. Planned go-lives, weighted by their probability, become a memory runway per site and quarter.

Customers kept apart.

System IDs repeat across customers. Rymvard keys every system by ID, site and customer, shows each customer's share and mirrors HANA into the compute view for showback and lifecycle.

Since version 0.24

Ready for your landscape.

What a pilot on a real SAP estate needs: sizes your sales team sells, the names your systems run under, one answer where sources disagree — and a basis for your own billing.

Rymvard's SAP and HANA placement: a new HANA system of profile L at one site with a replica partner host at the second site, and below it how many more systems of each profile still fit per site
Where does a new HANA system fit? Profile L with a replica partner at the second site — and “Free by profile” below.

Free by profile.

How many more systems of each size still fit per site — S, M, L and XL (256, 512, 1,024 and 2,048 GiB by default, or your own sizes), placed one by one on the best-fitting host. A new system can be placed by profile, with a partner host for its replica at the other site.

Virtual host names.

SAP systems run under virtual names. Rymvard maps each name to its physical host and learns new ones from the SAP Host Agent. A failover moves the name — it never deletes the system's memory and replication history.

Where sources disagree, a ranking you set decides.

For each SAP system's environment, customer, kind, product and version, a ranking per field decides which source wins — your CSV, Focused Run, HANA itself — or a person decides on the Conflicts page, once.

A billing basis per customer.

For administrators: weighted HANA hosts per customer and month — a host with four sockets or 2 TiB counts three, a host of unknown size is named instead of guessed, a shared host is split by allocation limits — recorded every night and exported as CSV. Counts for your own billing, not prices.

Read-only, from the systems you run.

Rymvard never writes to SAP. A small collector at each site reads what your landscape already knows and keeps it current.

  • SAP Host Agent — instances and hosts, over HTTPS, with read operations only; the collector refuses anything else.
  • HANA monitoring views — memory, replication and tenant databases from a short, fixed list of read-only queries, with a monitoring user over TLS.
  • Landscape tools — SAP Focused Run, ServiceNow, SAP LaMa and SAP Solution Manager — for systems, customers and environments.
  • Detailed records stay in their country; customer names are visible only to the people who need them.

Since 0.25 · Workspaces

Five homes for SAP teams.

SAP basis, hosting sales, customer management, capacity planning and resilience each open Rymvard on their own home — their question, their figures and only the findings that concern them, with AI that explains every number and suggests the next step. SAP findings never name a customer. See the workspaces

Rymvard's SAP Operations home: the HANA memory overview on top, then free HANA memory, production systems without replication, takeovers that would fail and hosts over 90 %
SAP Operations — for SAP basis.

SAP Operations

Does every SAP system have room and a working replica?

  • HANA memory free
  • PRD systems without replication
  • Takeovers that would fail
  • HANA hosts over 90 %
Rymvard's SAP Sales & Pre-Sales home: the HANA memory overview and its four figures — XL systems that still fit, HANA memory short from, Weighted SAP pipeline, next 4 quarters, HANA memory free
SAP Sales & Pre-Sales

SAP Sales & Pre-Sales

Which HANA system can I offer, where — and from when?

  • XL systems that still fit
  • HANA memory short from
  • Weighted SAP pipeline, next 4 quarters
  • HANA memory free
Rymvard's SAP Customer Management home: the HANA memory overview and its four figures — SAP customers, Customers with PRD unreplicated, Customers with a failing takeover, Systems leaving maintenance within 24 months
SAP Customer Management

SAP Customer Management

Is every customer's SAP landscape protected and on track?

  • SAP customers
  • Customers with PRD unreplicated
  • Customers with a failing takeover
  • Systems leaving maintenance within 24 months
Rymvard's SAP Capacity & S/4 Wave home: the HANA memory overview and its four figures — HANA memory short from, HANA memory free after planned demand, HANA systems leaving maintenance within 24 months, Memory for the double run
SAP Capacity & S/4 Wave

SAP Capacity & S/4 Wave

When does HANA memory run short, and which migrations land when?

  • HANA memory short from
  • HANA memory free after planned demand
  • HANA systems leaving maintenance within 24 months
  • Memory for the double run
Rymvard's SAP Resilience & DR home: the HANA memory overview and its four figures — Takeovers that would fail, Takeovers unknown, Replication links in error or stale, PRD systems without replication
SAP Resilience & DR

SAP Resilience & DR

Will every takeover work today — and can we prove it?

  • Takeovers that would fail
  • Takeovers unknown
  • Replication links in error or stale
  • PRD systems without replication

Screens from the running product on its example SAP landscape. Customer names appear only for planners and admins — SAP findings never name a customer.

The SAP pilot

Four weeks, one landscape.

One landscape, one or two sites, read-only: nothing is installed on your SAP hosts, and nothing in SAP changes. After four weeks you decide on figures from your own estate, not on a demo. Ask about a pilot

  • Week 1 · ConnectRead-only users, one collector per site, the first inventory from the SAP Host Agent or a CSV.
  • Week 2 · CompleteHANA memory and replication; customers and environments from your landscape tools; virtual host names settled.
  • Week 3 · UseBasis, sales, customer management and planning work on their own SAP homes and answer real placement requests with host and replica partner.
  • Week 4 · DecideA findings report against the agreed success criteria. You decide: continue — or everything is removed.

Europe and Asia-Pacific

Four SAP hosting scenarios.

The S/4HANA wave in Frankfurt, a DORA resilience test in Luxembourg, scarce power in Singapore and in-country SAP in Mumbai.

Frankfurt

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.

Read the scenario →

Luxembourg

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.

Read the scenario →

Singapore

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.

Read the scenario →

Mumbai

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.

Read the scenario →

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.

Start with a four-week pilot.

One SAP landscape, read-only: what is really free, reserved and at risk on every HANA host — and in week four, your decision.

Write to contact@rymvard.com