Linux downloads

PXM for Linux.

A headless manager for PHP, Node.js, websites, HTTPS and databases on Ubuntu 22.04, 24.04 and 26.04. Choose the archive for your computer's CPU architecture.

PXM 0.4.0 is available for both architectures. Each archive contains the CLI, its release receipt and license notices.

ARM64

Download PXM 0.4.0 for ARM64

Archive SHA-256:

SHA-256
c39c939a1797065ababddba25a5e397af4a227c2ab44e149f4c7cca6d5f0ba4c

x86_64 (AMD64)

Download PXM 0.4.0 for x86_64 (AMD64)

Archive SHA-256:

SHA-256
2fef01e113c532bbffb52d02bb8dba06bb832773dd963a7797fd2076d4063918

Signed stable release feed · Release verification

Install

Run uname -m: aarch64 uses ARM64 and x86_64 uses AMD64. Download the matching archive, compare sha256sum with the listed checksum, and extract it into a private directory. Run ./pxm --version and ./pxm doctor from that directory.

Install as the unprivileged account that will own your applications and databases. For a new installation:

Terminal
install -d -m 755 "$HOME/.local/bin"
# Run from the extracted release directory. Keep any existing command intact.
test ! -e "$HOME/.local/bin/pxm" && test ! -L "$HOME/.local/bin/pxm" && install -m 755 ./pxm "$HOME/.local/bin/pxm"
export PATH="$HOME/.local/bin:$PATH"
pxm doctor

Add the PATH line to your shell profile if needed. Check command -v pxm first when the older Omarchy CLI is installed. This release uses its own ~/.local/share/pxm-server workspace and does not adopt another manager's data automatically.

The executable and its directory must belong to your account, with no group or other write permission. Keep the release archive for its receipt and third-party license notices. The supported setup requires standard HTTPS CA certificates, private storage that allows executables, and systemd. No compiler, Go, Homebrew or Docker is required on the target computer.

Your first website

PHP, Node.js, sites and HTTPS are free features.

Terminal
pxm php install 8.5
pxm php use 8.5
pxm node install 24
pxm node use 24
pxm web enable --email you@example.com
pxm site add app.example.com /home/deploy/app/public --type php --php 8.5

Point the domain to the server and allow inbound ports 80 and 443. PXM does not change DNS or firewall rules. Enabling routing requests administrator access for its systemd unit; the router and application workers run as your unprivileged account. Read website operations before deploying a live application.

Add a database

New managed services and engine updates require PXM Pro. Existing services remain startable, backed up and recoverable offline.

Terminal
pxm license activate
pxm startup enable
pxm service add mysql --name database
pxm service start database
pxm service env database

The last command explicitly displays credentials. Keep its output private. Default ports are MySQL 3306, PostgreSQL 5432 and Redis 6379. Database operations covers maintenance and recovery. To move a database you already run, follow the import guide.

Updates you control

Terminal
pxm self-update --check
pxm self-update
# Schedule database maintenance before restarting its manager.
pxm daemon restart

pxm catalog php
pxm php install 8.5
pxm node available
pxm node install 24

pxm site update app.example.com --php 8.5
pxm site update node.example.com --node 24
pxm web update-check
pxm web update
pxm service update-check database
pxm service update database

The CLI updater verifies the signed feed, archive checksum and architecture. Installing it leaves running services alone. During a maintenance window, daemon restart cleanly stops owned databases and starts those with autostart enabled. Others remain stopped. The separate router and website units are not restarted by this command.

Runtime installation and global selection do not silently replace a production site's pinned worker. Update the site when ready. Router updates use a graceful restart. Database engine updates stay within a compatible line; major migrations require an explicit import.

Only accepted packages appear in the catalogs. The publisher checks reviewed compatible lines and builds paired architectures on the build Mac when it is running and its dependencies are available. It does not publish unreviewed new major lines or guarantee immediate availability after an upstream release.