Supported versions and upgrade matrix

Supported engine versions

Each DCT release supports Continuous Data, Continuous Compliance, and Hyperscale Compliance engines from the last nine releases. Delphix ships a release about every two months, so this covers about 18 months, which matches the Primary Support period for each engine release. Count back from the engine release with the same version number as DCT. Minor and patch releases are supported along with their parent release. For example, any 2025.3.x.x engine is supported when 2025.3 is.

For example, DCT 2026.5 supports engines from 2025.3 through 2026.5. An engine on 2025.2 or earlier must be upgraded to a supported release. For engine release dates, see the Continuous Data and Continuous Compliance maintenance lifecycle.

We recommend keeping DCT on the same release as your engines, or ahead of them.

Some DCT features need a newer engine than the oldest supported release. These requirements are listed in the release notes and on each feature's page.

DCT upgrade paths

Before you upgrade DCT, check that your engines are supported by the target DCT version. Upgrading DCT moves the nine-release window forward, so an engine that is supported today may not be supported after the upgrade.

You can upgrade directly between DCT versions, with one exception: customers on 2026.4.x or earlier must upgrade to 2026.5 before moving to a later release. DCT 2026.5 upgrades the bundled PostgreSQL database from version 14 to version 18. For deployments that use the bundled PostgreSQL database, backups created before the PostgreSQL 18 upgrade must be restored onto DCT 2026.5 and backed up again before moving to a later release. For more information, see the 2026.5 release notes.

For DCT release dates and support periods, see the DCT maintenance lifecycle.

Where x represents any minor release (for example, 2026.4.0 and 2026.4.1).