TL;DR
Get tech for your team 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 covered a simulated landscape of 200 hosts; the company has not identified a customer deployment or provided customer outcome data.
Rymvard released version 0.23 on October 4, 2026, 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 release is aimed at SAP hosting providers and operations teams. Rymvard says its tests used a simulated estate, not a customer deployment, so the release describes product functionality but does not establish results in live customer environments.
The software divides each HANA host’s physical memory among an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and remaining free memory. The default reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host has a different reserve configured. System usage is based on its 30-day peak. If allocations exceed physical memory, the ledger reports overbooking instead of presenting a negative free-capacity figure.
For systems using SAP HANA system replication, version 0.23 checks whether a secondary host could accommodate the primary system’s allocation after a takeover. It can count specifically named test or development systems as stoppable, but does not treat other customers’ production systems as stoppable. Results are reported as a fit, a fit after stopping named systems, a shortfall stated in GiB, or an unknown result. A replication status older than one hour or a memory figure older than 24 hours produces an unknown status rather than a passing assessment. Scale-out systems are evaluated as a whole, using the weakest host pair.
The release also proposes a host and replication-site partner for a new HANA system and estimates site-by-site, quarterly memory runway using planned go-lives weighted by their 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 the 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
Spotting HANA Memory Constraints
The release addresses a planning issue for providers whose immediate constraint is memory capacity, not the broader availability of data center resources such as power. A site may appear to have room overall while a particular HANA host—or the secondary host expected to take over—cannot accommodate an allocation. Showing overbooking and takeover shortfalls separately could help operations teams identify these limits before placing a system or relying on failover capacity.
The value of those checks depends on accurate, current data. Rymvard’s rules deliberately return an unknown when relevant readings are too old, rather than treating stale information as proof that capacity is available. That makes the status less conclusive when data is outdated, but avoids reporting a pass on that basis. The placement proposals and quarterly runway estimates could help teams compare deployments with planned capacity; the release material does not establish that they reduce costs, improve reliability or produce other customer outcomes.
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 release also lists read-only connections to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa for landscape information. The material does not say that customers must use all of these tools together. Rymvard describes version 0.23 as early-access software, with terms agreed directly with early-access partners rather than a published price list.
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, a takeover short by 512 GiB, a 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; those figures are test results, not customer findings.
“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 Not Reported
Rymvard has not named a customer deployment for version 0.23 or supplied customer outcome data. Its reported test results come from a simulated environment, and the company says the illustrative screens do not represent a real customer, site or outcome. The material therefore does not show how the checks perform across live SAP landscapes, unusual configurations or workloads that change over time.
Other details remain undisclosed, including public pricing, an expected broader availability date and independent evaluations. The release describes data-age thresholds and query limits, but does not provide a complete account of how integrations are validated in each customer environment or how readings behave outside the stated rules. The reported scenarios should be read as examples of the software’s intended checks, not proof of operational or financial benefits.
As an affiliate, we earn on qualifying purchases.
Early-Access Evaluation Ahead
The next step is evaluation by Rymvard’s early-access partners, with commercial terms arranged directly with the company. Rymvard has not announced a public price list, a broader release date or a named customer. Evidence from partner use, if later disclosed, would help clarify how the accounting and takeover checks perform against live SAP environments and whether the planning views support customer operations.
HANA system replication capacity checks
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, host and replication-site placement proposals, takeover capacity checks, and a workspace showing selected HANA operations indicators.
Has Rymvard reported a customer deployment?
No customer deployment or customer outcome is identified in the release material. The company says its reported test used a simulated estate.
When can a takeover check return an unknown result?
Rymvard says the result is unknown if replication status is more than one hour old or a memory figure is more than 24 hours old.
Does the software write to SAP?
Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The described collector uses read operations, alongside a separate monitoring connection using SELECT queries.
When will the software be generally available?
Rymvard has not announced a broader availability date. The release is described as early access, with evaluation by partners the next stated step.
Primary source: Rymvard · via ThorstenMeyerAI.com
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
