← ← Back to all products
MaxKB
Active
Server Software Latest Version: v2.10.0-lts Latest Release: Jun 4, 2026
MaxKB is an open-source enterprise-grade agent and knowledge-base Q&A platform built on large language models and RAG, developed by FIT2CLOUD (1Panel team).
Versions
7
Latest Version
v2.10.0-lts
Active Support
3
EOL
4
Lifecycle Timeline
Today ↓
2.10 (LTS)
2.10 (LTS)
2.9
2.9
2.8
2.8
2.0
2.0
1.10 (LTS)
1.10 (LTS)
1.9
1.9
1.0
1.0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.10 (LTS) | Jun 4, 2026 | Yes | No | v2.10.0-lts | Yes | Active |
| 2.9 | May 7, 2026 | Yes | No | v2.9.2 | No | Active |
| 2.8 | Apr 10, 2026 | No | Yes | v2.8.1 | No | EOL |
| 2.0 | Jul 17, 2025 | No | Yes | v2.0.2 | No | EOL |
| 1.10 (LTS) | Feb 10, 2025 | Yes | No | v1.10.14-lts | Yes | Active |
| 1.9 | Jan 2, 2025 | No | Yes | v1.9.1 | No | EOL |
| 1.0 | Apr 11, 2024 | No | Yes | v1.0.4 | No | EOL |
Frequently Asked Questions
Which versions of MaxKB have reached end of life?
The following MaxKB versions have reached end of life and no longer receive security updates: 2.8, 2.0, 1.9, 1.0. It is recommended to upgrade to a supported version.
Is it safe to continue using MaxKB 2.8?
MaxKB 2.8 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 MaxKB?
The latest version of MaxKB is v2.10.0-lts, released in the 2.10 (LTS) release cycle.
How many versions of MaxKB are currently supported?
MaxKB currently has 3 actively supported version(s): 2.10 (LTS), 2.9, 1.10 (LTS).
When does MaxKB 2.10 (LTS) reach end of life?
MaxKB 2.10 (LTS) does not have a specific end-of-life date announced yet.
What should I do when MaxKB reaches end of life?
When a MaxKB 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.