StackX Supported Versions (updated: July 12, 2026)
This page summarizes the versions supported within the StackX LAMP scope.
Specific environments: The standard delivery baseline currently covers Debian 12 and Debian 13. Any request involving another distribution, a legacy environment, or technology outside the standard scope requires a specific assessment. Contact us to evaluate feasibility, compensating measures, and the migration path.
Legend:Yes = standard support, Custom quote = legacy case or specific project, No = not supported in managed production.
Debian Distributions - StackX Baseline
Debian Distributions - StackX Baseline
Debian Distribution
StackX Use
Status
Debian 13 Trixie
New StackX generation, recent deliveries, and new projects
Yes
Debian 12 Bookworm
Current production baseline, still widely used as the reference
Yes
PHP - Standard Debian 12/13 MatrixStandard PHP versions on Debian 12 and 13
PHP - Standard Debian 12/13 Matrix
Debian Distribution
PHP Versions Available for Production
Status
Debian 13 Trixie
5.6 to 8.5
Yes
Debian 12 Bookworm
5.6 to 8.5
Yes
PHP - Versions Available through SuryMaintained PHP 5.6, 7.x, and 8.x versions
PHP - Versions Available through Sury
PHP Versions
StackX Status
Notes
PHP 8.0 to 8.5
Yes
Available on Debian 12 and Debian 13
PHP 7.0 to 7.4
Yes
Available on Debian 12 and Debian 13
PHP 5.6
Yes
Available on Debian 12 and Debian 13
PHP in StackX: StackX relies on the Sury repositories to deliver PHP versions from 5.6 to 8.5 on Debian 12 and Debian 13. Versions can be operated per vhost through PHP-FPM, allowing multiple versions to coexist on the same machine.
MariaDB - Standard Debian 12/13 MatrixLTS branches available on Debian 12 and 13
MariaDB - Standard Debian 12/13 Matrix
Debian Distribution
Available MariaDB Versions
Status
Debian 13 Trixie
11.8 LTS, 12.3 LTS
Yes
Debian 12 Bookworm
10.11 LTS, 11.4 LTS, 11.8 LTS, 12.3 LTS
Yes
New LTS Branch
Repository and StackX compatibility validated at the time of the request
Custom quote
Rolling / Short-lived Branches
Outside the standard baseline, existing-system takeover, or controlled migration
Custom quote
MariaDB policy: New standard deliveries favor LTS branches whose repositories are available for the selected distribution. A rolling branch may be technically accessible without being selected as a managed production baseline.
PostgreSQL - Standard Debian 12/13 MatrixPGDG branches available on Debian 12 and 13
PostgreSQL - Standard Debian 12/13 Matrix
Debian Distribution
Available PostgreSQL Versions
Status
Debian 13 Trixie
15 to 18 through the official PGDG repository
Yes
Debian 12 Bookworm
15 to 18 through the official PGDG repository
Yes
PostgreSQL 14
Existing-system maintenance or migration before upstream support ends on November 12, 2026
Custom quote
PostgreSQL 13 and Earlier
Versions no longer maintained upstream; controlled migration only
Custom quote
New Branches
Repository, upstream support, and StackX compatibility validated at the time of the request
Custom quote
PostgreSQL in StackX: StackX uses the official PostgreSQL PGDG repository and explicitly pins the selected major version. PostgreSQL can be the primary SQL engine or be added alongside another engine. In PRD/DRS, StackX uses physical primary/standby replication, not an active/active model.
MySQLSupported Oracle MySQL versions
MySQL
Version
StackX Status
Comment
MySQL 8.4 LTS
Yes
Standard support
MySQL 8.0
Custom quote
Existing-system maintenance on Debian 12 or controlled migration
MySQL 5.7
No
Upstream end of life
MySQL 5.6
No
Obsolete / not maintainable
Node.jsAvailable versions and per-user management
Node.js
Version
StackX Status
Comment
Node.js 24 LTS
Yes
Standard support
Node.js 22 LTS
Yes
Standard support
Node.js 20
Custom quote
Upstream end of life; existing systems only
Node.js 18 and Earlier
Custom quote
Obsolete versions; controlled maintenance only
Node.js in StackX: Node.js versions are managed per user through sxnode, without depending on a global system Node.js installation. StackX can install multiple versions per user, define a default version, and expose node, npm, npx, and corepack cleanly.
Legacy and Custom CasesExisting-system takeovers and controlled migrations
Legacy and Custom Cases
Context
StackX Handling
Status
Legacy Application
Controlled maintenance, compensating measures, and migration path
Custom quote
Enterprise Requirement
Specific contract, defined scope, and commitment aligned with the actual risk
Custom quote
New Standard Machine
Delivery on Debian 12 or Debian 13 only
Yes
StackX Operations & Upgrade Paths
StackX Operations & Upgrade Paths
Topic
What StackX Provides
PHP per vhost
Targeted PHP-FPM version switch for one vhost without rewiring the entire stack
Runtime Checks
Local verification of the PHP-FPM pool and associated services before or after maintenance work
Node.js per User
Per-user Node.js version management with controlled activation, status auditing, and corepack compatibility
Application Compatibility
Customizable docroot, .user.ini, and reverse proxy to Node.js, Python, or another local service
Database
Standard MariaDB/MySQL/PostgreSQL versions, or controlled support for legacy versions, with a migration path and replication according to the architecture
Version Upgrade
Prechecks, operational validation, and post-change checks across the managed scope
Need version planning for a migration? We can define a progressive upgrade path with you (runtime + database + dependencies), including a controlled failover window. Discuss a Migration Plan