TL;DR
Get the latest gadgets 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 host-level SAP HANA memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The company tested the release against a simulated landscape of 200 hosts, not a customer deployment, and has not reported customer outcomes.
Rymvard released version 0.23 of its early-access data center capacity ledger on October 4, adding tools to track SAP HANA memory, propose system placements and check whether replication partners could take over a system, as described in the original analysis. The release is aimed at SAP hosting providers and operations teams, but the company’s reported test results came from a simulated estate, not a customer deployment.
The new accounting divides each HANA host’s physical memory among the operating-system reserve, HANA system use, allocated but unused memory, capacity reserved for replicas from other sites and remaining free memory. Rymvard says system usage is based on its 30-day peak. The default operating-system reserve is 10% of the first 64 GiB and 3% of memory above that amount, unless a host has a different reserve configured. Allocations exceeding physical memory are shown as overbooking rather than hidden 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 takeover. It may count named test or development systems as stoppable, but does not treat other customers’ production systems as stoppable. Results are reported as fits, fits after stopping named systems, does not fit with a shortfall in GiB, or unknown. A replication status older than one hour or a memory measurement older than 24 hours yields an unknown result. For scale-out systems, Rymvard assesses the whole system using the weakest host pair.
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 displays 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 for use in customer showback and lifecycle planning.
🔍 Read the full analysis: Rymvard Brings SAP HANA Memory Into The Data Center Capacity Ledger on Rymvard
Why HANA Memory Shapes Placement
The release addresses a specific planning problem for data center operators: a facility may have capacity in its broader infrastructure while a particular HANA host, or its replication partner, lacks the memory needed for a workload or takeover. Separating free memory, unused allocations and overbooking could help teams see that constraint before placing a system or relying on failover.
Showing whether a replica can fit after a takeover also makes recovery capacity part of routine placement planning, rather than treating replication status alone as evidence that recovery is feasible. The unknown status for stale measurements is a cautious rule: outdated data does not count as proof that capacity is available. Still, the release describes functionality, not demonstrated operational gains. Rymvard has not supplied evidence that the new views reduce costs, improve availability or prevent incidents at customer sites.
As an affiliate, we earn on qualifying purchases.
How the Ledger Gets SAP Data
Rymvard says its collector connects to the SAP Host Agent over HTTPS and uses 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 product can also read landscape details through read-only interfaces in SAP Focused Run, ServiceNow, SAP Solution Manager via its System Landscape Directory, and SAP LaMa. Rymvard names these as supported data sources; the release does not say that customers must connect all of them. The added memory view is intended to bring SAP infrastructure into the company’s wider compute-capacity ledger.
For its reported test, Rymvard used a simulated landscape with 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. The company says the displayed screens use an illustrative estate and do not represent a customer, site or real operational outcome.
“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.
What the Simulation Cannot Show
Rymvard describes version 0.23 as early access and has not identified a customer deployment or published customer outcomes. Its test results show how the software behaved in one simulated landscape, but do not establish performance across live customer environments, unusual SAP configurations or workloads that change between measurements.
The release gives age thresholds for marking replication and memory data as unknown, but does not detail how quickly readings refresh in each environment or how integrations are validated at individual sites. Rymvard has not published prices, a broader availability date or independent evaluation results. The company says early-access pricing is arranged directly with partners.
As an affiliate, we earn on qualifying purchases.
Early-Access Partner Evaluations
The next step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. The company has not announced named partners, a public price list or a date for broader availability. Evidence from live deployments, if published, would help establish how the ledger’s readings and takeover checks perform across customer environments beyond the simulated test.
Until those details are available, version 0.23’s release documents its accounting rules, connection limits and example results, while customer performance and outcomes remain unreported.
SAP HANA replication capacity tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, placement proposals, replication takeover checks and related capacity views to its early-access data center ledger.
Was the software tested at a customer site?
No customer deployment is identified in the release. Rymvard says the reported results came from a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs.
How does the ledger report whether a takeover can fit?
It reports whether the secondary host fits the primary system’s allocation, could fit after stopping named systems, has a shortfall measured in GiB, or has an unknown status. Stale replication or memory data produces an unknown result.
Does Rymvard write data to SAP?
Rymvard says its SAP connections are read-only and states that nothing is written to SAP. The release lists specific Host Agent operations and other read-only data sources.
When will the product be generally available, and what does it cost?
The company has announced neither a broader availability date nor a public price list. It says early-access terms are agreed directly with partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
