🔍 Read the full analysis: Read-Only By Design: How A Capacity Ledger Connects To SAP Without Writing To It 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 early-access capacity ledger connects to SAP using read-only interfaces, including four permitted SAP Host Agent operations and six fixed HANA monitoring queries. The product has been tested against a simulator representing 200 hosts, not a customer estate; no customer deployment or outcomes are reported.
Rymvard says its early-access capacity ledger for data centers connects to SAP systems through read-only interfaces and does not write to them. The company describes a restricted collection design using SAP Host Agent operations, HANA monitoring queries and landscape tools, a relevant detail for SAP teams weighing how third-party software can access production environments.
At each site, Rymvard’s collector communicates with the SAP Host Agent over HTTPS and allows only four read operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. Rymvard says the collector refuses other operations. A separate component reads HANA monitoring views using a fixed list of six SELECT queries, as a monitoring user over TLS. The company sets a 60-second limit per system and a maximum of eight systems queried at a time.
Rymvard also says it reads landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa, using their read-only interfaces. The intended result is a ledger of systems, customers and environments assembled from existing records and observed infrastructure. Rymvard says data records remain in the country where they were measured, while customer names are visible only to planners and administrators.
The company says records are matched from evidence rather than inferred assignments: an instance is linked to the system already running on its host. A system not declared by an organization is recorded as a development system with 0.5 confidence and reported, rather than assigned to a customer. Values that a source can only guess do not overwrite declared values. An instance no longer listed by the Host Agent on its host is removed from the ledger.
SAP Access · Early Access · Company-Reported
Read-Only By Design
How a capacity ledger connects to SAP without writing to it. Rymvard describes a restricted collection design for data center planning; its connection has been tested in a simulator, with no customer deployment or outcomes reported.
01 / Collection path
Read from the landscape, then assemble a ledger
Rymvard says its collector combines observed infrastructure with existing landscape records. The described interfaces are read-only, and collection is bounded by an allowlist and query limits.
Four permitted reads
The collector communicates with SAP Host Agent and refuses operations outside this fixed set.
Fixed monitoring queries
A separate component reads HANA monitoring views with six SELECT queries over TLS: up to 60 seconds per system and no more than eight systems at once.
Existing records, read-only
Rymvard says it reads SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa using read-only interfaces.
02 / Interpretation rules
Records follow evidence, not assumptions
Rymvard describes safeguards for linking system records and handling missing or conflicting information. The quality of the ledger still depends on the coverage and accuracy of its source data.
- Link by observed placement: an instance is matched to the system already running on its host.
- Do not guess a customer: an undeclared system is marked as development and reported.
- Preserve declared values: a source that can only guess does not overwrite a declared value.
- Remove stale instances: an instance no longer listed by its host’s Host Agent is removed from the ledger.
- Keep detailed records local: the company says data remains in the country where measured.
- Restrict customer-name visibility: names are visible only to planners and administrators.
03 / What has been demonstrated
Simulator testing is not customer proof
Rymvard says the product is running in early access. Publicly described connection testing used a simulator representing 200 hosts—not a customer’s live SAP estate.
Reported by Rymvard
The connection was tested against a simulator responding like SAP Host Agent and HANA monitoring views in a 200-host landscape. Product screens show an illustrative example estate.
Not established publicly
No customer deployment, live operating results, or measured capacity-planning outcomes have been reported. The 200-host simulator does not establish production performance or reliability at that scale.
Rymvard has not identified an early-access organization using the product.
No independent security review or specific hosting arrangements have been disclosed.
Update speed, unavailable or inconsistent sources, and customer-configurable controls remain unclear.
04 / Evaluation ahead
Live use will provide the next evidence
The practical test is whether early-access partners can connect real SAP landscapes under the stated restrictions, and how the ledger behaves with real data.
What remains to be learned
Rymvard has not announced a wider release date or published pricing; pricing is agreed with early-access partners. The company invites inquiries at contact@rymvard.com. Until customer experience or further technical validation is published, the access rules and simulator results remain company-reported details.
05 / Key questions
What SAP teams may want to know
Does Rymvard write data to SAP?
Rymvard says it does not. Its described Host Agent connection permits four read operations and uses read-only interfaces for the other landscape tools.
How does it read HANA monitoring data?
A separate component runs six fixed SELECT queries against monitoring views with a monitoring user over TLS. The stated limits are 60 seconds per system and eight systems at once.
Has it been tested in a customer SAP environment?
No customer deployment is identified. Rymvard describes simulator testing for a 200-host landscape and says the displayed estate is illustrative.
How is an undeclared system handled?
It is recorded as a development system with confidence 0.5 and reported, rather than assigned to a customer by guess.
Is the product available, and what does it cost?
Rymvard says the product is running in early access. Prices are not published; the company says pricing is agreed with early-access partners.
What does the design mean for evaluation?
The stated restrictions may help cautious SAP teams assess access, but they are a company description—not an independent security certification.
Read-Only Access for SAP Teams
Production SAP environments can support business-critical workloads, so permission to change system data is a major operational concern. Rymvard’s described approach is to gather information for capacity planning while limiting access to specified read operations. That design may make the product easier for cautious SAP basis teams to evaluate, though the stated restrictions are a description of Rymvard’s implementation, not an independent security certification.
The approach also matters for how capacity records are interpreted. Explicitly marking an undeclared system as a development system with a confidence value, and declining to guess its customer, makes uncertainty visible instead of presenting an inferred relationship as confirmed. The ledger’s usefulness will still depend on the quality and coverage of the underlying SAP and landscape data.
As an affiliate, we earn on qualifying purchases.
Simulator Testing, Not Customer Proof
Rymvard describes itself as a capacity ledger for data centers and says it has no SAP system of its own. It built and tested the connection against a simulator that responds like the SAP Host Agent and HANA monitoring views for a landscape of 200 hosts. The company says the product is running in early access and that the screens shown are from the product on an illustrative example estate.
That qualification sets the limits of what has been demonstrated publicly: simulator testing is not the same as operating across a customer’s live estate. Rymvard says the scenarios are illustrative and do not imply a customer, site or outcome. It has not published prices, saying pricing is agreed with early-access partners.
““Nothing is ever written to SAP.””
— Rymvard
read-only SAP landscape management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Live Deployment Evidence Still Missing
Rymvard has not identified a customer using the product or provided results from a live SAP deployment. It also has not disclosed an independent security review, specific hosting arrangements, or technical details beyond the stated interfaces, query limits and access rules. The simulator’s 200-host landscape describes its test setup; it does not establish performance or reliability across a customer environment of that size.
Other practical questions remain open, including how quickly the ledger reflects changes, how it handles unavailable or inconsistent data sources, and what controls customers can inspect or configure. Rymvard’s description does not provide measured capacity-planning outcomes, pricing, or a timetable for moving beyond early access.
SAP landscape data collection tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Early-Access Evaluation Comes Next
The next evidence will need to come from the product’s early-access use: whether partner organizations can connect it to their SAP landscapes under the stated restrictions, and how the ledger performs with real system data. Rymvard has not announced a broader release date or named an early-access customer.
The company says pricing is arranged with early-access partners and invites inquiries through contact@rymvard.com. Until it publishes customer experience or further technical validation, the read-only controls and simulator results remain company-reported details rather than proof of performance in production.
Source: Rymvard
As an affiliate, we earn on qualifying purchases.
Key Questions
Does Rymvard write data to SAP?
Rymvard says it does not write to SAP. Its described connection permits four SAP Host Agent read operations and uses read-only interfaces for other landscape tools.
How does the product read HANA monitoring data?
Rymvard says a separate component runs a fixed list of six SELECT queries against HANA monitoring views, using a monitoring user over TLS. It sets a 60-second limit per system and queries no more than eight systems at a time.
Has Rymvard been tested in a customer’s SAP environment?
No customer deployment is identified. Rymvard says it tested the connection against a simulator representing a 200-host landscape and describes the displayed estate as illustrative.
How does the ledger handle an undeclared system?
Rymvard says it records an undeclared system as a development system with 0.5 confidence and reports it, rather than guessing which customer it belongs to.
Is Rymvard available, and what does it cost?
The product is in early access and is running, according to the company. Rymvard has not published prices; it says pricing is agreed with early-access partners.
Source: Rymvard
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
