Skip to main content

Database Engine Versions

FPT Database Engine supports several versions of each engine at once, so you can pick the one that fits your workload 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. The catalog further down carries the dates for every engine.

Key principles

  • Multiple versions of each engine are supported at the same time.
  • New versions released by each engine's community are added on an ongoing basis, for features, performance, and security.
  • Major versions are never upgraded automatically. Moving between them is a manual data migration, so that data integrity stays under your control.

Version structure

FPT Database Engine follows each engine community's own versioning convention. Versions usually have three parts, as in 8.0.42.

ComponentWhat it means
MajorSignificant changes to architecture or features. May not be backward compatible.
MinorThe feature or release branch.
PatchSmaller 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.

StageWhat it meansConsole 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
warning

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 runsDo this
A GA versionCarry on. No action needed.
A Beta versionFollow the update announcements closely. The version can change or be withdrawn without notice.
A Deprecated versionStop creating new clusters on it and plan an upgrade to a supported version. End of Support is approaching.

Supported version catalog

Each engine offers several versions, listed below with the dates that matter for planning: when the version became available, and when its support ends. The Status column gives the stage the version sits in today, using the same four names as the Version lifecycle table above.

note

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.

PostgreSQL

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
17.7GA10/202510/2025
16.11GA20242024
15.15GA20232023
14.19GA20222022
13.23EoS2021202111/202530/06/2026
12.xEoS2020202011/202530/06/2026
11.xEoS2019201911/202530/06/2026

MySQL

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
8.4.8GA20262026
8.0.42GA08/202508/2025
8.0.31EoS
8.0.30Dep.2024202412/08/202630/09/2026
8.0.25EoS2021202111/202530/06/2026

MariaDB

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
11.4.10GA2026
10.11.16GA2026
10.9.xGA20252025
10.8.xEoS2024202411/202530/06/2026
10.7.xEoS2023202311/202530/06/2026
10.6.14GA20232023
10.5.xEoS2023202311/202530/06/2026
note

No GA date has been published yet for 11.4.10 or 10.11.16. Check the version tag in the Console Portal before you plan production work around them.

MariaDB is the only engine with an in-place upgrade path. See Upgrade database version.

SQL Server

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
2022GA20252025
2019EoS2024202411/202530/06/2026
2017EoS2023202311/202530/06/2026

MongoDB

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
6.0.6Beta03/2026
6.0.6GA20242024
5.0.15EoS2024202415/11/202530/06/2026
4.4.6EoS2023202315/11/202530/06/2026

Redis

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
7.2.13Beta2026
7.2.1GA20242024
6.0.6EoS2024202411/202530/06/2026

Cassandra

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
4.1.4GA20242024

OpenSearch

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
3.5.0Beta2026
2.8.0GA20242024

RabbitMQ

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
3.13.6-1GA20242024

Kafka (KRaft)

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
4.1.2Beta2026
3.8.0GA20252025
3.4.0EoS2024202411/202530/06/2026

Kafka (ZooKeeper)

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
3.4.0EoS2024202411/202530/06/2026

Kafka is offered in two metadata modes. KRaft is the mode to build on: ZooKeeper mode has reached End of Support, and Kafka 4.x drops ZooKeeper entirely.

TimescaleDB

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
2.12.2GA20242024

ClickHouse

VersionStatusFDE PreviewFDE GAFDE DeprecatedFDE EoS
23.9.2.56GA20242024

Next steps