The definitive CIO playbook for understanding SAP HANA licensing models: runtime versus full-use rights, memory-based pricing, cloud transitions, compliance risks, and cost optimisation strategies.
This is a pillar guide in the SAP HANA licensing series. Related: S/4HANA Licensing Migration Paths | RISE vs On-Premise Licensing | S/4HANA and HANA Licensing Guide.
SAP HANA is the in-memory database at the heart of every modern SAP system. Any organisation adopting S/4HANA, BW/4HANA, or SAP's next-generation platforms must run them on HANA, making database licensing a critical cost and compliance consideration. The choice between runtime and full-use can mean the difference between a $150,000 database licence and a $600,000+ investment for the same environment.
A HANA runtime licence is a cost-effective way to licence the HANA database exclusively for SAP applications. It is valid only when HANA serves as the underlying database for SAP software such as S/4HANA, BW/4HANA, SAP Business Suite, or other SAP products. Priced at approximately 15% of the SAP application's licence cost. For example, an S/4HANA software package purchased for $1,000,000 would carry a HANA runtime database licence of roughly $150,000 as a one-time fee. Annual support fees (approximately 22%) apply on top.
| Runtime Restriction | Detail |
|---|---|
| No custom applications | Cannot build custom applications that directly query HANA tables |
| No third-party BI tools | Cannot connect Tableau, Power BI, Python scripts, or other tools directly to the HANA database |
| No custom schemas | Cannot create custom schemas or load external data into HANA outside the SAP application |
| No non-SAP workloads | Cannot run any non-SAP workloads on the same HANA instance |
If your HANA usage is confined to standard SAP applications, always opt for runtime. Do not let SAP upsell you to full-use "just in case." Implement access controls restricting HANA database credentials to authorised SAP Basis administrators only. Block creation of custom schemas in production environments. Ensure developers and power users understand that direct HANA connections are prohibited under runtime licensing. A common compliance trap occurs when a developer connects a data visualisation tool directly to HANA because it is technically straightforward, not realising it violates the licence.
A HANA full-use licence unlocks the complete platform with no usage restrictions. HANA can serve as the database for SAP applications and for any other applications, custom developments, or third-party tools. Licensed per 64 GB memory block at approximately $50,000+ per block list price. A 256 GB instance requires 4 blocks at roughly $200,000 list. Larger environments easily reach seven figures. SAP offers limited discounting on HANA full-use compared to application licences.
| Full-Use Trigger | Detail |
|---|---|
| Custom applications on HANA | Building custom applications that run on HANA for high-performance needs |
| Consolidated data platform | Using HANA to pull data from non-SAP systems for real-time analytics |
| Third-party software on HANA | Running third-party software on the HANA instance |
| External BI tools | Connecting external BI tools directly to the HANA database (Tableau, Power BI, etc.) |
| Consolidated multi-product instance | Running multiple SAP products on a single HANA instance (runtime generally cannot cover this) |
| Aspect | HANA Runtime Licence | HANA Full-Use Licence |
|---|---|---|
| Allowed usage | SAP applications only. No third-party or custom direct use | Any application: SAP, third-party, or custom with no restrictions |
| Pricing model | Approximately 15% of SAP application licence value (one-time) | Per 64 GB memory block (approximately $50K+ per block list) |
| Upfront cost | Lower: fraction of full-use | Significantly higher: scales with memory |
| Annual support | Approximately 22% of runtime licence fee | Approximately 22% of full-use licence fee (higher absolute amount) |
| Scalability | Not tied to specific GB: grows with SAP app usage | Explicitly memory-sized: must purchase more blocks as data grows |
| Ideal use case | SAP-only environments (ERP, BW) | Mixed: SAP + custom apps, analytics, third-party tools |
| Upgrade path | Can convert to full-use (pay the delta) | Already unrestricted |
A technology company needing 512 GB for S/4HANA plus custom real-time analytics and IoT data required full-use licensing: 8 x 64 GB blocks at approximately $400,000 list, roughly 2.7x more than runtime for the S/4HANA system alone. The flexibility is genuine but so is the cost. Start with runtime and convert later if genuinely needed.
| Scenario | Detail |
|---|---|
| S/4HANA on-premise | HANA runtime is almost always most cost-effective unless concrete plans for non-SAP workloads exist. Runtime licence is tied to that specific S/4HANA environment. A separate BW/4HANA system requires its own runtime licence |
| BW on HANA / BW/4HANA | Runtime licence restricted to BW workloads. Running BW and S/4 on the same HANA database may require full-use. Mixing workloads or custom BW-based data marts may push towards full-use |
| Non-SAP and custom applications | The single most common compliance trap. Any time you use HANA for something other than an SAP application, you need full-use. Even a third-party tool reading S/4HANA tables via direct HANA connection (bypassing SAP interfaces) counts as unlicensed under runtime |
| Cloud: BYOL vs pay-as-you-go | BYOL reuses existing licence on cloud VM (same terms, different hardware) and is more cost-effective for steady production. Pay-as-you-go includes licensing in hourly rate, convenient for prototyping but substantially more expensive long-term |
| RISE with SAP | HANA database delivered as part of subscription: no separate licence. Existing on-premise licences become potential shelfware. Always negotiate trade-in credit. SAP HANA Cloud (BTP) is an entirely separate subscription: on-premise licences do not carry over |
| Strategy | Detail |
|---|---|
| Choose runtime whenever feasible | If HANA usage is confined to standard SAP applications, always opt for runtime. Cost difference is substantial: often 3-4x lower than full-use. Start with runtime; you can upgrade later if genuinely needed |
| Right-size your memory | For full-use, memory equals cost. Use SAP's sizing tools and conservative growth projections. Do not over-size with a large safety cushion. Every unnecessary 64 GB block is real money wasted. Purchase additional capacity later; you cannot refund unused licensed capacity |
| Implement data tiering and archiving | Not all data needs expensive in-memory storage. Use HANA Native Storage Extension (NSE), warm/cold data tiering, and aggressive archiving. Archiving five-year-old transactional data could save you from licensing an additional 128 GB block, potentially $50,000+ saved per year in support |
| Negotiate future growth upfront | Lock in pricing for future memory expansions. If anticipating doubling capacity in 2-3 years, negotiate the option to purchase additional blocks at the same discount rate. Without this, SAP may charge list price when you have less leverage. Large S/4HANA migration deals are the ideal moment |
| Monitor usage continuously | Use SAP system measurement tools, HANA cockpit views, and SQL queries to track memory consumption and connected users. Early detection of compliance issues (unauthorised schema, rogue BI connection, memory creeping past licensed amount) allows remediation before audit pressure |
| Leverage SAP programmes and bundles | SAP periodically offers promotions: free runtime for legacy migrations, bundle pricing for S/4HANA + HANA + BTP, conversion credits. Always decompose bundle pricing to confirm genuine value rather than hidden costs |
It is not choosing the wrong model. It is failing to enforce the boundaries of the model you chose. A runtime licence that quietly acquires third-party connections costs far more to remediate in an audit than a proactively licensed full-use environment.
SAP audit tools and system measurement scripts detect: memory installed versus licensed (for full-use), unauthorised users/schemas/connections (indicating non-SAP usage on runtime), and features used beyond licence edition scope.
| Compliance Risk | Consequence |
|---|---|
| Memory overage on full-use | Must purchase additional 64 GB blocks retroactively plus back-dated maintenance fees for the period of non-compliance |
| Unauthorised usage on runtime | SAP may require full conversion to full-use licensing: an unplanned expense that can reach hundreds of thousands of dollars |
| Case Study: Manufacturing Firm | Detail |
|---|---|
| Situation | Manufacturer runs S/4HANA on HANA runtime licence. A data analyst connects Tableau directly to the HANA database for executive dashboards. Technically straightforward but contractually prohibited |
| Audit discovery | SAP system measurement detects external schema and user created for Tableau. Audit team classifies this as unlicensed full-use consumption |
| Result | Must purchase full-use licence for entire instance (approximately $400K) plus back-maintenance for 18 months of non-compliant usage (approximately $132K). Total unplanned spend: over $530,000 |
| Takeaway | Implement governance controls preventing direct HANA connections under runtime licensing. Education and access restrictions are far cheaper than audit remediation |
| Transition Path | Detail |
|---|---|
| RISE with SAP | RISE includes HANA as part of subscription. Existing on-premise licences become unused assets unless you negotiate trade-in credits. You may continue paying maintenance on idle licences unless actively terminated. Always negotiate credit for existing investment |
| BYOL to hyperscaler cloud | Reuse existing licences on AWS, Azure, or GCP VMs. Licence is not hardware-bound: as long as cloud VM is HANA-certified, entitlement carries over. Maximises existing investment whilst gaining cloud flexibility |
| SAP HANA Cloud (BTP) | On-premise licences do not carry over. If adopting BTP-based HANA, negotiate conversion rights or cloud credits during transition deal to avoid paying twice for database capability |
Track which HANA licences are actively deployed versus idle. Terminate maintenance on genuinely unused licences. When discussing RISE, insist on credit for existing HANA licence investments. Negotiate a clause allowing you to resurrect on-premise licences if you later decide to insource or move off SAP's cloud.
Generally, yes. HANA runtime licensing is tied to each SAP product environment. Separate systems for S/4HANA and BW/4HANA each require their own runtime licence. You cannot use one runtime licence for two different SAP products simultaneously. Non-production (dev/test) systems are typically covered under your production licence but always verify specific contract terms. The only scenario where a single licence covers multiple systems is full-use licensing on a consolidated instance with sufficient memory.
On full-use, exceeding purchased memory capacity puts you out of compliance. You must purchase additional blocks to cover the overage. If discovered during audit, SAP will typically backdate maintenance fees to when the overage began. It is far better to monitor proactively and licence up before an audit forces the issue. On runtime, there is no explicit memory cap, but SAP may question extremely large database growth inconsistent with normal SAP application usage.
Not for all, but for major current-generation products, yes. S/4HANA runs exclusively on HANA. Unlike predecessor SAP ECC, you cannot use Oracle, DB2, or SQL Server. BW/4HANA similarly requires HANA. Some SAP products still support other databases (e.g. SAP Business One on SQL Server), but if adopting SAP's modern ERP and analytics solutions, HANA is mandatory.
Yes. SAP typically lets you convert by crediting the original runtime licence fees towards full-use (you pay the delta). For example, $200K runtime and $600K full-use for the same scenario means approximately $400K for the upgrade. Anticipate this need early and negotiate conversion terms as part of your original deal while you have maximum leverage. Do not begin using HANA beyond runtime rights until you have officially completed the licence conversion.
In RISE, SAP provides the HANA database as part of the subscription service. You do not separately deal with a HANA licence. The subscription covers database usage with restrictions similar to runtime (no free access to raw database). Existing on-premise licences are not consumed by RISE and may become shelfware unless you negotiate trade-in credits. On-premise licences cannot be converted to SAP HANA Cloud credits: these are entirely separate constructs.
Redress Compliance provides independent, vendor-neutral advisory on SAP licensing: HANA model selection, cost optimisation, audit defence, and contract negotiation. 100% vendor-independent. Fixed-fee engagement.
SAP Advisory ServicesIndependent SAP advisory. HANA model selection. Runtime vs full-use analysis. Audit defence. 100% vendor-independent, fixed-fee engagement.