TL;DR
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
Rymvard released early-access 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. Its reported test used a simulated landscape of 200 hosts and 161 systems; the company has not provided customer deployment results.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger, as discussed in the original analysis. The early-access software is intended for SAP hosting providers and operations teams, but the company’s reported test results came from a simulated landscape, not a customer deployment.
The release tracks memory across each HANA host, separating the operating-system reserve, HANA system usage, allocated but unused memory, replica reservations and remaining free capacity. Rymvard’s default operating-system reserve is 10 percent of the first 64 GiB and 3 percent of memory above that, unless a host is configured with a different reserve. System usage is based on its 30-day peak. If allocations exceed physical memory, the ledger labels the host as overbooked instead of presenting a negative free-capacity figure.
For systems using SAP HANA system replication, the software checks whether the secondary host could accommodate the primary system’s allocation after a takeover. It reports whether the allocation fits, fits after named systems are stopped, falls short by a stated number of GiB, or cannot be assessed. Named test or development systems may count as stoppable; production systems belonging to other customers do not. A replication status more than an hour old or a memory reading more than 24 hours old results in an unknown outcome, not a passing check. Scale-out systems are evaluated as a whole using the weakest host pair.
Rymvard also added proposals for placing a new HANA system on a host and replication-site partner, plus estimates of memory runway by site and quarter. Those estimates draw on planned go-lives weighted by probability. A new SAP Operations workspace displays indicators for free HANA memory, production systems without replication, takeovers that would fail and hosts above 90 percent utilization. Rymvard says HANA instances are mirrored into its compute view so SAP memory can appear in customer showback and lifecycle planning.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Where HANA Failover Capacity Falls Short
The release focuses on a specific planning issue for infrastructure providers: available data center capacity does not necessarily mean available HANA memory. A facility may have room in its broader infrastructure while an individual HANA host, or a replication partner expected to take over, lacks memory for an allocation. Separating overbooking from free capacity and showing a takeover shortfall could help operations teams identify that constraint before a new system is placed or a failover is needed.
The value of these views depends on the quality and freshness of the information feeding them. Rymvard’s rule that stale readings produce an unknown result avoids treating old data as evidence that capacity is available. Placement proposals and quarterly runway estimates may help teams compare expected deployments across sites, but the release material does not establish cost savings, improved reliability or customer outcomes. The features describe planning checks, not proof that a real-world deployment will meet a particular service or availability target.
As an affiliate, we earn on qualifying purchases.
How Rymvard Connects to SAP
Rymvard says its collector contacts SAP Host Agent over HTTPS and is limited 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 the software does not write to SAP.
The release also lists read-only connections to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa for system, customer and environment information. Rymvard describes these as supported sources; it does not say that customers must use all of them together. For version 0.23, the company reports testing against a simulated estate of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it identified one production system without replication, one takeover short by 512 GiB, one host overbooked by 128 GiB and one replication in an error state. Rymvard says the screens use an illustrative estate, not a customer environment.
“Nothing is ever written to SAP.”
— Rymvard
data center capacity planning software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Live Customer Results Remain Unreported
Rymvard describes version 0.23 as early access and has not identified a customer deployment or provided customer results for the release. The simulated test shows how the company says the checks behaved under one scenario; it does not establish performance across live customer landscapes, unusual SAP configurations or workloads that change over time.
The release describes the connector limits and data-age thresholds, but does not provide independent validation, detailed results from customer environments or a full account of how the product handles every possible SAP configuration. The company has not published pricing, saying terms are arranged with early-access partners. A broader availability date and named customer deployments have not been announced.
As an affiliate, we earn on qualifying purchases.
Early-Access Evaluations Ahead
The next stated step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. Those evaluations could provide information about how the memory ledger and takeover checks work with live SAP landscapes, but the company has not published an evaluation schedule or reported any completed customer trials.
Rymvard has not announced a public price list or a date for broader availability. Until it provides customer deployment evidence or further release details, version 0.23’s documented capabilities and simulated test results are the available basis for judging the update.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-memory accounting, system placement proposals and replication takeover checks to its data center capacity ledger, along with a SAP Operations workspace.
Was version 0.23 tested in a customer environment?
No customer deployment is identified in the release material. Rymvard reports testing against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.
How does the software handle old capacity data?
Rymvard says a replication status more than an hour old or a memory figure more than 24 hours old produces an unknown takeover result rather than a passing result.
Does the software write to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.”
When will Rymvard 0.23 become generally available?
The company has not announced a broader availability date. The stated next step is evaluation by early-access partners, with pricing arranged directly with Rymvard.
Primary source: Rymvard · via ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
