Pricing benchmark

What extended support for end-of-life software costs

On 26 Oct 2026 the published prices were: Ubuntu Pro $500 per server a year, TuxCare from $5,000 a year for up to 10 systems, SQL Server 2016 ESU from $278 a month per 2 cores, and AWS RDS Extended Support $0.10 per vCPU-hour. HeroDevs and OpenLogic publish none. OSSeva publishes none; its quote follows technologies, versions, environments and tier.

Third-party prices checked 26 Oct 2026 on each vendor's own page, with sources at the foot of this page. Written by the OSSeva team, which sells a competing service.

Published extended support prices, checked 26 Oct 2026

Seven vendors, five billing units. OSSeva comes first: it has no list price, and a quote follows four things set out below. The other rows are the numbers each vendor prints today, or a plain "not published".

Published extended support prices by vendor, checked 26 Oct 2026
VendorWhat it extendsPublished priceBilling unitPer year, full use
OSSevaSelf-managed open source databases, brokers and runtimes, end-of-life lines includedNot published. A senior engineer replies within 1 business day with a quote.Per cluster for most technologies (how a quote is built)Not published
Canonical Ubuntu ProUbuntu LTS and the packages in the Ubuntu archive$25 per workstation and $500 per server (unlimited VMs) per machine per year. 24/7 support add-on: $1,775 Infra or $3,400 Full per server per year; weekday support is 50% less.Per machine; public cloud is metered by the hour, about 3 to 4.5% of the list price$500 per physical server
Microsoft ESU (Azure Arc)SQL Server 2014 and 2016, Windows Server 2016SQL Server: $1,081 Enterprise or $278 Standard per month per 2 cores. Windows Server 2016: $60 Datacenter or $10.50 Standard per month per 2 cores.Per core, billed monthly; 4-core minimum per SQL Server instanceSQL Server $6,486 or $1,668 per core; Windows $360 or $63 per core
TuxCare (OSSeva vs TuxCare)Linux operating systems and six runtimes (.NET, Node.js, OpenJDK, PHP, Python, Ruby)Sold annually in bands: up to 10 systems $5,000, up to 100 $9,750, up to 250 $23,750. Above that, custom. Its pricing page asks for a custom quote.Per system (physical, VM or cloud instance), or per runtime instanceUp to $500, $97.50 or $95 per system when the band is full
AWS RDS and Aurora Extended SupportRDS for PostgreSQL and MySQL past standard support$0.100 per vCPU-hour in years 1 and 2, $0.200 in year 3 (US East, Ohio). Other Regions cost more.Per vCPU-hour; Multi-AZ standby instances are billed$876 per vCPU, then $1,752
Azure Database for PostgreSQLPostgreSQL 11 to 13 on Azure Flexible Server now, 14 from 1 Feb 2027$0.070 per vCore-hour (East US). Billing for versions 11 to 13 started 1 Sep 2026.Per vCore-hour, running servers only$613.20 per vCore
HeroDevs (OSSeva vs HeroDevs)Never-Ending Support for named application versionsNot published. The page shows Custom Pricing, billed annually, multi-year options.Annual licence per user: people who commit code to the project repositoryNot published
OpenLogic (OSSeva vs OpenLogic)Technical support and long-term support for open sourceNot published. The page offers a quote request only.Not statedNot published

The last column is arithmetic on the published rate for a full year (8,760 hours, or 12 months) and is not a vendor quote. TuxCare bands were read from its checkout by selecting each band; nothing was submitted, and the page prints no per-system rate. Ubuntu Pro prices exclude the cloud-metered option. Amazon ElastiCache, EKS, OpenSearch and Azure AKS are on the cloud extended support pricing page.

The same 50-system estate at each published rate

Take 50 systems of 4 cores or vCPUs each, running all year. This shows how each unit scales, not which vendor is better: the rows cover different software, and some cannot cover the same systems at all.

Annual list price for a 50-system estate by vendor
VendorHow the 50 systems are countedAnnual list price
Ubuntu Pro50 physical servers, subscription only$25,000 (50 x $500)
TuxCare50 systems fall in the up-to-100 band$9,750
SQL Server Standard ESU200 vCores = 100 two-core units x $278 x 12$333,600
SQL Server Enterprise ESU100 two-core units x $1,081 x 12$1,297,200
AWS RDS Extended Support200 vCPUs x $0.10 x 8,760 hours (years 1 and 2)$175,200, then $350,400 in year 3
Azure PostgreSQL200 vCores x $0.07 x 8,760 hours$122,640
HeroDevs, OpenLogicPriced per user, or not statedNot published
OSSevaPer cluster, not per server, core or vCPUNot published; quote on request

Why the spread is so wide: Microsoft and AWS count cores or vCPU-hours, so the bill grows with hardware. TuxCare counts systems in bands. OSSeva counts clusters, so adding cores to a cluster does not change the count. For your own figures, put a quote and your current spend into the database support cost calculator.

What each price buys, and what it does not

Ubuntu Pro

Infra-only coverage is security maintenance for Ubuntu's Main repository for five years beyond standard support. Full coverage adds the Universe repository for up to 10 years, and a Legacy add-on costs 50% more for 15 years in total. It patches what Ubuntu ships, so it is a fit if your databases come from the Ubuntu archive.

Microsoft ESU

Critical security updates only, for up to three years, with no new features and no general technical support. A late subscriber is billed back to the start of the ESU term. SQL Server needs Azure Arc plus Software Assurance or pay-as-you-go; Express, Web and Developer editions cannot be enrolled. SQL Server ESU cost in detail.

TuxCare

The checkout lists SLA-backed CVE patching, compatibility-preserving updates and 24/7 expert support. Its application pages list named versions; see our TuxCare comparison for what they cover and where OSSeva differs.

AWS RDS Extended Support

Charges begin the day after RDS end of standard support, stop when you upgrade or delete the database, and restart if the target version later enters Extended Support. It only covers databases inside RDS and Aurora. RDS Extended Support cost and calculator.

How OSSeva prices extended support

OSSeva does not publish a price. Four things set a quote, and each one is stated in words so you can check a quote against your own estate.

Technologies and units in scope

Most technologies are priced per cluster. Tomcat is per application server, Spring Boot per application and .NET per application runtime environment. Adding capacity to a cluster does not change the count.

Versions you run

Current and end-of-life versions are both covered. Lines upstream no longer fixes need OSSeva's patched builds, so the version mix shapes the backporting work.

Environments

Where the software runs (bare metal, VMs, Kubernetes or your own cloud account) and whether production, staging and disaster recovery clusters are all in scope. OSSeva supports software you run yourself.

Tier

Patch, Assure or Operate. Critical CVEs are patched within 48 hours and High within 7 days on every tier. Assure adds 24/7 reactive support. Operate adds 24/7 monitoring and a 15-minute P1 response.

The full unit list is on the pricing page. A senior engineer replies within 1 business day with a quote.

Extended support or an upgrade?

Every extended support price above is a bridge, and several stop the day you upgrade: the AWS charge ends when the instance runs a version in standard support, and Microsoft cancels ESU billing on upgrade or migration. Run both costs side by side in the upgrade vs extended support calculator.

When OSSeva is not the right purchase

  • Operating systems: OSSeva does not patch Linux distributions or kernels. Use the OS vendor, TuxCare or OpenLogic.
  • SQL Server and Windows Server: OSSeva does not support or patch them. Buy Microsoft ESU, or migrate SQL Server databases to PostgreSQL.
  • Databases inside RDS, Aurora or ElastiCache: only AWS can change those builds, so Extended Support or an upgrade is the route.
  • You want the vendor to host and run the database for you: a managed service fits better than software you operate.

Where the software is yours to run, see the extended support vendors compared.

Sources

Every third-party figure on this page was read on the vendor's own page on 26 Oct 2026. Prices change; confirm with the vendor before you budget.

Questions

Frequently asked questions

Book a 15-minute call

How much does extended support cost?

It depends on what is extended and how the vendor counts. On 26 Oct 2026 the published prices were: Ubuntu Pro $500 per server per year, TuxCare $5,000 a year for up to 10 systems, SQL Server 2016 ESU $278 a month per 2 cores on Standard and $1,081 on Enterprise through Azure Arc, and AWS RDS Extended Support $0.10 per vCPU-hour in US East (Ohio) in years 1 and 2, then $0.20. HeroDevs and OpenLogic do not publish prices. OSSeva does not publish one either.

Is TuxCare cheaper than HeroDevs?

No published figure can settle it. HeroDevs shows Custom Pricing, billed annually, with licences counted per user, meaning people who commit code to the project repository. TuxCare's checkout shows annual bands per system: $5,000 up to 10 systems, $9,750 up to 100 and $23,750 up to 250. The units differ and the products cover different software, so ask both for a quote on the same list of versions.

What does AWS RDS Extended Support cost?

AWS charges per vCPU per hour on provisioned RDS instances after standard support ends: $0.100 in years 1 and 2 and $0.200 in year 3 in US East (Ohio), per the RDS for PostgreSQL pricing page on 26 Oct 2026. Other Regions cost more and standby instances in Multi-AZ deployments are billed. The charge stops when you upgrade to a version in standard support or delete the database. An 8 vCPU instance running all year costs $7,008 in years 1 and 2.

Does OSSeva publish its prices?

No. OSSeva shows no price list. A quote depends on the technologies and units in scope, the versions you run, the environments and the tier: Patch, Assure or Operate. A senior engineer replies within 1 business day. The database support cost calculator compares a quote with what you pay today, from your own figures.

Why can't I compare these prices directly?

Each vendor counts a different unit: a machine, a core, a band of systems, a vCPU-hour or a user, and each covers different software. Normalise to your own estate, as the 50-system example on this page does, and ask every vendor to quote the same list of versions and environments.

Get a quote

Get your exact quote.

Send the technologies, versions and clusters you run. A senior engineer replies within 1 business day with a quote priced per cluster.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call