DuckDB End of Service Life Dates
DuckDB has published end-of-service-life dates for 7 products in our catalog. 3 reach EOSL within the next 12 months and 4 are already past OEM support. Third-party support keeps those releases covered after the vendor stops shipping patches: issue management, vulnerability remediation and compliance maintenance.
DuckDB products reaching EOSL in 2026(1)
| Model | EOSL date | |
|---|---|---|
| DuckDB 1.4 (LTS) | Nov 17, 2026 | Get price |
DuckDB products reaching EOSL in 2027(2)
| Model | EOSL date | |
|---|---|---|
| DuckDB 1.5 | Mar 1, 2027 | Get price |
| DuckDB 2.0 (LTS) | Oct 21, 2027 | Get price |
DuckDB products reaching EOSL in 2025(3)
| Model | EOSL date | |
|---|---|---|
| DuckDB 1.1 | Feb 5, 2025 | Get price |
| DuckDB 1.2 | May 21, 2025 | Get price |
| DuckDB 1.3 | Sep 16, 2025 | Get price |
DuckDB products reaching EOSL in 2024(1)
| Model | EOSL date | |
|---|---|---|
| DuckDB 1.0 | Sep 9, 2024 | Get price |
DuckDB EOSL: Frequently Asked Questions
What does end of service life (EOSL) mean for DuckDB equipment?
EOSL is the date after which DuckDB no longer sells support contracts or ships updates for a product. The equipment keeps working; only the OEM's willingness to support it ends. Third-party maintenance takes over from that date with engineering support and replacement parts.
Can I get support for DuckDB products that are already past EOSL?
Yes. 4 DuckDB products in this list are already past their EOSL date and all remain supportable. We hold spares for every model we quote and cover equipment for 5+ years past the OEM date.
How far ahead should I plan for a DuckDB EOSL date?
Start 6 to 12 months before the EOSL date. That is enough time to compare the OEM's final renewal against third-party maintenance, decide whether to extend or refresh, and move coverage without a gap. We return an indicative price within 24 hours and a firm quote within 48.