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

SUSE Manager

Active
DevOps & CI/CD Latest Version: 5.1 Latest Release: Jul 31, 2025

SUSE Manager is an infrastructure management solution for configuration and compliance of Linux systems.

Versions

11

Latest Version

5.1

Active Support

2

EOL

9

Lifecycle Timeline

Today
5.1
5.1
5.0
5.0
4.3
4.3
4.2
4.2
4.1
4.1
4.0
4.0
3.2
3.2
3.1
3.1
3.0
3.0
2.1
2.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.1Jul 31, 2025-No5.1No
Active
5.0Jul 16, 2024-Jun 30, 20265.0.5No
Active
4.3Jun 20, 2022-Jul 23, 20254.3.16No
EOL
4.2Jun 21, 2021-Oct 31, 20234.2.14No
EOL
4.1Jul 21, 2020-Oct 31, 20224.1.15No
EOL
4.0Jun 26, 2019-Jun 30, 20214.0.14No
EOL
3.2Jun 25, 2018-Sep 30, 20203.2.15No
EOL
3.1Jun 27, 2017-Jun 30, 20193.1.11No
EOL
3.0Apr 5, 2016-Oct 31, 20183.0.12No
EOL
2.1Jun 2, 2014-Jan 31, 20172.1.19No
EOL
1.7Aug 9, 2012-Jun 30, 20151.7.6No
EOL

Frequently Asked Questions

Which versions of SUSE Manager have reached end of life?
The following SUSE Manager versions have reached end of life and no longer receive security updates: 4.3, 4.2, 4.1, 4.0, 3.2, 3.1, 3.0, 2.1 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using SUSE Manager 4.3?
SUSE Manager 4.3 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 SUSE Manager?
The latest version of SUSE Manager is 5.1, released in the 5.1 release cycle.
How many versions of SUSE Manager are currently supported?
SUSE Manager currently has 2 actively supported version(s): 5.1, 5.0.
When does SUSE Manager 5.1 reach end of life?
SUSE Manager 5.1 does not have a specific end-of-life date announced yet.
What should I do when SUSE Manager reaches end of life?
When a SUSE Manager 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.