2027 end-of-life calendar

This is a count of end-of-life dates, not of products. Some products appear twice because two of their lines end in the year. Each row links to the page for that line, with its dates and the options for staying on it. Dates for lines that ended before 2027 are on the EOL tracker.

Download all 19 dates as an .ics calendar file to add them to Google Calendar, Outlook or Apple Calendar as all-day events.

Where the 2027 dates cluster

• The third quarter holds more than half the year. 10 of the 19 dates fall between July and September, from etcd 3.5 on 8 July to Valkey 8.0 on 15 September.
• Four lines end on 31 July. Spring Boot 4.1, Spring Framework 7.0, Spring Security 7.1 and RabbitMQ 4.4 all reach end of life on 31 July 2027. A Spring stack that uses all three Spring lines has one deadline, not three.
• Two dates share 30 April. HashiCorp Consul 1.21 and Node.js 22 both end on 30 April 2027.
• ClickHouse and Camel each lose two lines. ClickHouse 26.3 and 26.8, and Apache Camel 4.18 and 4.22, are all long-term-support lines that end in 2027.

The busiest stretch comes just before this calendar starts. According to endoflife.date, .NET 8 and .NET 9 end on 10 November 2026 and PostgreSQL 14 on 12 November 2026. Those dates are not counted above. See .NET 8, .NET 9 and PostgreSQL 14.

What end of life means here

EOL stands for end of life. In this calendar it is the date, as endoflife.date records it, after which the project no longer releases fixes for that release line. Teams also hear end of support and end of service life. Some vendors use the three terms for one date and others for different dates, so check the policy of each project before you plan around a single day.

Method

1. Take every technology OSSeva has a page for. For each one that endoflife.date tracks, read the eol field of every release line from endoflife.date/api/<product>.json on 30 October 2026, and keep the lines dated 2027.
2. Compare each date with the end-of-life data on this site. Where they disagreed, use the endoflife.date value.
3. Cross-check the RabbitMQ 4.3 and 4.4 dates against the community support end in RabbitMQ's release information table.
4. Group by calendar quarter and count the rows in each.

What is not counted

• Later support dates. Some projects publish a second, later date for security-only or paid commercial support, such as Apache Pulsar 4.0 security support to 21 October 2027 or RabbitMQ commercial support. Only the end-of-life date is counted.
• Products endoflife.date does not track. Hazelcast, Tanzu GemFire, Apache Druid, Apache Hive, Apache Ignite and Apache Storm have no endoflife.date feed to check. No 2027 date is claimed for them here.
• Lines with no end date. A release line that endoflife.date lists as supported with no end date, including every current Apache Kafka line, cannot be placed on a calendar.
• Cloud provider dates. Managed services set their own cut-off dates, which can differ from the project's.

For what lands on a line after its date, read the EOL exposure study. We sell extended support for several of these technologies, so check the dates yourself with the sources below.

Sources

All checked 30 October 2026.

• https://endoflife.date/api/rabbitmq.json
• https://endoflife.date/api/apache-camel.json
• https://endoflife.date/api/clickhouse.json
• https://endoflife.date/api/tomcat.json
• https://endoflife.date/api/redis.json
• https://endoflife.date/api/consul.json
• https://endoflife.date/api/nodejs.json
• https://endoflife.date/api/erlang.json
• https://endoflife.date/api/etcd.json
• https://endoflife.date/api/elasticsearch.json
• https://endoflife.date/api/spring-boot.json
• https://endoflife.date/api/spring-framework.json
• https://endoflife.date/api/spring-security.json
• https://endoflife.date/api/mongodb.json
• https://endoflife.date/api/valkey.json
• https://endoflife.date/api/postgresql.json
• https://www.rabbitmq.com/release-information