TL;DR
Rymvard released version 0.23 on October 4, 2026, adding SAP HANA host-memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The company says its connections to SAP are read-only, and its reported testing used a simulated estate rather than a customer deployment.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting, system-placement proposals and replication takeover checks to its data center capacity ledger, as described in the original analysis. The early-access update is aimed at SAP hosting providers and operations teams that need to track whether individual hosts and backup sites have enough memory for HANA workloads; Rymvard says the software connects through read-only interfaces and does not write to SAP.
The release divides each HANA host’s physical memory among the operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and remaining free memory, a consideration for teams assessing whether HANA memory could bottleneck an S/4HANA migration. Rymvard’s default operating-system reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host has a different reserve configured. System usage is calculated from its 30-day peak. When allocations exceed physical memory, the ledger shows overbooking rather than concealing the issue as negative free capacity.
For systems using SAP HANA system replication, the software checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It returns one of four results: fits; fits after named systems are stopped; does not fit, with the shortfall stated in GiB; or unknown. Named test or development systems may be treated as stoppable, while production systems belonging to other customers are not. A replication status older than one hour or a memory reading older than 24 hours results in an unknown status, not a passing check. Scale-out landscapes are evaluated as a whole, with the weakest host pair determining the assessment.
Version 0.23 also proposes a host and replication-site partner for a new HANA system and estimates memory runway by site and quarter using planned go-lives weighted by probability. A new SAP Operations workspace shows indicators for free HANA memory, production systems without replication, takeovers that would fail and hosts above 90% utilization. Rymvard says HANA instances are mirrored into its compute view so SAP memory can be included in customer showback and lifecycle planning.
Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Making HANA Failover Capacity Visible
For providers, the update focuses on a capacity constraint that broader data center totals can obscure: a facility may have room in its overall infrastructure while a particular HANA host or replication partner lacks the memory needed for a workload. Separating free memory, overbooking and takeover shortfalls could help operations teams identify those limits before placing a system or relying on a secondary site during a failure.
The takeover check also makes a distinction between theoretical capacity and capacity that can be used under stated operating assumptions. If a backup host can fit a workload only after specific test or development systems stop, that condition is visible in the result; production systems owned by other customers are not assumed to be available. The system’s unknown status for stale readings avoids presenting outdated information as evidence that a takeover will work.
Those are product capabilities described by Rymvard, not demonstrated customer outcomes. The release material does not establish that the checks have reduced outages, improved reliability or produced savings in operating data centers. Their practical value will depend on whether the software receives accurate, current information and represents each provider’s SAP environment correctly.
Read-Only SAP Data and Test Scope
Rymvard says its collector communicates with SAP Host Agent over HTTPS and is restricted to four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. A separate monitoring connection uses TLS and a fixed set of six SELECT queries, with a 60-second limit per system and no more than eight systems queried at once. The company says it does not write to SAP. It also lists read-only access to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa for landscape information; the release does not say customers must connect all of these sources.
Rymvard reports testing version 0.23 against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the software identified one production system without replication, a takeover short by 512 GiB, a host overbooked by 128 GiB, and one replication in an error state. The company says the displayed screens use an illustrative estate, not a customer environment, and that the examples do not imply a real customer, site or outcome.
The distinction matters when evaluating the release: the described test shows how the software reported conditions in a constructed scenario, not how it performs across live customer landscapes, unusual SAP configurations or changing workloads. Rymvard calls the product early access. The company has not named a customer deployment or provided customer results for this version.
“Nothing is ever written to SAP.”
— Rymvard
Live Customer Results Not Reported
The release does not identify a customer deployment or provide independently evaluated results from a live environment. Rymvard’s reported findings come from a simulated estate, so it remains unclear how the checks behave across real-world configurations, workload changes and provider-specific operating practices.
Rymvard has described age thresholds for classifying replication and memory data as unknown, but the release does not provide broader evidence about data quality or update performance in customer installations. It also does not state how every possible SAP configuration is handled or how integrations are validated in each environment. Pricing has not been published; the company says terms are arranged with early-access partners. A general availability date and named customers have not been announced.
Early-Access Partner Evaluations
The next step is evaluation with early-access partners, with commercial terms arranged directly with Rymvard. Those evaluations may provide evidence about how the memory ledger and takeover checks work with live SAP landscapes, but the company has not announced when results will be shared.
Rymvard has not set a date for broader availability, published a price list or named a customer using version 0.23. Until it provides deployment details or independent performance evidence, the announced functions and simulated test results are the available basis for judging the release.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-memory accounting, system-placement proposals, replication takeover checks and a workspace for monitoring selected HANA capacity indicators.
Was version 0.23 tested at a customer site?
Rymvard reports testing against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. The company says the displayed estate is illustrative and has not identified a customer deployment for this release.
What does an unknown takeover result mean?
The software reports unknown when the replication status is more than one hour old or the memory figure is more than 24 hours old. It does not treat stale data as proof that the secondary host can accommodate a takeover.
Does Rymvard write data to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release describes specific read operations and monitoring queries.
When will the software be generally available?
No broader availability date or public price list has been announced. Rymvard says the current next step is evaluation by early-access partners, with terms arranged directly with the company.
Primary source: Rymvard · via ThorstenMeyerAI.com