PanelAlpha Engine changelog

Every release, what it fixes and which stacks it touches. One command to update.

Version 2.2.0

Read more on PanelAlpha Blog: PanelAlpha Engine 2.2

New Features

  • Move a WordPress site onto the engine. pae wordpress:migrate, the API or MCP wordpress_migration_create imports an existing WordPress site into a new or an empty classic project. The engine signs in to wp-admin, or you install the migrator plugin yourself from a link it gives you. An import can be followed, resumed, cancelled and deleted. Cancelling removes what it created here.
  • Test a source first. wordpress_migration_test checks a source without creating anything, and says which domain the import would get or why it would fail.
  • The site keeps its domain. The imported site keeps the source's domain. source_ip reaches the source while its DNS still points elsewhere. The import status shows progress and the DNS record to set.
  • Named WordPress operations. Plugins, themes, users, application passwords, a one-time login link, core, maintenance mode, cache flush, wp-config, options, auto-updates, search-replace, site language, database export and import. Each one is an API route under /projects/{username}/wp/, a pae wordpress:* command and a wp_* MCP tool.
  • skip_plugins. Every operation can skip plugins and themes, so a site with a broken plugin can still be fixed.
  • Core status. Core status says whether WordPress is installed, has no config or cannot reach its database. A site that fails to load is reported as an error, never as not installed.
  • Page cache flush. Cache flush also purges WP Super Cache, LiteSpeed Cache, W3 Total Cache, WP Rocket and WP Fastest Cache.
  • WP-CLI in containers. The raw WP-CLI command and the named operations also run on WordPress in a project's own containers.
  • CPU and memory per project. The engine samples every project and its containers each minute and keeps 30 days of hourly averages. Each project carries its latest usage. project_metrics_history charts a project and container_metrics shows each container.
  • Server history. metrics_history returns server metrics for the last hour, day, week or month, now with disk usage.
  • Monthly bandwidth on every project. Project lists carry this month's transfer, so a list no longer needs one usage call per project.
  • Session length. Visitor statistics add the average session length per day.
  • App status on every project. Each project reports its app type, status (live, building, failed, down, suspended), public address and whether admin login is supported.
  • Host details. GET /system/info adds the hostname, OS, kernel, uptime, CPU cores, RAM, data disk size and main IPv4.
  • Token rotation. A token can rotate itself: the new one keeps the name, permissions and lifetime, and the old one works for 10 minutes more. A token can also revoke itself.
  • Activity log filters. The MCP activity log filters by token and project, also in pae mcp:log:list.
  • Webhooks registered at the provider. pae git:deploy-hook --register also creates the webhook at GitHub, GitLab or Bitbucket, including self-managed GitLab and GitHub Enterprise. Rotating updates it and deleting removes it.
  • Signed GitLab webhooks. Signed GitLab deliveries are verified. Hooks created before 2.2.0 keep working; rotate one to switch it to signed deliveries.
  • Cloudflare from your assistant. With a project's own Cloudflare token, your assistant can show the zone settings, purge the cache and change the security level, including Under Attack mode. Errors name the missing permission.
  • SSL check. pae ssl:check (MCP ssl_check) shows the certificate a domain really serves, from public DNS and from the engine, with its chain.
  • Private key from the vault. A custom certificate's private key can be given as a vault: reference.
  • Self-signed warning. A proxy rule on port 443 that would get the host's self-signed certificate returns a warning saying how to get a real one.
  • Trusted certificates for wildcard rules. A rule on 443 such as *.example.com is served with a trusted certificate on the server that covers its name.
  • ModSecurity rule report. Install and update list ModSecurity rule files on the host that differ from the shipped ones, without changing them.

Improvements

  • Git. Git commands the engine runs against a URL you give, submodules included, accept only http, https and ssh with a deploy key, and refuse internal addresses. The git token is given only to the project's own git host.
  • Vault keys. References use a random key instead of a sequential id. Values set from the vault stay masked. This changes how references are written.
  • Mail secrets. The mail settings no longer return stored secrets, only whether each one is set. A save keeps a secret sent empty. Read-only MCP tokens can now read the mail settings. This changes its response.
  • Scoped tokens. A project-scoped token can clone or copy only into a project on its own list. Deleting a project removes it from every token scope.
  • Account files. File operations, archive extraction and Compose volumes stay inside the project's home.
  • Image updates. The engine and account images are rebuilt with the latest OS security updates.
  • Unlimited (-1). -1 means unlimited on every project limit except memory, and an unlimited project reports -1 for disk and usage. Domains, databases and FTP or SFTP accounts can now be created on a project with unlimited limits. This changes its response.
  • Minimum memory. A memory limit below 256 MB is refused for a container project, which needs it for its own Docker daemon.
  • FTP quota. An FTP account on a project with unlimited disk gets no quota.
  • Separate container copies. A staging copy, clone or push of a container project gets its own database, public address, account, env vars and tokens, instead of sharing the source's.
  • Images and volumes in copies. A copy fetches the images it needs first. Copies of images that declare their own volumes, such as the official WordPress image, no longer fail.
  • Classic WordPress copies. A copy points WordPress at its own database and domain, and a push keeps the target's. A copy of a classic WordPress project needs its databases copied, instead of sharing the live site's database. This changes its behaviour.
  • Push rollback. A push that fails, or whose app keeps restarting, is rolled back completely and no longer blocks the next push.
  • Empty container push. A container push with nothing to carry is refused with 422 before anything stops. This changes its behaviour.
  • Build memory in accounts. Builds inside a container project's account are held to the build memory limit and the project's limit.
  • Submodules on redeploy. A redeploy keeps a submodule that can no longer be fetched, and warns.
  • Missing base image. A PHP deploy whose base image was removed by the daily cleanup rebuilds it instead of failing.
  • Cancelling. A cancelled deploy ends at once and leaves the running version alone.
  • Railpack and volumes. Railpack projects can be redeployed, and anonymous Compose volumes keep their data across a recreate.
  • WP-CLI route. The raw WP-CLI route is POST /projects/{username}/wp/command. The old wp-cli/command route still works but is deprecated, as is pae domain:wp-cli in favour of pae wordpress:command.
  • WordPress recipe. WP-CLI database commands work, and the database stays healthy after an upgrade from 2.0.x.
  • PHP version. WP-CLI on PHP hosting uses the PHP version of the domain that serves the path, instead of always 8.3.
  • Name check. project_verify_name answers 200 for a well-formed name that is taken, with valid: false and a reason. Only a name that breaks the rules is still 422. This changes its response.
  • Project delete. Deleting a project ends its open SFTP sessions first.
  • Unzip conflicts. Unzip answers 409 when the destination already holds one of the archive's entries, instead of overwriting it. This changes its behaviour.
  • Proxy rules on site names. An HTTP rule named after a domain alias or a classic PHP project's domain is refused. Such rules were stored but never served. This changes its behaviour.
  • Firewall edits. Changing a deny rule also closes the ports Docker publishes.
  • ModSecurity and WordPress. With OWASP CRS on, the WordPress REST API, the block editor and Elementor saves are no longer blocked. A rule file you switched off stays off after updates.
  • sysbox accounts. Accounts on some hosts are no longer recreated every five minutes.
  • Current metrics. Current CPU is reported instead of the average since boot.
  • SSL trust. A certificate served without its intermediates is no longer reported as trusted.
  • Task log pages. task_get and task_log_list return logs in pages (limit, default 500), so a long log fits an MCP result. This changes its response.
  • Token name filter. The activity log's token name filter matches part of a name, ignoring case. This changes its behaviour.
  • Commands that cannot ask. Without a terminal, a pae command that needs a confirmation and has no --force exits 1 instead of 0. This changes its behaviour.

Try PanelAlpha Engine yourself.

The simplest way to turn your server into a safe, controlled environment for your AI agent. Deploy, manage and maintain any project from Claude Code, Cursor, Codex or any other MCP client. Open source and free to run.

Requires Ubuntu 24.04 or 26.04 · 2 GB RAM · 1 CPURead the documentation