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 version 0.23 on October 4, 2026, adding SAP HANA memory accounting, placement proposals and replication takeover checks to its data center capacity ledger. The early-access software connects through read-only interfaces; the company’s reported results came from a simulated landscape, with no customer deployment or outcomes identified.
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 detailed in the original analysis. The early-access software 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 release breaks down each HANA host’s physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and remaining free memory. Unless a host has a different reserve configured, Rymvard sets aside 10% of the first 64 GiB and 3% of the remainder. System usage is based on its 30-day peak. Allocations that exceed physical memory are shown as overbooking rather than being hidden as negative free capacity.
For systems using SAP HANA system replication, the software checks whether a secondary host could take over the primary system’s allocation. It reports whether the allocation fits, fits after named test or development systems are stopped, exceeds capacity by a stated amount, or has an unknown status. The company says production systems belonging to other customers are not treated as stoppable. Replication status older than one hour or memory data older than 24 hours results in an unknown outcome rather than a passing check. Scale-out systems are evaluated 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, using planned go-lives weighted by probability. A new SAP Operations workspace highlights 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 their 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
Why HANA Memory Shapes Placement
The release addresses a capacity-planning problem that can be missed when teams look only at a data center’s overall infrastructure. A facility may have room in its broader systems while a particular HANA host—or its replication partner—lacks the memory needed for a new allocation or a failover. By showing overbooking and takeover shortfalls separately, Rymvard’s ledger is intended to help operations teams see those constraints before placement or a recovery event.
That visibility could inform decisions about where to host new systems, whether a secondary site can absorb a workload, and how planned go-lives compare with expected capacity. But the release does not establish savings, improved reliability, or customer results. The practical value depends on the accuracy and freshness of the information available to the software, as well as how well its rules fit each customer’s SAP landscape. Its treatment of stale data as unknown is a cautious safeguard, not evidence that a takeover will succeed.
As an affiliate, we earn on qualifying purchases.
Read-Only Connections, Simulated Tests
Rymvard says its collector communicates with 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 names 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 describes these as supported sources, not tools that must all be connected together.
For its reported test, Rymvard used 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 with a 512 GiB shortfall, 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 real customer, site or 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.
Customer Performance Remains Unreported
Rymvard describes version 0.23 as early access and has not identified a customer deployment or supplied customer outcomes for the release. Its test figures are from a simulation, so they do not show performance across live customer environments, unusual SAP configurations or workloads that change over time. The company has not provided independent evaluations or real-world reliability data.
Other details are also not established in the release material, including how integrations are validated in individual environments and how frequently readings update beyond the stated thresholds for marking data stale. Rymvard has not published prices, saying terms are agreed with early-access partners. The reported test findings should be read as results from the described scenario, not as evidence of results customers can expect.
SAP HANA replication management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Evaluations Ahead
The immediate next step is evaluation by early-access partners, with pricing arranged directly with Rymvard. The company has not announced a broader availability date, public price list or named customer deployment. Further evidence from live environments would be needed to show how the placement and takeover checks perform across varied SAP landscapes and operational conditions.
Until such information is available, providers considering the release can assess its stated data sources, memory rules and stale-data thresholds against their own requirements. Whether the product delivers useful planning outcomes in customer environments remains unreported.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Rymvard add in version 0.23?
It added SAP HANA host-level memory accounting, placement proposals, replication takeover-capacity checks and a workspace for viewing selected HANA operations indicators.
Has Rymvard reported results from a customer deployment?
No customer deployment or customer outcome is identified in the release material. The reported test used 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 older than one hour or a memory figure older than 24 hours produces an unknown takeover result, rather than a passing result.
Does the collector write to SAP?
Rymvard says it uses read-only interfaces and does not write to SAP. It lists four permitted SAP Host Agent read operations, along with a separate monitoring connection using six SELECT queries.
When will the software be generally available, and what will it cost?
The company has not announced a broader availability date or public price list. It says terms are arranged directly with early-access partners.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
