TL;DR
Rymvard released version 0.23 on October 4, 2026, adding SAP HANA memory accounting, system placement proposals and replication takeover checks to its capacity ledger. The company says the software uses read-only SAP connections, but its reported results came from a simulated landscape rather than a customer deployment.
Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting and replication takeover checks to its data center capacity ledger. The early-access software is aimed at SAP hosting providers and operations teams that need to plan HANA placements and assess whether a secondary host has enough memory to take over a system; the company’s reported tests used a simulated estate, not a customer deployment.
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
For each HANA host, the ledger divides physical memory among an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and free capacity. The default reserve is 10 percent of the first 64 GiB and 3 percent of the remaining memory, unless a host has a different reserve configured. System usage is based on its 30-day peak. Allocations above physical capacity are shown as overbooking rather than hidden as negative free memory.
For HANA system replication, the software checks whether a secondary host could accommodate the primary system’s allocation after takeover. It returns one of four outcomes: fits, fits after stopping named systems, does not fit—with a shortfall in GiB—or unknown. Named test or development systems may be treated as stoppable; production systems belonging to other customers are not. A replication status more than an hour old or a memory reading more than 24 hours old produces an unknown result, not a passing check. Scale-out systems are assessed as a whole, 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, weighting planned go-lives by their probability. A new SAP Operations workspace highlights 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 be used 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
The release addresses a planning problem for providers whose constraint is memory rather than power. A data center may have room in its broader infrastructure while a particular HANA host—or the partner expected to receive a replicated system—lacks memory for a placement or takeover. Separating overbooking from takeover shortfalls could help operations teams identify those limits before a new system is placed or a failover is needed.
The checks are only as useful as the data behind them. Rymvard’s rule that stale readings produce an unknown result avoids presenting old information as evidence that capacity is available. Its placement and quarterly runway views may help teams compare planned deployments across sites, but the release does not provide evidence of customer savings, improved reliability or operational outcomes. The distinction between a described feature and demonstrated results matters because this is early-access software and the supplied test estate was simulated.
Popular right now

Breville Bambino Espresso Machine, Brushed Stainless Steel

Ninja Double Oven Pro XL Countertop Oven and Air Fryer, 12-in-1, Onyx, DCT801BK

KitchenAid Artisan 5-Qt Tilt-Head Stand Mixer, Almond Cream
As an affiliate, we earn on qualifying purchases.
Read-Only SAP Data Connections
Rymvard says its collector connects to the SAP Host Agent over HTTPS and permits 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 product does not write to SAP.
The release also lists read-only sources for system, customer and environment information: SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard presents these as supported sources, not as tools that must all be used together. Its reported version 0.23 test covered a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, the software 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 screens use an illustrative estate, not a customer environment.
“Nothing is ever written to SAP.”
— Rymvard
Customer Results Remain Unreported
Rymvard has not identified a customer deployment or supplied customer outcome data for version 0.23. Its test figures describe a simulated landscape, and the company says the examples do not represent a real customer, site or outcome. The release therefore does not establish how the checks perform across live customer environments, unusual SAP configurations or workloads that change over time.
Other details are also not public, including pricing, which Rymvard says is arranged with early-access partners, and a date for broader availability. The release describes data-age thresholds but does not provide independent validation of the integrations or explain how quickly readings update in individual environments. These limits leave the software’s real-world performance and deployment experience unverified in the supplied material.
Early-Access Evaluations Ahead
The next stated step is evaluation by early-access partners, with commercial terms agreed directly with Rymvard. The company has not announced a public price list, a named customer or a wider availability date. Evidence from partner deployments could clarify how the ledger handles different SAP landscapes and whether its placement and takeover views prove useful in day-to-day capacity planning.
Until such results are published, readers should treat the reported findings as a description of product behavior in a simulated test, rather than evidence of customer performance. Rymvard has not provided a timetable for additional releases or announced when it may share deployment outcomes.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA memory accounting, proposed system placement, replication takeover checks and related capacity views to its data center ledger.
Does the software write to SAP systems?
Rymvard says its SAP connections are read-only and that the product does not write to SAP.
Were the reported test results from a customer deployment?
No. Rymvard says its test used a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs, and that its screens show an illustrative estate.
How does Rymvard handle outdated capacity data?
It reports takeover capacity as unknown if replication status is more than an hour old or a memory figure is more than 24 hours old.
When will the product be generally available?
Rymvard has not announced a broader availability date. The next stated step is evaluation by early-access partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
