🔍 Read the full analysis: In-Country SAP In India: A HANA Capacity Planning Checklist on Rymvard
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Rymvard is offering an early-access tool for in-country SAP hosting providers to plan HANA capacity across customer landscapes and sites. It models system memory use, replica needs and probability-weighted future deployments; its Mumbai example is illustrative, not a customer case.
Rymvard says its early-access product helps in-country SAP hosting providers in India plan HANA memory capacity across customer systems, sites and replicas. The company says its running tool accounts for current system use and probability-weighted planned landscapes; the Mumbai estate shown is illustrative, not a customer deployment.
The product is designed to give providers a view of memory capacity across multiple customers, rather than rely on a separate spreadsheet for each estate. Rymvard says it identifies each SAP system using a combination of system ID, site and customer, addressing the possibility that system IDs repeat across customers. It displays available HANA memory per site after accounting for replicas.
For each host, Rymvard breaks physical memory into an operating-system reserve, memory used by HANA systems, memory allocated but unused, memory reserved for replicas of systems at other sites, and memory still free. Unless a host specifies a different reserve, the default calculation is 10% of the first 64 GiB of physical memory plus 3% of the remainder. System use is based on its 30-day peak, according to the product description.
The tool also turns planned deployments into a quarter-by-quarter memory runway, weighting each planned landscape by its stated probability and including a replica at a second site. If allocations exceed physical memory, the product marks the host as overbooked rather than presenting the excess as negative free capacity. Rymvard says the product runs today and is in early access. It has not published prices; pricing is agreed with early-access partners.
EARLY ACCESS • INDIA • SAP HANA CAPACITY
In-Country SAP in India: A HANA Capacity Planning Checklist
Rymvard says its running early-access tool helps Indian SAP hosting providers plan HANA memory across customer systems, sites, replicas and probability-weighted future deployments. The Mumbai estate is illustrative, not a customer case.
THE PLANNING QUESTION
When will a site run short of memory?
Bring current use, idle allocations, replica commitments and likely deployments into one view—then check every assumption against the provider’s own environment.
What the capacity view brings together
Planning goes beyond memory currently consumed by production. Rymvard describes a multi-customer view intended to combine site capacity, system usage, allocations and replica needs instead of relying on a separate spreadsheet for each estate.
Distinguish each SAP system
Systems are identified using system ID + site + customer, accounting for system IDs that may repeat across customers.
Show memory by host and site
Physical memory is broken into OS reserve, HANA system use, allocated but unused memory, replica reserves and remaining free capacity.
Model possible deployments
Planned landscapes are weighted by stated probability and translated into a quarter-by-quarter runway, including a second-site replica.
Host memory: inspect every allocation
The product description says system use is based on each system’s 30-day peak. Unless a host specifies otherwise, the OS reserve defaults to 10% of the first 64 GiB of physical memory plus 3% of the remainder.
Bars illustrate categories only; they do not represent measured proportions. If allocations exceed physical memory, Rymvard marks the host as overbooked rather than showing negative free capacity.
Forecast flow: from pipeline to runway
A probability-weighted plan can help teams see when a site may approach its capacity limit. The forecast depends on the assumptions entered for each planned landscape and replica.
Set system baseline
Use each system’s reported 30-day peak memory.
Add commitments
Count used memory, idle allocations and replica reservations.
Weight the pipeline
Enter planned landscapes and their stated probabilities.
Review each quarter
Check site runway and any host flagged as overbooked.
Regulatory context, stated narrowly
The Reserve Bank of India circular dated 6 April 2018 says the entire data relating to payment systems must be stored in a system only in India. Its stated scope is payment-system data; it should not be read as a general mandate covering every enterprise SAP workload.
In-country SAP hosting may also reflect enterprise or provider requirements. The Mumbai example does not establish a customer, actual capacity constraint or deployment outcome.
“The entire data relating to payment systems must be stored in a system only in India.”
Regulatory context cited for interest in in-country hosting. Scope: data relating to payment systems.
Customer results remain unreported
Rymvard has not identified a customer using the product or provided results from a live customer estate. The Mumbai scenario is explicitly illustrative and does not confirm actual constraints, deployments or outcomes at a named provider.
The available description does not include independent validation of memory calculations, how probability estimates are set, performance comparisons, integrations or operational support details.
Evidence to watch for
Whether early-access partners use the tool on live estates; published deployment details or customer outcomes; clearer product and support information; and independent assessment of capacity assumptions and replica accounting.
Key questions
What does the product do?
It models SAP HANA memory across customer systems and sites, including current use, idle allocations, replicas and probability-weighted planned landscapes.
Is the Mumbai example a customer case?
No. Rymvard describes the provider scenario as illustrative; it implies no customer, site or outcome.
What does the RBI circular require?
Its 6 April 2018 circular says payment-system data must be stored only in India. That does not necessarily cover every SAP workload.
Is it generally available, and what does it cost?
Rymvard says the product is running in early access. Pricing is agreed with partners; no general release date or prices have been published.
Planning HANA Capacity Across Sites
For hosting providers, capacity decisions involve more than the memory currently consumed by production systems. Providers must also account for allocated but idle capacity, replica requirements and new customer landscapes that may or may not proceed. Bringing those figures together can help teams identify when a site may run short of memory and how planned deployments could affect the timeline.
Rymvard’s approach is relevant to providers serving customers that want SAP systems hosted in India, but the product description does not establish that every SAP workload is subject to the RBI payment-data rule. The distinction matters: the Reserve Bank of India’s 2018 circular addresses data relating to payment systems. Any broader decision to host SAP systems in-country is an enterprise or provider requirement, not a claim that the circular applies to all SAP data.
The planning view may help providers compare capacity across sites, particularly when a second-site replica is part of the design. However, the stated features and example do not demonstrate measured savings, improved reliability or results from a live customer estate. Those outcomes remain to be established through use.
Products Worth Considering
Apple MacBook Air 13.6-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Midnight
Samsung Galaxy Tab S7 11-inch Android Tablet 128GB Wi‑Fi with S Pen Mystic Black
Sony WH-1000XM5 Premium Noise Cancelling Wireless Headphones – Midnight Blue
As an affiliate, we earn on qualifying purchases.
India’s Payment-Data Storage Rule
The Reserve Bank of India’s circular, dated 6 April 2018, says that the entire data relating to payment systems must be stored in a system only in India. That requirement is the regulatory backdrop cited for interest in in-country hosting. Its stated scope is payment-system data; it should not be read here as a general mandate covering every enterprise SAP system.
Rymvard presents the product as a response to capacity-planning complexity for in-country SAP hosting providers managing multiple customer landscapes. Its example uses a provider in Mumbai, but the company says no customer, site or outcome is implied. The screens come from the running product and an illustrative estate, rather than a customer case study.
“The tool turns the pipeline of planned landscapes, weighted by probability, into a memory runway per quarter.”
— Rymvard
Customer Results Remain Unreported
Rymvard has not identified a customer using the product or provided results from a live customer estate. The Mumbai scenario is explicitly illustrative, so it does not confirm actual capacity constraints, deployments or outcomes at a named provider. The company also has not disclosed pricing, the number of early-access partners or a broader commercial availability date.
The available description does not provide independent validation of the memory calculations, details on how probability estimates are set, or performance data comparing the tool with existing planning methods. It is also unclear how the product handles differences in workload patterns beyond using each system’s 30-day peak, or what integrations and operational support are available.
Early-Access Use Will Test the Model
The next evidence to watch for is whether early-access partners use Rymvard on live estates and whether the company publishes details on deployments, product capabilities or customer outcomes. Rymvard says pricing is agreed individually with those partners and invites inquiries at contact@rymvard.com; it has not announced a general release timeline.
Until customer deployments or independent assessments are described, the product’s demonstrated scope is its running software and illustrative planning scenario. The next step for providers considering it is to verify how its capacity assumptions, replica accounting and planned-landscape forecasts fit their own environments.
Primary source: Reserve Bank of India · via Rymvard
Key Questions
What does Rymvard’s product do?
It models SAP HANA memory capacity across customer systems and sites, including current usage, allocated but unused memory, replicas and probability-weighted planned landscapes.
Is the Mumbai example based on a real customer?
No. Rymvard describes the Mumbai provider scenario as illustrative and says it does not imply a customer, site or outcome.
What does the RBI circular require?
The 6 April 2018 circular says that all data relating to payment systems must be stored in a system only in India. That stated requirement concerns payment-system data, not necessarily every SAP workload.
Is Rymvard generally available, and what does it cost?
Rymvard says the product is running in early access. It has published no prices and says pricing is agreed with early-access partners; a general release date has not been provided.
Primary source: Reserve Bank of India · via Rymvard
