🔍 Read the full analysis: In-Country SAP In India: Planning HANA Capacity Under Payment Data Rules on Rymvard
Get the latest gadgets 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 is offering an early-access tool to help in-country SAP hosting providers plan HANA memory across customer landscapes and sites. Its example models system usage, reserved memory, replicas and probability-weighted future demand; it is an illustrative scenario, not a reported customer deployment or outcome.
Rymvard says its SAP capacity-planning product is running in early access, with tools for Indian hosting providers to model HANA memory across customer systems and sites. The product is designed for providers planning in-country infrastructure amid payment-data storage requirements, but the Mumbai example Rymvard presents is illustrative, not a customer case.
The product addresses a planning problem that can grow as providers host more SAP landscapes within India: deciding how much HANA capacity is available now and what future demand could require. Rymvard says a separate spreadsheet for each customer becomes difficult to manage, particularly because SAP system IDs can repeat across customers. Its product identifies each system using the system ID together with its site and customer.
For each HANA host, the tool separates physical memory into categories: an operating-system reserve, memory used by HANA systems, memory allocated but not currently used, memory held for replicas of systems at other sites, and memory that remains free. Rymvard says system usage is based on the 30-day peak. Its default operating-system reserve is 10% of the first 64 GiB and 3% of the remainder, unless a host has a different reserve declared.
Rymvard says the product displays overbooking when allocations exceed physical memory rather than concealing it as negative free capacity. It also models planned landscapes using their assigned probabilities to produce a quarter-by-quarter memory runway, including the replica required at a second site. The company says the screens are from its running product, but the estate shown is illustrative and does not represent a customer.
Infrastructure briefing · India · Early access
In-Country SAP in India: Planning HANA Capacity Under Payment Data Rules
Rymvard says its early-access tool helps Indian hosting providers plan HANA memory across customer landscapes and sites. Its Mumbai estate is an illustrative scenario—not a reported customer deployment or outcome.
01 / Host memory map
What counts against capacity?
A provider needs to see more than active production use. Rymvard’s model separates the main claims on each HANA host so that allocated capacity and replica obligations remain visible.
Operating system
Default reserve: 10% of the first 64 GiB, then 3% of the remainder, unless the host declares another reserve.
HANA systems
System usage is based on the 30-day peak, according to Rymvard.
Unused allocation
Memory assigned to systems but not currently used remains a distinct category.
Replica memory
Capacity held for replicas of systems hosted at other sites is included.
Free capacity
Remaining physical memory is shown, with overbooking made visible when allocations exceed the host.
02 / Planning flow
From host inventory to a quarterly runway
The product models current memory categories alongside planned landscapes. Probability weights shape a quarter-by-quarter view of possible demand, including a required replica at a second site.
Identify systems
Match each system using its ID, customer and site.
Map host memory
Separate reserve, usage, idle allocation, replicas and free space.
Weight planned demand
Include prospective landscapes using assigned probabilities.
Review runway
Inspect projected quarter-by-quarter memory needs across sites.
+ 3% × remaining memory
Rymvard says a host-specific declared reserve can replace this default. Allocations beyond physical memory are displayed as overbooking.
Demand runway by quarter
Conceptual view only. No customer measurements or forecast values are published in the supplied details.
03 / Regulatory context
What India’s payment-data rule says
The regulatory backdrop is the Reserve Bank of India circular dated 6 April 2018 on storage of payment system data. Its stated scope matters when interpreting the in-country hosting context.
Payment system data
The circular requires the entire data relating to payment systems to be stored in a system only in India.
Not every SAP workload
The circular does not, by itself, establish that every SAP system or all enterprise data must be hosted in-country.
“The entire data relating to payment systems is to be stored in a system only in India.”Reserve Bank of India circular · 6 April 2018
04 / Evidence and limits
What is known—and what remains unreported
The screens are described as coming from a running product, but the estate shown is illustrative. That distinction limits what can be concluded about customer use or business impact.
Early-access product
Tools for modeling HANA memory and replica requirements across Indian hosting sites.
Mumbai provider scenario
No customer, site or business outcome is implied by the example estate.
Deployment evidence
No named provider, customer deployment, measured result or number of early-access partners is identified.
Release and forecast detail
No general availability date, public price list, independent estimate validation or method for setting probability weights is provided.
05 / Key questions
Quick answers for providers
What does the RBI circular require?
It requires the entire data relating to payment systems to be stored in a system only in India. The available details do not say that every SAP workload or all enterprise data is covered.
What does Rymvard’s product calculate?
It categorizes HANA host memory—including usage, OS reserves, unused allocations, replica requirements and free capacity—and models probability-weighted planned landscapes by quarter.
Is the Mumbai example a live customer deployment?
No. Rymvard describes the Mumbai provider scenario and estate as illustrative; it says the screens do not come from a customer.
Is the product generally available, and what does it cost?
Rymvard says it is in early access. Prices are agreed with early-access partners, and no general release date or public price list has been provided.
Primary source: Reserve Bank of India · Product details via Rymvard
Planning HANA Capacity Across Sites
For a hosting provider, capacity planning has to account for more than the memory currently consumed by production systems. Allocated but unused memory, operating-system reserves and replicas can all affect how much capacity is genuinely available to accept another landscape. Showing these categories separately may help teams spot a shortage earlier than a plan that counts only active usage.
The multi-customer view also addresses an operational complication: a system ID alone may not uniquely identify an SAP system across an entire provider’s estate. Rymvard’s combination of system ID, site and customer is intended to distinguish those systems while enabling a provider to review memory at each site. Its probability-weighted pipeline view is a planning aid, however, not a guarantee that prospective workloads will arrive as forecast.
The distinction matters for providers deciding when to add HANA capacity or where to place replicas. The product’s model can make assumptions and potential overbooking visible, but the available information does not establish that it has reduced costs, prevented outages or improved capacity decisions for a live customer.
SAP HANA memory capacity planning tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
India’s Payment-Data Storage Rule
The regulatory backdrop is the Reserve Bank of India’s circular dated 6 April 2018 on storage of payment system data. The circular requires that the entire data relating to payment systems be stored in a system only in India. That requirement concerns payment system data; it does not, by itself, establish that every SAP system or all enterprise data must be hosted in-country.
Rymvard describes Indian enterprises as seeking in-country hosting for SAP systems and says this is increasing the number of landscapes providers need to plan. The circular supplies relevant context for providers building domestic infrastructure, but the product’s example is specifically a hypothetical in-country provider in Mumbai. Rymvard says no customer, site or business outcome is implied by that scenario.
The company has not published prices. It says pricing is agreed with early-access partners, and it invites interested organisations to contact it directly. The product’s availability is therefore described as early access rather than a broadly priced commercial release.
““Rymvard is in early access.””
— Rymvard
Customer Results and Release Plans
No customer deployment, measured result or named hosting provider is identified in the available details. The Mumbai estate is explicitly illustrative, so it cannot be treated as evidence that the product has been used to plan a real customer environment or that its forecasts have matched actual demand.
Rymvard has not specified how many early-access partners are using the product, when general availability might begin, or what prices partners pay. The company also does not provide independent validation of its memory estimates or explain how providers should set probability weights for planned landscapes. Those inputs can affect a runway forecast, and the information provided does not say how uncertainty in them is quantified.
The circular’s requirement applies to payment system data. The details here do not establish that it requires all SAP workloads or all enterprise information to remain in India, nor do they describe how a particular organisation determines whether its SAP environment contains data covered by the rule.
Early-Access Partner Discussions
Rymvard says early-access partners can discuss pricing directly with the company; no public price list or release timetable is available. The next concrete indicators will be whether the company announces general availability, identifies production deployments, or provides customer results showing how its capacity estimates compare with observed HANA usage and replica requirements.
Until such details are available, the product should be understood as a running early-access planning tool presented through an illustrative estate. Providers considering it would need to assess its assumptions against their own host configurations, allocation practices, replica policies and demand forecasts.
Primary source: Reserve Bank of India · via Rymvard
Key Questions
What does the RBI circular require?
The 6 April 2018 circular requires the entire data relating to payment systems to be stored in a system only in India. The details here do not say that every SAP workload or all enterprise data is covered.
What does Rymvard’s product calculate?
It categorizes HANA host memory, including system usage, operating-system reserves, unused allocations, replica requirements and free capacity. Rymvard says it also models probability-weighted planned landscapes by quarter.
Is the Mumbai example a live customer deployment?
No. Rymvard describes the Mumbai provider scenario and estate as illustrative and says the screens do not come from a customer.
Is the product generally available, and what does it cost?
Rymvard says the product is in early access. It has not published prices, saying pricing is agreed with early-access partners, and has not provided a general release date.
Primary source: Reserve Bank of India · via Rymvard
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
