SAP HANA Database Licensing Explained: Runtime vs Full-Use and Costs

Why SAP HANA Licensing Is Uniquely Complex

SAP HANA is both a database platform and an application runtime — it underpins virtually every modern SAP product including S/4HANA, SAP BW/4HANA, SAP Analytics Cloud, and the Business Technology Platform (BTP). SAP's commercial model ties HANA database entitlements tightly to the application licences you purchase, but the scope of what each HANA licence type permits diverges significantly depending on how your organisation uses the database.

Many organisations discover after an SAP audit that their HANA installation has been running workloads — custom applications, third-party data warehouses, or developer sandboxes — that fall outside the scope of their contracted Runtime licence. The financial exposure from such gaps can reach millions of dollars, particularly when SAP calculates back-charges from the date the out-of-scope usage commenced.

SAP HANA Runtime Licence: What It Is and What It Covers

The SAP HANA Runtime licence is a restricted-use database licence that authorises the use of HANA exclusively as the underlying database for specific, named SAP applications. If you purchase S/4HANA, the Runtime licence allows you to run HANA in support of S/4HANA — and only S/4HANA. The licence is bundled into or priced as a derivative of your application licence value.

What a Runtime Licence Permits

• Running the HANA database instance to support the named SAP application
• Creating and managing database objects required by the licensed SAP application
• Using SAP-provided database tools, management utilities, and backup systems
• Replication of data within the SAP application scope using SAP-provided tools

What a Runtime Licence Prohibits

• Running non-SAP applications on the same HANA instance
• Direct third-party application access to HANA via JDBC, ODBC, or direct SQL connections
• Creating custom schemas outside the SAP application namespace
• Using HANA as a general-purpose data warehouse or analytics platform
• Developer or testing workloads that do not relate to the licensed SAP application

Runtime Licence Pricing

The Runtime licence is typically priced as approximately 15% of the net licence value of the SAP application it supports. If your S/4HANA application licence package has a net value of $2,000,000, the HANA Runtime licence component would be priced at approximately $300,000 as a one-time perpetual fee. Annual support on the Runtime licence follows SAP's standard support rate of approximately 22% of net licence value per year — adding approximately $66,000 in annual recurring cost in this example. In the context of migrating to S/4HANA or RISE with SAP, the licence baseline change affects how this Runtime valuation is calculated, and buyers should model the full support cost impact before committing to a migration deal.

SAP HANA Full-Use Licence: What It Allows

The SAP HANA Full-Use licence is an unrestricted database licence that authorises HANA deployment for any purpose — SAP applications, non-SAP applications, custom analytics platforms, and third-party integration hubs. It removes all the use restrictions inherent in the Runtime licence and is the appropriate choice for organisations that intend to use HANA as a platform beyond the SAP application suite.

Full-Use Licence Capabilities

• Running both SAP and non-SAP applications on the same HANA instance
• Direct third-party application connectivity via standard database interfaces
• Custom schema creation and management across the database
• Using HANA as an enterprise data warehouse, analytics engine, or IoT data platform
• Developer and testing environments for non-SAP applications

Full-Use Licence Pricing

Full-Use licences are priced on a memory-capacity basis. The standard pricing model is per 64 GB of RAM block, with list prices in the range of $50,000 or more per block. A HANA instance provisioned with 256 GB of RAM would require four 64 GB blocks, resulting in a list price of approximately $200,000 for the Full-Use licence before negotiation. SAP offers limited discount flexibility on Full-Use licences compared to application licences, typically in the range of 20–30% below list. Annual support is charged at approximately 22% of net licence value, adding approximately $30,000–$44,000 per year for a 256 GB configuration at negotiated prices.

Full-Use pricing scales with memory, meaning organisations that expand their HANA footprint — adding nodes, increasing RAM, or deploying in-memory analytics across a larger dataset — face proportionally higher licence costs. This memory-linked pricing model requires careful capacity planning before deployment.

The Compliance Risk: When Runtime Becomes Full-Use

The compliance exposure in SAP HANA licensing typically arises not from deliberate misuse, but from the organic expansion of what teams do with the HANA platform. A common audit finding pattern looks like this: an organisation licenses HANA for S/4HANA (Runtime), the Basis team connects a third-party reporting tool to HANA for operational convenience, developers create custom schemas for testing and prototyping, and a data analytics team starts using HANA as a staging layer for their data lake pipeline. None of these decisions felt like a licence violation when made — each solved an immediate operational problem. But collectively they convert a Runtime-licensed instance into one that required a Full-Use licence from the moment the first out-of-scope connection was established.

SAP's audit methodology specifically targets this pattern. Auditors examine RFC connections, ODBC/JDBC logs, and schema ownership records in HANA. The presence of non-SAP schemas or third-party application connection credentials is treated as evidence that the Full-Use licence is required — and claims are typically back-dated to the earliest evidence of out-of-scope use.

The HANA Audit Claim Mechanism

When SAP constructs an indirect access or licence underage claim related to HANA, the methodology combines the number of 64 GB memory blocks in use (capacity metric) with the list price for Full-Use licences, less any credit for existing Runtime licences already paid. The resulting claim is often presented as a retroactive licence fee plus annual support back-charges, framed as the cost of converting the Runtime licence to Full-Use from the point of first non-compliant use. This retroactive calculation can be financially devastating — an organisation that has been running out-of-scope workloads on a 1 TB HANA instance for three years may face a claim exceeding $1 million before negotiation.

Migration and S/4HANA Licence Baseline Implications

When organisations migrate from SAP ECC to S/4HANA, the licence baseline changes. S/4HANA uses a different user metric framework and the HANA Runtime licence parameters are recalculated against the new application licence value. This migration creates two common licence issues. First, if the negotiated S/4HANA licence value is lower than the ECC baseline (a common outcome of well-structured migration negotiations), the implied Runtime licence value also decreases — which is positive. Second, if migration introduces additional HANA use cases (embedded analytics, Fiori apps accessing HANA directly, or BTP-based extensions connecting to HANA), those new use cases may require Full-Use coverage that was not modelled in the migration cost.

Buyers who are in active S/4HANA migration discussions should explicitly scope their HANA licence requirements — Runtime versus Full-Use — as part of the commercial negotiation, not as an afterthought following implementation go-live.

Optimisation Strategies

Organisations with existing HANA deployments can take several steps to reduce exposure and optimise their licensing position.

• Inventory all HANA connections: Document every application, tool, and process that accesses your HANA instance. Classify each as within or outside the scope of your Runtime licence.
• Isolate out-of-scope workloads: Move non-SAP workloads to a separate HANA tenant or instance, which can be licensed under Full-Use while keeping the primary SAP application instance on Runtime. This architectural separation can substantially reduce Full-Use licence fees by containing the memory footprint of the out-of-scope workload.
• Evaluate HANA Cloud alternatives: For analytics and non-SAP workloads, SAP HANA Cloud (the SaaS version) offers consumption-based pricing that may be more cost-effective than on-premise Full-Use licences for variable or non-production workloads.
• Negotiate at the right moment: If your organisation is already in discussions about S/4HANA migration, RISE with SAP, or an ELA, use that commercial moment to address HANA licence scope proactively. SAP is more likely to provide favourable Full-Use conversion pricing as part of a broader deal than when approached reactively after an audit.