🔍 Read the full analysis: How To Plan HANA Capacity For In-Country SAP Hosting In India on Rymvard

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

Get office and shipping supplies 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.Hide

TL;DR

Rymvard says its early-access product models SAP HANA capacity across customer landscapes and hosting sites, including system replicas and projected demand. Its Mumbai example is illustrative, not a customer deployment; the company has not published pricing or customer outcomes.

Rymvard says its early-access product helps SAP hosting providers in India plan HANA memory across customer systems, hosting sites and required replicas. The company’s example models an illustrative Mumbai provider estate; it is not evidence of a customer deployment or a verified capacity-planning outcome.

The product addresses a planning problem that can arise as providers add SAP landscapes faster than new hardware can be delivered. Tracking each customer in a separate spreadsheet can make capacity difficult to compare across sites, while SAP system IDs may repeat between customers. Rymvard says its tool identifies each system using its system ID, site and customer, then reports free HANA memory at each site after accounting for replicas.

For each HANA host, Rymvard divides physical memory into an operating-system reserve, memory used by HANA systems, allocated but unused capacity, memory reserved for replicas hosted on that site, and memory that remains free. System use is based on the 30-day peak, according to the company. Its default operating-system reserve is 10% of the first 64 GiB of physical memory and 3% of the remainder, unless a host has a separately declared reserve.

The planner also uses a provider’s pipeline of prospective landscapes, weighted by their stated probability, to estimate a quarter-by-quarter memory runway. That projection includes the replica a landscape would need at a second site. If allocations exceed physical memory, the product shows the overbooking rather than masking it as a negative free-memory figure, Rymvard says.

Forecasting HANA Demand Across Sites

For an in-country hosting provider, a capacity decision involves more than the memory currently occupied by production systems. Providers also need to account for systems allocated but not yet using their full capacity, replicas at another site, and prospective customer environments that may or may not proceed. A forecast that separates these categories can make potential shortfalls visible before a provider commits to additional landscapes or hardware.

The approach may help operators compare projected demand with available memory on a site-by-site basis, while making assumptions such as pipeline probability and replica requirements visible. It does not, by itself, establish that a provider will avoid outages, reduce costs or improve utilisation. Rymvard has supplied no customer results or independent performance evidence, and its illustrated estate is explicitly not a customer example.

India’s Payment Data Storage Rule

The Reserve Bank of India issued its circular on storage of payment system data on 6 April 2018. The circular requires payment-system data to be stored in a system only in India. That requirement applies to the payment-system data covered by the circular; it should not be read as a blanket rule that every SAP system or all enterprise data must be hosted domestically.

Rymvard describes Indian enterprises as increasingly seeking in-country SAP hosting, and frames its product around the capacity challenges providers may face as they add landscapes. The company says the screens come from a running product and use an illustrative Mumbai estate. Rymvard is in early access, and it says pricing is agreed with early-access partners rather than published publicly.

““The 30-day peak””

— Rymvard

Customer Results and Rollout Remain Unknown

No customer deployment, named hosting provider or measured outcome is identified in the available product description. Rymvard says the Mumbai scenario is illustrative and does not imply a customer, site or result. The company has not provided benchmarks showing how accurately its forecasts predict actual demand, or whether using the tool changes hardware purchases or service performance.

Further details about the product’s integrations, supported SAP configurations, data inputs and controls are also not specified. The RBI circular concerns payment-system data within its scope; the material does not establish that the circular itself requires all SAP workloads to be located in India. Pricing is not public, with terms agreed directly with early-access partners.

Early Access and Product Validation

Rymvard says the product is running and is available through an early-access partner arrangement. The company directs interested parties to contact@rymvard.com and says it agrees pricing with partners. No public timetable for general availability, customer rollout or independent validation has been announced.

The next useful evidence would be deployments identified as customer examples, along with details on how forecasts compare with actual HANA memory use over time. Until then, the Mumbai scenario should be treated as a demonstration of the product’s planning method, not a report of operational results.

Primary source: Reserve Bank of India · via Rymvard

Key Questions

Does India’s RBI rule require every SAP system to be hosted in India?

No. The 6 April 2018 RBI circular addresses storage of payment-system data covered by the rule. It does not establish a general requirement that every enterprise SAP system be hosted in India.

What does Rymvard’s HANA planner track?

Rymvard says it tracks system memory use, allocated but unused memory, operating-system reserves, replica capacity and free memory across hosts and sites. It identifies systems by system ID, site and customer to distinguish repeated IDs across customers.

How does the tool estimate future capacity needs?

It weights planned customer landscapes by their pipeline probability and projects a quarterly memory runway, including the replica planned at a second site. The accuracy of those estimates has not been independently reported.

Is the Mumbai example a real customer deployment?

No. Rymvard describes it as an illustrative example estate from its running product and says no customer, site or outcome is implied.

Is Rymvard generally available, and what does it cost?

Rymvard says it is in early access. It has not published prices; pricing is agreed with early-access partners.

Primary source: Reserve Bank of India · via Rymvard