Rymvard Brings SAP HANA Memory Into Data Center Capacity Oversight

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get hardware and tech essentials 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

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Rymvard released version 0.23 on October 4, 2026, adding SAP HANA memory tracking, placement proposals and replication takeover checks to its data center capacity ledger. The company tested the early-access software on a simulated estate, not a live customer deployment, and has not reported customer outcomes.

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 landscape, not a customer deployment.

The new ledger view breaks down memory on each HANA host into an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas from other sites, and what remains free. 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. HANA system usage is based on its 30-day peak. If allocations exceed physical memory, the software identifies overbooking rather than presenting the excess as negative free capacity.

For systems using HANA system replication, version 0.23 checks whether the secondary host could accommodate the primary system’s allocation after a takeover. It reports whether the system fits, fits if specified test or development systems are stopped, falls short by a stated number of GiB, or has an unknown status. Rymvard says production systems belonging to other customers are not treated as stoppable. A replication status older than one hour or a memory reading older than 24 hours results in an unknown outcome rather than a passing assessment. Scale-out systems are evaluated as a whole, based on their weakest host pair.

The release also proposes a host and replication-site partner for a new HANA system and estimates memory runway by site and quarter. Those estimates use planned go-lives weighted by their probability. Rymvard says HANA instances are mirrored into its compute view, where they can appear in customer showback and lifecycle planning. A new SAP Operations workspace displays free HANA memory, production systems without replication, takeovers that would fail, and hosts above 90% utilization.

Making HANA Failover Capacity Visible

The release addresses a specific planning problem for SAP hosting providers: available data center capacity does not guarantee available HANA memory. A site may have room in its broader infrastructure while a particular HANA host, or its replication partner, cannot accommodate another allocation or a failover. Showing host overbooking and takeover shortfalls separately could help operations teams identify those constraints before placing systems or relying on a secondary host.

The freshness rules are also relevant to how teams interpret the results. A stale replication status or memory measurement is marked unknown, rather than being treated as evidence that a takeover will work. That is a cautious reporting rule, but its practical value depends on the quality and timeliness of the information available to the ledger. Rymvard’s placement proposals and quarterly runway estimates may help teams compare expected deployments with site capacity; the release does not establish that they produce cost savings, improve reliability or change customer outcomes.

Read-Only SAP Data Connections

Rymvard says its collector connects to the 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’s stated position is that the software does not write to SAP.

The release also lists read-only sources for landscape information: SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa. Rymvard describes these as supported sources; it does not say that customers must connect all of them. The product is presented as an early-access addition to the company’s existing compute view, rather than as a change to SAP systems themselves.

Rymvard says it tested version 0.23 against a simulated estate 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 and do not represent a real customer, site or outcome. These figures describe that test scenario; they are not reported customer results.

“Nothing is ever written to SAP.”

— Rymvard

Live Customer Results Not Reported

Rymvard has not identified a customer deployment for this release or supplied customer outcomes. Its test findings are from a simulated landscape, so they do not show how the software performs across live customer environments, unusual SAP configurations or workloads that change over time. The company has also not published independent evaluations or real-world performance data.

The release describes the access limits and data-age thresholds, but leaves open how integrations are validated in individual environments and how the product handles every possible SAP configuration. Rymvard has not published prices; it says terms are arranged directly with early-access partners. A broader availability date and public price list have not been announced.

Early-Access Partner Evaluations

The next step is evaluation by early-access partners, with commercial terms arranged directly with Rymvard. Those evaluations could provide evidence about how the memory ledger, placement proposals and takeover checks work with live SAP landscapes, but the company has not announced a timeline for partner findings or public case studies.

Rymvard has not set a date for broader availability or published a public price list. Until it reports customer deployments or independent testing, the release’s stated capabilities and simulated test results remain the available evidence for assessing version 0.23.

Key Questions

What did Rymvard add in version 0.23?

Version 0.23 adds SAP HANA memory accounting, proposed host and replication-site placement, and checks of whether a secondary host could accommodate a replicated system after takeover.

Was the software tested at a customer site?

No customer deployment is reported. Rymvard says its 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 result, not a passing takeover assessment.

Does Rymvard write data to SAP?

The company says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release describes limited Host Agent read operations and separate read-only monitoring queries.

When will the product be generally available?

Rymvard has not announced a broader availability date. It says the current release is in early access, with pricing terms agreed directly with partners.

Primary source: Rymvard · via ThorstenMeyerAI.com