EOL.Wiki EOL.Wiki
← ← Back to all products

Veeam ONE

Active
Cloud & Platforms Latest Version: 13.0.1.6168 Latest Release: Jan 6, 2026

Veeam ONE provides monitoring and analytics for virtual, cloud, and data protection environments.

Versions

10

Latest Version

13.0.1.6168

Active Support

1

EOL

8

Lifecycle Timeline

Today
13
13
12
12
11
11
10
10
9.5
9.5
9.0
9.0
8.0
8.0
7.0
7.0
6.5
6.5
6.0
6.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
13Sep 3, 2025YesNo13.0.1.6168No
Active
12Jan 30, 2023Sep 3, 2025Feb 1, 202712.3.0.4670No
Security
11Feb 9, 2021Feb 1, 2023Feb 1, 202411.0.1.1880No
EOL
10Feb 18, 2020Feb 1, 2021Feb 1, 202310.0.2.1094No
EOL
9.5Nov 16, 2016Feb 1, 2020Feb 1, 20229.5.4.4587No
EOL
9.0Jan 12, 2016NoYes9.0.0.2088No
EOL
8.0Nov 6, 2014NoYes8.0.0.1669No
EOL
7.0Aug 15, 2013NoYes7.0.0.949No
EOL
6.5Oct 9, 2012NoYes6.5.0.686No
EOL
6.0Aug 22, 2011NoYes6.0.0.520No
EOL

Frequently Asked Questions

Which versions of Veeam ONE have reached end of life?
The following Veeam ONE versions have reached end of life and no longer receive security updates: 11, 10, 9.5, 9.0, 8.0, 7.0, 6.5, 6.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Veeam ONE 11?
Veeam ONE 11 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 Veeam ONE?
The latest version of Veeam ONE is 13.0.1.6168, released in the 13 release cycle.
How many versions of Veeam ONE are currently supported?
Veeam ONE currently has 2 actively supported version(s): 13, 12.
When does Veeam ONE 13 reach end of life?
Veeam ONE 13 does not have a specific end-of-life date announced yet.
What should I do when Veeam ONE reaches end of life?
When a Veeam ONE 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.