← ← Back to all products
NocoBase
Active
Server Software Latest Version: v2.1.0 Latest Release: Jun 10, 2026
NocoBase is an open-source, no-code/low-code platform for building internal tools and business applications, with a plugin-based and data-model-driven architecture.
Versions
8
Latest Version
v2.1.0
Active Support
2
EOL
6
Lifecycle Timeline
Today ↓
2.1
2.1
2.0
2.0
1.9
1.9
1.8
1.8
1.7
1.7
1.6
1.6
1.5
1.5
1.4
1.4
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.1 | Jun 10, 2026 | Yes | No | v2.1.0 | No | Active |
| 2.0 | Feb 14, 2026 | Yes | No | v2.0.62 | No | Active |
| 1.9 | Nov 2, 2025 | No | Yes | v1.9.47 | No | EOL |
| 1.8 | Jul 7, 2025 | No | Yes | v1.8.33 | No | EOL |
| 1.7 | Jun 3, 2025 | No | Yes | v1.7.20 | No | EOL |
| 1.6 | Mar 11, 2025 | No | Yes | v1.6.38 | No | EOL |
| 1.5 | Feb 5, 2025 | No | Yes | v1.5.25 | No | EOL |
| 1.4 | Dec 3, 2024 | No | Yes | v1.4.34 | No | EOL |
Frequently Asked Questions
Which versions of NocoBase have reached end of life?
The following NocoBase versions have reached end of life and no longer receive security updates: 1.9, 1.8, 1.7, 1.6, 1.5, 1.4. It is recommended to upgrade to a supported version.
Is it safe to continue using NocoBase 1.9?
NocoBase 1.9 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 NocoBase?
The latest version of NocoBase is v2.1.0, released in the 2.1 release cycle.
How many versions of NocoBase are currently supported?
NocoBase currently has 2 actively supported version(s): 2.1, 2.0.
When does NocoBase 2.1 reach end of life?
NocoBase 2.1 does not have a specific end-of-life date announced yet.
What should I do when NocoBase reaches end of life?
When a NocoBase 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.