Back to blog

OSSeva Blog

Operations

Spring Boot Commercial Support: What to Check Beyond Spring Enterprise

7 min read

Spring Boot commercial support is sold by Broadcom as Spring Enterprise and, for lines past open-source support, by HeroDevs, TuxCare, OpenLogic and OSSeva. The offers differ on eight things: which Boot lines are listed, how long, how fast fixes arrive, whether that speed is a contract, how builds are delivered, which Spring projects are in scope, what happens to the dependencies Boot manages, and how the price is set. Each answer below comes from the vendor's own page, read on 17 November 2026 (TuxCare on 20 October 2026, because its page returned an error on 17 November). If your lines are Spring Boot 2.x or Spring Framework 5, start from Spring Boot extended support.

Running Spring Framework in production? OSSeva patches and supports it, end-of-life versions included.

Spring Framework extended support: what is covered

What should you check before buying Spring Boot commercial support?

Check the exact Boot line, the end date, the fix time, the contract term, the delivery, the Spring projects, the dependencies and the price model, in that order.

CheckWhy it mattersWhat the vendors state
1. Is your exact Boot line listed?A vendor that lists 2.7 may not list 3.1, and the reverseBroadcom lists lines inside its window, including 2.7 to 30 Jun 2029. HeroDevs lists Boot 1.5, 2.5, 2.7, 3.2, 3.3, 3.4 and 3.5. TuxCare listed 2.4, 2.6, 3.1 and 3.5 but not 2.7. OpenLogic lists 2.7 and 3.1 to 3.5. OSSeva patches 2.6, 2.7 and 3.0 to 3.5
2. How long is the commitment?Support that ends before your migration does is a gap with a date on itBroadcom: 2.7 to 30 Jun 2029, 3.5 to 30 Jun 2032, 3.4 to 31 Dec 2026. OpenLogic: 2.7 to 31 Oct 2027, 3.1 to 3.5 to 30 Jun 2028. HeroDevs and OSSeva publish no end date for Spring cover on the pages read
3. How fast does a fix arrive?Exploit windows are short; a fix in 90 days is a different product from a fix in 2Broadcom promises day-zero access to patches and "fast response times", without figures. OpenLogic: 14 days for CVSS 9 and above, 30 days for CVSS 7 and above. HeroDevs: response times vary by severity, no figures. OSSeva: Critical within 48 hours, High within 7 days
4. Is the speed a contract?An objective is a target; an SLA has remediesOpenLogic says Spring timings are service level objectives, with SLAs only for CentOS 7 and AngularJS. HeroDevs says it has an SLA and provides it on request. OSSeva states patch targets and, on Operate, response times of 15 minutes for P1, 1 hour for P2 and 4 hours for P3
5. How are builds delivered?It decides whether your build files changeBroadcom, HeroDevs and OSSeva deliver through Maven repositories; HeroDevs also through a CLI. TuxCare lists Maven and Gradle. OSSeva signs artifacts and keeps your version line
6. Which Spring projects are in scope?Spring Data, Spring Cloud and others hold CVEs tooBroadcom lists over 50 Spring projects plus OpenJDK and Tomcat. HeroDevs lists the Data, Cloud and other projects each Boot line manages. OSSeva publishes Framework, Boot and Security only, and confirms any other project before you buy
7. What about the dependencies Boot manages?Most findings sit in Jackson, Netty, Logback and embedded Tomcat, not in Spring codeHeroDevs states that NES covers the Spring-managed dependencies for Boot 2.7 and 3.5. OSSeva backports fixes to the libraries the Boot 2.7 BOM manages. Ask the others which libraries are in scope
8. How is the price set?Per core, per application and per seat scale differently with your estateNo vendor publishes a Spring price on the pages read. OSSeva prices per application. Ask each for a written quote with the versions named

Sources: enterprise.spring.io, herodevs.com/support/spring-nes and openlogic.com/products/long-term-support, read 17 November 2026; tuxcare.com/endless-lifecycle-support/java-spring-eol-support, read 20 October 2026; api.spring.io for Spring's own dates. Where a page states no figure, the cell says so rather than guessing.

What does Spring Enterprise from Broadcom add that other vendors do not?

Spring Enterprise is the route where, in Broadcom's own words, fixes come from the engineers who write Spring. enterprise.spring.io describes day-zero access to patches for enterprise versions and the latest open-source releases, private access to releases no longer under open-source support, Spring Boot extensions for FIPS, PCI-DSS and SBOM checks, Application Advisor for automated upgrade pull requests, and 24x7 support for more than 50 Spring projects plus OpenJDK and Tomcat. Its limit is the calendar: Spring lists a commercial end date per line, one year after open-source end for most lines and 2029 and 2032 for 2.7 and 3.5. A line whose date has passed does not come back by signing. See why those dates differ.

When is a third-party vendor the better fit?

A third party fits when your line is outside Broadcom's window, when Spring is one of several stacks you need covered, or when you want the build files to stay the same. Boot 3.0 to 3.3 are out of Broadcom's commercial window, and Boot 3.4's ends on 31 December 2026. HeroDevs, OpenLogic and OSSeva list some or all of them. A single contract across Spring, Tomcat and the brokers and databases beneath them is the case OSSeva is built for. Where OSSeva is not the right pick: you need Spring Data or Spring Cloud versions it has not confirmed, or you want patches from the Spring maintainers themselves.

What should be in the contract?

Name the Spring projects and exact versions, the fix time in hours or days, and what happens when a line you run has no fix.

  • The versions: write Boot, Framework and Security versions into the order form, not "Spring".
  • The clock: the patch target, who starts it and what counts as a fix.
  • The delivery: where artifacts come from, how they are signed and how your build verifies them.
  • The exit: whether you can keep patched builds you already received if you stop paying.

Spring Boot extended support sets out OSSeva's answer to each, and the Spring 5 and Boot 2 extended support comparison sets the vendors side by side.

Frequently asked questions

Who sells Spring Boot commercial support?

Broadcom sells it as Spring Enterprise (TrueSource). For lines past open-source support, HeroDevs, TuxCare, OpenLogic and OSSeva also sell patched builds, each listing different Boot lines.

How much does Spring Boot commercial support cost?

None of the vendor pages read on 17 November 2026 publishes a Spring price. OSSeva prices per application; the others quote per customer.

Is Spring Boot commercial support the same as extended support?

Not exactly. Commercial support is the paid service around a line, including help and response times; extended support is the paid fix stream for a line after open-source support ends. Many offers bundle both, so check which one a quote covers.

Can I buy support for Spring Boot 3.0 to 3.3?

Not from Broadcom, whose commercial support for 3.0 to 3.3 has ended. HeroDevs lists 3.2 and 3.3, OpenLogic lists 3.1 to 3.3 to 30 June 2028 and OSSeva patches 3.0 to 3.3.

Should I upgrade instead of buying support?

Upgrade the applications that can move. Buy support for those blocked by Java 17, the jakarta rename or a validation cycle, with an upgrade date written down for each.

Tags

Spring BootSpring FrameworkVendor ComparisonExtended SupportEnd of Life

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

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

Prefer to talk or read more first?

Book a call