On this page
Lifecycle Policy - TOS
This policy is in effect from 2026, starting with version 5.0.00. For the lifecycle policy of earlier versions, see R25-2 Lifecycle Policy, R25-1 Lifecycle Policy, R24-2 Lifecycle Policy . We release a new platform version every year and continue to release new features and/or bug fixes for that platform version for up to two years.
Platform version phases
-
Initial release version: The first version, not for production deployment. Meant to test and verify that the new TOS infrastructure deploys and runs smoothly in a lab environment. It contains infrastructure updates and bug fixes, but little or no new features.
-
Feature versions: These versions are production-ready. They contain feature enhancements and bug fixes with little or no infrastructure changes. They will typically be spaced out around six weeks apart. Updating to a feature version within the same platform version generally takes less time than updating to a new platform version.
-
Unplanned versions: Released if a bug is discovered that is considered important enough to correct urgently rather than waiting until the next feature version.
-
End of Life (EOL): No more versions will be released for this platform version. Support will given for update related issues only. EOL Comes into effect when the platform version after next is released, about two years later.
Product naming convention
TOS platform versions are named TOS 5, TOS 6, etc. As new features and bug fixes are made available, they are released as new feature versions within that platform version.
TOS versions are named in the format w.x.y,
Where:
-
w is the platform version number - ‘5’ for TOS 5, ‘6’ for TOS 6 etc.
-
x is the feature version number within that platform version, or ‘0’ for the initial release version.
-
y is the unplanned version number or ‘00’ for planned versions.
Examples:
• 5.0.00, 6.0.00 – initial release versions
• 5.1.0, 5.2.0 - feature versions
• 5.1.01, 6.3.02 - unplanned versions
Update policy
-
You can only update to versions released after the source version.
-
You can update from any version of the same platform version or the platform version that immediately preceded it.
-
An exception to the rule above is updating to TOS 5, which can updated from any version of TOS 5, R25-2, or R25-1.
-
Updating to a later feature version in the same platform version e.g. 5.0.00 to 5.2.00, 5.1.00 to 5.5.00 etc. will generally be faster than updates to a new platform version.
There can be exceptions to these rules. See TOS Release History and Update Paths.
End of Life Schedule
|
Platform Version |
Latest Version Release |
EOL End of Life |
|---|---|---|
| TOS 5 | 5.1.01 See what's new. | May 31 2028 |
| R25-2 | R25-2 PHF4.1.0 | March 24 2027 |
| R25-1 | R25-1 PHF3.1.0 | June 3 2026 |
| R24-2 and earlier | R24-2 PHF3.0.0 | November 19 2025 or earlier |
Additional information
To receive announcements for new hotfixes, register at: Tufin Subscriptions. This mailing list is also used for TufinOS release announcements.