🔍 Read the full analysis: Can You Connect A Capacity Ledger To SAP Without Writing Data? on Rymvard
Get privacy and security 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
TL;DR
Rymvard says its capacity ledger connects to SAP using read-only operations, including a fixed set of HANA monitoring queries, and does not write to SAP. The product is in early access, and its SAP connection was tested against a simulator representing 200 hosts, not a customer SAP landscape.
Rymvard says its capacity ledger connects to SAP without writing data, using a restricted set of read operations to collect system and database information for capacity planning. The product is in early access, and the company says it tested the integration against a simulator rather than a customer SAP landscape, leaving live-customer performance and outcomes unestablished.
A small collector at each site communicates with the SAP Host Agent over HTTPS. Rymvard says the collector permits four read operations only: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. It says requests outside those operations are refused. A separate component reads HANA monitoring views over TLS using a monitoring account and a fixed list of six SELECT queries. Each system has a 60-second limit, with no more than eight systems queried at once.
Rymvard also says it can read landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa, using read-only interfaces. The company describes the overall connection as non-writing: nothing is written back to SAP. That is a description of the product’s design from Rymvard, not an independently verified security assessment.
The ledger uses evidence to associate instances, systems, customers and environments. Rymvard says an instance is linked to the system already running on its host. A system that has not been declared is recorded as a development system with 0.5 confidence and reported rather than assigned to a customer by guess. The company says an inferred value does not replace one that has been declared, and an instance no longer listed by the Host Agent on its host is removed from the ledger.
Can You Connect a Capacity Ledger to SAP Without Writing Data?
Rymvard says its capacity ledger gathers SAP inventory through restricted read-only interfaces. Its integration has been tested against a simulator representing 200 hosts; validation in a customer SAP landscape has not been described.
How the read-only boundary is described
Collection path · Rymvard accountA small collector at each site communicates with SAP Host Agent over HTTPS. A separate component reads HANA monitoring views over TLS using a monitoring account. Rymvard says requests outside its permitted set are refused.
Four allowed calls
Rymvard says its collector is limited to these SAP Host Agent operations:
- ListInstances
- ListDatabases
- GetDatabaseStatus
- GetComputerSystem
Fixed query set
Six fixed SELECT queries read HANA monitoring views over TLS. Rymvard says each system has a 60-second limit, with no more than eight systems queried at once.
Read-only interfaces
Rymvard also says it can read landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa.
Evidence, matching and uncertain records
Ledger behavior · As describedShow uncertainty instead of guessing
Rymvard says an instance is linked to the system already running on its host. When a system has not been declared, the ledger records it as a development system with 0.5 confidence and reports it, rather than assigning it to a customer by guess.
An inferred value does not replace a value that has been declared, according to Rymvard.
An instance no longer listed by Host Agent on its host is removed from the ledger.
Rymvard says detailed records stay in the country where measured; customer names are visible only to planners and administrators.
Collector requests limited inventory data.
Evidence links instances to systems and environments.
Undeclared systems carry a stated confidence value.
Ledger records support planning; no SAP write-back is claimed.
What the simulator test establishes—and leaves open
Evidence statusAvailable information
- The connection was tested against a simulator representing a 200-host landscape, designed to respond like Host Agent and HANA views.
- The product is in early access; shown screens use an illustrative estate, not a customer environment.
- Terms are agreed with early-access partners; pricing is not published.
Live-system evidence
- No customer SAP landscape test or named early-access deployment is described.
- Live configuration coverage, failure handling, and unusual system responses remain unestablished in the available description.
- No independent security review, deployment outcomes, or broader availability timetable is provided.
Design intent is not deployment evidence
Rymvard’s stated permissions, query limits, data-location rules and matching behavior give SAP teams concrete points to assess against their own requirements. The simulator test can demonstrate handling of simulated responses, but does not establish performance or outcomes in customer environments.
Key questions
Quick referenceDoes Rymvard write data to SAP?
Rymvard says nothing is written to SAP. It describes restricted Host Agent operations and HANA monitoring queries as read-only product behavior.
How does it read HANA data?
It says a monitoring user connects over TLS to run six fixed SELECT queries, with a 60-second limit per system and up to eight systems queried at once.
Was it tested with a customer SAP system?
Rymvard describes testing against a simulator for a 200-host landscape, not a customer SAP environment. The screens shown use an illustrative estate.
How are unclassified systems handled?
An undeclared system is recorded as development with 0.5 confidence and reported, rather than assigned to a customer by guess. Inferred values do not replace declared ones.
Is it available, and what does it cost?
The product is in early access. Rymvard has not published pricing; it says terms are agreed with early-access partners.
What remains to be assessed?
Live-estate performance, failure handling and independent review have not been established in the information described. Teams can assess the stated controls against their requirements.
Read-Only Boundaries for SAP Teams
For teams managing production SAP estates, the central practical question is whether a capacity-planning tool can gather inventory without changing operational systems. Rymvard’s stated design draws a boundary around collection: limited Host Agent calls, a fixed set of HANA queries, and read-only access to landscape tools. Those constraints may help SAP basis teams evaluate whether the integration fits their change-control and access policies.
The approach to uncertain records also matters. Marking an undeclared system as a development system with a confidence score, instead of silently assigning it to a customer, makes the uncertainty visible to planners. That could reduce the risk of treating an inference as authoritative inventory. But the effectiveness of these safeguards depends on how the product is configured and behaves in a real estate, details not established by the available product description.
Data location and permissions are part of the stated design as well. Rymvard says detailed records remain in the country where they were measured, while customer names are visible only to planners and administrators. These controls are relevant to organizations assessing data residency and internal access. They are company-described features, not evidence of an audit, certification or customer deployment.
As an affiliate, we earn on qualifying purchases.
Simulator Testing, Not Customer Deployment
Rymvard describes its product as a capacity ledger for data centers and says it is already running in early access. The company says the screens shown are from the running product using an illustrative example estate; they do not depict a customer environment. Its listed scenarios are illustrative, and it says no particular customer, site or outcome is implied.
The company says it has no SAP system of its own. It therefore built and tested the connection against a simulator representing a 200-host landscape, designed to respond like the SAP Host Agent and HANA views. That test setup can show how the integration handles simulated responses, but it is not the same as testing against a live customer system. Rymvard has not published pricing; it says terms are agreed with early-access partners.
“Nothing is ever written to SAP.”
— Rymvard
As an affiliate, we earn on qualifying purchases.
Live-System Validation Still Pending
The key limitation is that Rymvard says its SAP connection was tested against a simulator, not against a customer’s SAP environment. The company has not provided details establishing how the integration performs across live configurations, how it handles failures or unusual system responses, or whether an independent party has reviewed its security controls. Those points remain open for organizations considering an evaluation.
Rymvard has not identified an early-access customer, published deployment outcomes, or stated when broader availability might begin. Its claims about read-only behavior, data residency and access restrictions are product descriptions from the company; the information available here does not include independent verification. Pricing is also not public, with the company saying it is agreed with early-access partners.
As an affiliate, we earn on qualifying purchases.
Early-Access Testing and Evidence
The next meaningful evidence would come from disclosed early-access deployments or independent validation showing how the integration behaves with customer SAP landscapes. Rymvard has not announced a timetable for either. Organizations interested in the product can contact the company at contact@rymvard.com; its early-access pricing is negotiated with partners rather than published.
Until live-system evidence or further technical documentation is available, SAP teams will need to assess the stated permissions, query limits, data-location rules and record-matching behavior against their own requirements. The simulator test and product description explain the intended design, but do not establish results in customer environments.
Source: Rymvard
As an affiliate, we earn on qualifying purchases.
Key Questions
Does Rymvard write data to SAP?
Rymvard says nothing is written to SAP. It describes its connections as read-only, including restricted SAP Host Agent operations and HANA monitoring queries. This is the company’s account of the product design.
How does the integration read HANA data?
Rymvard says it uses a monitoring user over TLS to run six fixed SELECT queries against HANA monitoring views. It sets a 60-second limit per system and queries at most eight systems at a time.
Has Rymvard tested the connection with a customer SAP system?
Rymvard says it tested against a simulator that responds like the SAP Host Agent and HANA views for a 200-host landscape. It has not described that test as a customer deployment, and the screens shown use an illustrative estate.
How does the ledger handle systems it cannot confidently classify?
Rymvard says an undeclared system is recorded as a development system with 0.5 confidence and reported, rather than assigned to a customer by guess. It also says an inferred value does not replace a declared one.
Is Rymvard available, and what does it cost?
The product is in early access. Rymvard has not published prices and says pricing is agreed with early-access partners.
Source: Rymvard
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
