SAP HANA 2.0 is the current on-premise and private-cloud generation of SAP's in-memory database and application platform. It underpins SAP S/4HANA, SAP BW/4HANA and a wide range of custom and partner workloads, and it uses a per-support-package-stack (SPS) maintenance model rather than a single platform-wide end date — a distinction that materially changes how customers should track it.
It became generally available on 1 December 2016. SAP mainstream maintenance runs until 30 November 2028 — the date from which SAP ceases routine corrections, security notes and legal/regulatory updates for the release. Crucially, SAP offers no extended-maintenance phase for this release, so the mainstream date is a hard cut-off rather than the start of a paid extension — there is no buying of extra time at the version level. That leaves a workable but finite window; given that SAP transformations routinely run multi-year, scoping and budgeting should be underway rather than deferred.
The cloud-strategic successor is SAP HANA Cloud, the managed service generation. On-premise customers stay current primarily by moving across HANA 2.0 SPS levels under SAP's revision and maintenance strategy; the platform-edition date provides an outer boundary, but the date that actually governs a given system depends on the specific SPS it runs.
Database and Basis teams should track the SPS they operate against SAP's HANA 2.0 maintenance strategy rather than assuming one platform-wide deadline, and should factor SAP HANA Cloud into longer-term plans. Because the database sits beneath almost every other SAP workload, its currency is a prerequisite for the supportability of everything running on top of it.
Independent reference tool. Not affiliated with, endorsed by, or sponsored by SAP SE. Product names are referenced as plain text for identification only. Always confirm dates against SAP's official Product Availability Matrix and your support contract.