← ← Back to all products
All badges & lifecycle API →
KirbyEnd of Life (EOL) Dates & Support Status
Active
CMS & ContentLatest Version: 5.6.0Latest Release: Sep 16, 2026
Kirby is a file-based CMS that gives developers full control over content structure.
Support summary
Kirby 4 reaches EOL in 62 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Nov 28, 2026
Kirby 4 · 62 days left
Supported cycles
2
0 lts
Versions
21
Latest Version
5.6.0
Active Support
2
EOL
19
Lifecycle Timeline
Nov 5, 2019As of Sep 27, 2026
5Active · Date not announced
3.10EOL · Nov 27, 2025
4Active · Nov 28, 2026
3.9EOL · Nov 27, 2025
3.8EOL · Jan 16, 2025
3.7EOL · Oct 5, 2024
3.6EOL · Jun 26, 2024
3.5EOL · Nov 15, 2023
3.4EOL · Nov 16, 2021
3.3EOL · Nov 16, 2021
ActiveSecurityEOLHistorical phase unknown
Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5 | Jun 24, 2025 | Maintained | Date not announced | 5.6.0 | No | Active |
| 3.10 | Dec 19, 2023 | Ended | Nov 27, 2025 | 3.10.1.2 | No | EOL |
| 4A new era | Nov 28, 2023 | Maintained | Nov 28, 2026 | 4.9.6 | No | Active |
| 3.9Brookesia | Jan 17, 2023 | Ended | Nov 27, 2025 | 3.9.8.3 | No | EOL |
| 3.8Rhampholeon | Oct 6, 2022 | Ended | Jan 16, 2025 | 3.8.4.4 | No | EOL |
| 3.7Kinyongia | Jun 27, 2022 | Ended | Oct 5, 2024 | 3.7.5.5 | No | EOL |
| 3.6Jungle Calumma | Nov 16, 2021 | Ended | Jun 26, 2024 | 3.6.6.6 | No | EOL |
| 3.5Calumma | Dec 15, 2020 | Ended | Nov 15, 2023 | 3.5.8.4 | No | EOL |
| 3.4Furcifer | Jul 7, 2020 | Ended | Nov 16, 2021 | 3.4.5 | No | EOL |
| 3.3Trioceros | Nov 5, 2019 | Ended | Nov 16, 2021 | 3.3.6 | No | EOL |
| 3.2Archaius | Jun 25, 2019 | Ended | Nov 16, 2021 | 3.2.5 | No | EOL |
| 3.1Chamaeleo | Mar 19, 2019 | Ended | Nov 16, 2021 | 3.1.4 | No | EOL |
| 3.0 | Jan 15, 2019 | Ended | Nov 16, 2021 | 3.0.3 | No | EOL |
| 2.5 | Jun 20, 2017 | Ended | Jan 1, 2021 | 2.5.14 | No | EOL |
| 2.4 | Nov 3, 2016 | Ended | Jan 1, 2021 | 2.4.2 | No | EOL |
| 2.3 | May 17, 2016 | Ended | Jan 1, 2021 | 2.3.3 | No | EOL |
| 2.2 | Nov 17, 2015 | Ended | Jan 1, 2021 | 2.2.3 | No | EOL |
| 2.1 | May 19, 2015 | Ended | Jan 1, 2021 | 2.1.1 | No | EOL |
| 2.0 | Oct 7, 2014 | Ended | Jan 1, 2021 | 2.0.6 | No | EOL |
| 1.1 | Jun 19, 2012 | Ended | Feb 1, 2016 | 1.1.2 | No | EOL |
| 1.0 | Jan 9, 2012 | Ended | Feb 1, 2016 | 1.0.9 | No | EOL |
Data sources
Sources
Embed this badge
Show Kirby's live support status in your README, docs, or dashboard. The badge is a static SVG served from eol.wiki and follows the lifecycle data above.
Markdown
[](https://eol.wiki/kirby/)HTML
<a href="https://eol.wiki/kirby/"><img src="https://eol.wiki/badge/kirby.svg" alt="Kirby end-of-life status" height="20"></a>Frequently Asked Questions
Which versions of Kirby have reached end of life?
The following Kirby versions have reached end of life and no longer receive security updates: 3.10, 3.9, 3.8, 3.7, 3.6, 3.5, 3.4, 3.3 (and 11 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Kirby 3.10?
Kirby 3.10 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Kirby?
The latest version of Kirby is 5.6.0, released in the 5 release cycle.
How many versions of Kirby are currently supported?
Kirby currently has 2 actively supported version(s): 5, 4.
When does Kirby 5 reach end of life?
Kirby 5 does not have a specific end-of-life date announced yet.
What should I do when Kirby reaches end of life?
When a Kirby version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.