Database engine versions
FPT MongoDB Enterprise supports several MongoDB Enterprise versions at once, so you can pick the one that fits your application rather than the one that happens to be newest. Every version publishes its release and End of Support dates, which is what lets you plan an upgrade instead of reacting to one.
The policy exists to keep two things true: your cluster runs on a supported version, and you know in advance when that stops being the case.
Key principles
- Several MongoDB Enterprise versions run side by side, so you can match the version to what your application actually needs.
- Only stable, production-ready builds reach the platform.
- FPT Cloud applies critical security patches on a periodic or emergency basis, and keeps the impact on your workload as small as it can while doing so.
- You can upgrade a patch version in place on a running cluster. On Replica Set the disruption is smaller still.
Version structure
FPT MongoDB Enterprise follows the versioning convention set by MongoDB Inc. Versions have three parts, as in 8.0.20.
| Component | What it means |
|---|---|
| Major | Significant changes to architecture or features. May not be backward compatible. |
| Minor | The feature or release branch. |
| Patch | Smaller updates, bug fixes, and security patches. Backward compatible. |
To see the exact version a cluster runs, open its details in the Console Portal.
Version lifecycle
Every version moves through four stages.
| Stage | What it means | Console Portal tag |
|---|---|---|
| Preview (Beta) | Under test, with no SLA. Features can change or be removed at any time. Use it for evaluation and non-production work. Not recommended for production. | Beta |
| General Availability (GA) | Stable, production-ready, and officially supported under SLA. | none |
| Deprecated (Dep.) | No longer recommended for new deployments and approaching End of Support. Existing clusters keep working. | Deprecated or Dep. |
| End of Support (EoS) | No longer supported. | EoS |
Plan your upgrade before your version reaches Deprecated or End of Support. Waiting until it does leaves you running an unsupported engine, with no fix available for a security issue.
What to do at each stage
| If your cluster runs | Do this |
|---|---|
| A GA version | Carry on. No action needed, though it is worth tracking when a newer GA version appears. |
| A Beta version | Follow the update announcements closely. The version can change or be withdrawn without notice. |
| A Deprecated version | Stop creating new clusters on it and plan an upgrade to a supported version. End of Support is approaching. |
Supported version catalog
| Version | Status | FDE Preview | FDE GA | FDE Deprecated | FDE EoS |
|---|---|---|---|---|---|
| 8.0.20 | GA | 2026 | 2026 | – | – |
| 7.0.30 | GA | 2026 | 2026 | – | – |
| 6.0.27 | GA | 2026 | 2026 | – | – |
A dash means no value has been published for that column. In the FDE Deprecated and FDE EoS columns, that means no date has been announced yet, not that the version is supported indefinitely.
Next steps
- Upgrade patch version to move an existing cluster to a higher patch
- Features if you are still evaluating the service
- Create your first database, where you pick the version