StackRegent lifecycle policy for releases and Windows Server versions

About this lifecycle policy#

This lifecycle policy describes how we support StackRegent over time. It is a statement of policy, not a guarantee of a particular outcome, and it forms part of the terms of service. We may change it; when a change shortens a support period that you rely on, we announce it in the release notes at least 30 days before it applies.

Last updated: 13 November 2026.

Supported Windows Server versions#

StackRegent supports these versions of Windows Server, with Desktop Experience or as Server Core:

Microsoft's dates come from its Windows Server release information page; check there for the exact day. On Server Core, IIS Manager and the Service Monitor tray app are not available, and the panel manages everything else as usual. Some features depend on the Windows version: TLS 1.3 for websites and HTTP/3 are available on 2022 and 2025, and Git over SSH with the built-in OpenSSH needs 2019 or later. The requirements and the install guides for 2025, 2022, 2019 and 2016 list the details.

How long a Windows Server version stays supported#

Our policy is to support each Windows Server version until Microsoft's end of extended support for it. After that date, Microsoft no longer patches that version of Windows, and we recommend moving accounts to a newer server well before it. Releases made after the end date may no longer install on it, and problems reported on it are handled on a best-effort basis.

For Windows Server 2016, whose extended support ends in January 2027, that means StackRegent support ends at the same time. New releases keep installing on 2016 until then, and the release notes will say in advance which release is the last one for it.

Adding new Windows Server versions#

When Microsoft releases a new long-term version of Windows Server, we add support in a regular release once it passes our own installation and hosting tests. The release notes say when a version is supported. Until then, please do not install StackRegent on it for production use.

Release lines and how long they are supported#

StackRegent version numbers have three parts. The first two parts name a release line (for example 0.17); the last part counts releases within that line. A new release line starts when changes are large enough to need attention, such as a change to the panel's own database or to a supported component. Releases within a line contain fixes and smaller improvements.

The newest release is the supported release#

Updates are free while your license is active, and they install from Tools & Settings › Updates in one click, or automatically at night if you turn on automatic updates. Because of that, our policy is simple: the newest release is the supported release. Fixes, including security fixes, are delivered as new releases, not as patches for older ones. When you open a ticket about an older release, we may ask you to update first if the problem is already fixed. See updating.

The previous release line#

When a new release line starts, the previous line stays supported for 30 days. During that period we answer tickets about it and may publish critical security fixes for it, so you have time to test the new line before you move every server. After 30 days, the previous line is no longer supported and you should update.

Beta releases#

If you turn on Include beta releases in Update Settings, your server is offered test releases before they become stable. Beta releases are for testing. They are not supported for production servers, and they may change or be withdrawn before release.

Server components#

StackRegent installs and manages components made by others: PHP, MariaDB, SQL Server Express, the .NET Framework and ASP.NET Core Hosting Bundle, Node.js, MailEnable, Roundcube, phpMyAdmin and ModSecurity with the OWASP Core Rule Set. Each follows its own vendor's lifecycle. The components page lists them.

• When a vendor ends support for a version, for example a PHP or Node.js version, we announce in the release notes that it will no longer be offered for new installation under Server Components, then remove it from the list in a later release.
• Versions already installed on your server keep running. StackRegent does not remove a component that websites are using.
• Moving websites off an unsupported component version is your decision. PHP versions can run side by side and be chosen per site, so you can move sites one by one.

What happens at end of support#

End of support never switches anything off on its own.

When a Windows Server version reaches end of support#

• Existing installations keep working. Websites, mail, DNS, databases and the panels carry on, and the license keeps checking as normal.
• New releases stop installing on that version. The server stays on the last release that supported it, and the release notes name that release.
• Tickets are answered on a best-effort basis. We help where we can, but we do not fix problems that are specific to the unsupported version.
• We recommend moving to a newer server. The Migration & Transfer Manager moves subscriptions from one StackRegent server to another over HTTPS, with website files, databases, mail and FTP accounts, and can be repeated to copy the latest content just before you switch DNS. The migration guide explains the steps. To move your license, ask for a reissue in the client area.

When a release line reaches end of support#

Nothing changes on your server. The panel keeps working on that release, and the newest release stays available to install while your license is active.

When a license ends#

A lapsed license is not an end of support for the product, but it does stop updates. The panel enters restricted mode, where administrators can open only the license page and cannot add accounts or install updates, while websites, mail, DNS and customer panels keep working. Renewing the license restores updates, and the newest release can be installed straight away. See the license agreement.

Where announcements are made#

Every lifecycle change, such as the last release for a Windows Server version, the start of a new release line or a component version being withdrawn, is announced in the release notes and the changelog. To be told by email, turn on Email me when a new release is available under Tools & Settings › Update Settings. Questions about this policy go to support@stackregent.com.