AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

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

Get monitors, keyboards and dev gear 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.

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 company’s reported test results came from a simulated estate; it has not identified a customer deployment or reported customer outcomes.

Rymvard released version 0.23 on October 4, adding SAP HANA memory accounting, proposed system placement and replication takeover checks to its data center capacity ledger. The early-access software is aimed at SAP hosting providers and operations teams, but the company’s reported test results are from a simulated estate, not a customer deployment.

For each HANA host, the software separates physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused memory, capacity set aside for replicas from other sites, and remaining free memory. Its default operating-system reserve is 10 percent of the first 64 GiB and 3 percent of the memory above that, unless a host has a different reserve configured. System usage is calculated from its 30-day peak. If allocations exceed physical memory, the ledger shows overbooking rather than presenting a negative free-memory figure.

For systems using HANA system replication, Rymvard checks whether a secondary host could accommodate a primary system’s allocation after a takeover. It accounts for the replicated system moving to the secondary and can treat specifically named test or development systems as stoppable. It does not treat other customers’ production systems as stoppable. Results are reported as fits, fits after stopping named systems, a failure with a shortfall stated in GiB, or unknown.

The status can be unknown when source data is stale: replication information older than an hour or a memory figure older than 24 hours does not produce a passing result. Scale-out systems are assessed 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-level memory runway by quarter, using planned go-lives weighted by their probability.

At a glance
announcementWhen: Released October 4, 2026; early access
The developmentRymvard’s October 4 release adds early-access SAP HANA memory and failover-capacity planning to its data center capacity software.

Making HANA Failover Capacity Visible

The release addresses a specific planning problem for providers: memory can limit HANA capacity even when a data center appears to have room in its wider infrastructure. A host may be overcommitted, or a replication partner may lack enough memory to take over a system. Showing those conditions separately from general capacity can help teams identify a constraint before placing a workload or relying on a failover plan.

The takeover result is particularly relevant to operations teams because it distinguishes a nominal replication relationship from the ability to accommodate the workload on the other side. A warning about a shortfall, or a result marked unknown because measurements are stale, gives planners a different signal from a simple indication that replication is configured. However, the release describes the software’s checks; it does not establish that they improve reliability or prevent outages in customer environments.

Rymvard says HANA instances are mirrored into its compute view, allowing SAP memory to appear in customer showback and lifecycle planning. Its new SAP Operations workspace displays four indicators: free HANA memory, production systems without replication, takeovers that would fail and hosts above 90 percent utilization. These views could support comparisons of proposed deployments and site capacity, but the company has not reported measured savings, operating results or customer outcomes.

Amazon

SAP HANA memory management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

How the Capacity Ledger Works

Rymvard describes the product as early-access software that links SAP HANA memory information with data center capacity planning. The release identifies SAP Host Agent, monitoring connections and landscape-management sources as ways to supply information. It says the 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 these connections do not write to SAP. It also lists read-only access to SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa for system, customer and environment information. The release names these as supported sources; it does not say that customers must connect all of them together.

Rymvard reports testing version 0.23 against a simulated landscape of 200 HANA hosts, 161 systems and 39 replicated pairs. In that scenario, it says 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, and the example does not imply a real customer, site or outcome.

“Nothing is ever written to SAP.”

— Rymvard

Amazon

data center capacity planning software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Customer Results Remain Unreported

Rymvard has not named a customer using version 0.23 or supplied outcomes from a live deployment. The figures it reports come from a simulated landscape, so they do not show how the checks perform across customer systems, unusual SAP configurations or changing workloads. No independent evaluation is included in the release material.

Other details also remain open, including how integrations are validated in each customer environment and how quickly capacity readings refresh beyond the stated age thresholds. Rymvard has not published pricing, saying terms are arranged with early-access partners. The release describes the product’s rules and stated limits, but does not provide a broader availability date or a public price list.

Amazon

HANA system replication capacity check

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 commercial terms arranged directly with Rymvard. Those evaluations could provide evidence about how the ledger handles live HANA landscapes and whether its placement and takeover views fit provider operations. The company has not said when that evidence will be available.

Rymvard has not announced a general release date, named an early-access customer or published pricing. Until it shares live deployment data or independent assessments, the reported scenario should be read as a demonstration of the software’s stated checks rather than evidence of customer performance.

Amazon

server memory allocation monitoring

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, proposed placement for new systems, replication takeover checks and site-level quarterly memory runway estimates to its capacity ledger.

Has Rymvard reported a customer deployment?

No customer deployment or customer outcome is identified in the release material. The reported test used a simulated estate.

How does the software handle stale capacity data?

Rymvard says the takeover result becomes unknown if replication status is more than an hour old or a memory figure is more than 24 hours old, rather than treating stale information as proof that capacity is sufficient.

Does the software write to SAP?

Rymvard says its SAP connections are read-only and states, “Nothing is ever written to SAP.” The release lists specific read operations and other supported read-only information sources.

When will the software be generally available?

Rymvard has not announced a broader availability date. The release describes version 0.23 as early access, with partner terms arranged directly with the company.

Primary source: Rymvard · via ThorstenMeyerAI.com

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Walgit – A Git Server That Is One Binary In Front Of An Object Store

Walgit is introduced as a new Git server architecture, consisting of one binary layer interfacing directly with an object store. This approach aims for simplicity and scalability.

CSS-Tricks In Limbo

Search interest in CSS-Tricks spikes, but the platform’s future remains unclear amid ongoing staffing and operational uncertainties.

Android 17 Is The First Since 3.X To Add New APIs Without Releasing To The AOSP

Android 17 is the first version since 3.x to introduce new APIs outside of the official AOSP release, signaling a shift in update practices.

The Hidden Difficulties Of Regulating Artificial Minds

Exploring Europe’s struggles to regulate AI amidst hybrid threats like drone attacks, highlighting the gap between regulation and technological capability.