WordPress hosting

Run WordPress on infrastructure you control.

Install, cache, secure and back up WordPress and WooCommerce from one panel on your Debian or Ubuntu server. Every WordPress feature is included in the licence — no toolkit editions, no per-site count.

1 clickWordPress or WooCommerce, database and HTTPS included
3 PHPversions side by side, pinned per site
nginxpage cache with WordPress-aware bypass, Redis objects
∞ sitesper server, each its own Linux user

One-click WordPress and WooCommerce

Pick WordPress from the application catalogue, give it a domain, and auraPanel does the rest in one transactional pass: an isolated Linux user for the site, an nginx vhost from the WordPress template, a MariaDB database with its own credentials, the core download and wp-config, the admin user, and an HTTPS certificate. The site is live when the progress bar finishes.

WooCommerce is its own catalogue entry: the same install, then the WooCommerce plugin fetched and activated, so a storefront starts from the panel rather than from the plugin screen. WP-CLI is fetched on demand the first time a WordPress site is created, so hosts that never run WordPress never carry it.

  • Database, admin user and certificate created for you
  • WooCommerce variant with the plugin pre-activated
  • WP-CLI available on the host once WordPress is

Caching that knows WordPress

Full-page caching is nginx fastcgi_cache, turned on per site and purgeable from the panel. The WordPress template carries its own exclusions, so /wp-admin/, the login page, the cart and the checkout are never served from cache while the public pages are. Redis backs the object cache for plugins that use it.

Because the cache is in nginx rather than a plugin, it works for every theme and needs nothing installed inside WordPress.

  • nginx fastcgi_cache with WordPress-aware bypass rules
  • Redis object cache
  • Per-site toggle and purge

PHP versions per site

PHP 8.3, 8.4 and 8.5 install side by side from deb.sury.org and each site pins its own version with its own PHP-FPM pool and Unix socket. Move one site to a new PHP release without touching the others; keep an older plugin stack on 8.3 while new builds run 8.5. Add versions later from Settings without reinstalling.

  • PHP 8.3 / 8.4 / 8.5 side by side
  • One PHP-FPM pool per site
  • Pin and change per site

Every site in its own Linux user

A compromised plugin on one WordPress site cannot read another site’s wp-config.php: each site runs as its own UID with a chroot-jailed SFTP account, and its PHP-FPM pool runs under that user. That is the isolation shared hosting sells, on a server you own, for every site on the box.

Automatic HTTPS is issued in-process (HTTP-01, or Cloudflare DNS-01 for wildcard and proxied domains), and the Cloudflare Edge Shield can lock a site’s origin to Cloudflare’s IP ranges so it only answers traffic that came through the proxy.

  • Per-site UID and chroot SFTP
  • Automatic HTTPS, Cloudflare DNS-01 supported
  • Origin lock for Cloudflare-proxied sites

Restore points for every site

Scheduled backups capture the WordPress files and database together, to local storage or any rclone-compatible remote. A restore can go over the existing site or into a new one — and when it lands in a new site auraPanel re-homes the database credentials, so the copy runs against its own database instead of quietly writing to the original’s. That is how you make a working copy of a client site to test an upgrade.

On-demand backups run as background jobs, so a multi-gigabyte media library finishes even if the browser tab is closed.

  • Files and database in one restore point
  • Restore over the site or into a new one
  • Local storage or rclone remotes

Included, not an add-on

cPanel and Plesk sell WordPress management as a toolkit with its own editions and limits. In auraPanel there is nothing to add: the install, the cache, the PHP versions, the isolation and the restore points are the panel, for every site, on one per-server licence with no site count.

Frequently asked

Does auraPanel manage WordPress updates for me?

No. auraPanel installs, isolates, caches and backs up WordPress; core, theme and plugin updates stay in WordPress itself (or WP-CLI, which is on the host). Panel updates are separate and can be automatic.

Can I move an existing WordPress site in?

Yes — restore a backup of the files and database into a new site. The credential re-home step points the copy at its new database. There is no one-click importer from another panel today.

Which database does WordPress use?

MariaDB. auraPanel also ships PostgreSQL for applications that support it (Laravel, Moodle, Drupal and others), and auraDB opens either engine in the browser.

Is there a limit on WordPress sites?

No. A licence covers the server and everything on it. Practical capacity is your server’s memory and CPU, which auraPanel tunes MariaDB, Redis and PHP-FPM against at install.

Try the live demo

A real auraPanel on a real server, shared with everyone. Sign in with the demo account and click around.

Email
demo@goaura.one
Password
demo1234
Open the demo panel ↗

Shared public demo, so please don’t put anything personal in it. More about the demo →

Talk to us

Tell us what you need and how to reach you. A person reads this, not a queue.

We use these details only to reply to you. Privacy

Recent updates

What shipped in the last releases. With automatic updates on, each lands on your server the moment it is published.

  1. v1.21.3
    Framework sites were undetectable, and a restore could silently point the copy at the original's live database.

    DetectApp looked for each application's signature relative to the docroot — but every PHP framework in the registry serves from a subdirectory (DocrootSub: public, webroot, web, pub, docroot) and keeps the file that identifies it one level *above* that. So the Laravel signature searched <project>/public/artisan,…

  2. v1.21.2
    Restarting nginx now blocks the panel and reconnects, instead of showing a notice.

    v1.21.1 stopped the false "HTTP 520" but only put up a toast — and a toast is the wrong affordance when the panel itself is about to go away: the page sat there looking broken while every request failed underneath it.

  3. v1.21.1
    Restarting nginx from Services no longer reports a false failure.

    It showed "Restart failed — HTTP 520". The panel is reverse-proxied *by* nginx, so the request deadlocked against itself: the handler blocked waiting for the restart to finish, while nginx's graceful stop waited for that very request to drain. Neither could proceed until nginx's stop-retry timeout force-killed it,…

  4. v1.21.0
    Per-site X-Frame-Options, fixing page builders that couldn't load their preview.

    Elementor's editor failed with *"Multiple 'X-Frame-Options' headers with conflicting values ('DENY, SAMEORIGIN')"*. The cause is that nginx's add_header appends rather than replaces: when the application also sets the header — a WordPress security plugin, or a CDN transform — the browser received two values,…

  5. v1.20.6
    The multi-database restore refusal now says what is in the backup and what still works.

    It read only "Restoring a multi-database site isn't supported yet", which is a dead end: it named neither the databases involved, nor why one of them is the limit, nor any route forward.

  6. v1.20.5
    Services: cards in a row now match heights.

    Like the settings grid before it, the Services grid pinned each card to its own content height, so a row often showed one card noticeably shorter than the card beside it. Each row now takes the taller card's height and both fill it, and it re-balances as content changes — a runtime installed, a longer service list.

  7. v1.20.4
    Settings: paired cards now match heights.

    Organisation / Panel Domain and auraPanel Updates / Session timeout each sat at their own content height, so a row showed one card visibly shorter than its neighbour. Each row now takes the taller card's height and both fill it — driven by content, not a fixed value, so it still adapts as a card grows (a validation…

  8. v1.20.3
    Settings: Organisation and Panel Domain now share a row too.

    They were full-width blocks stacked above the rest of the page; they now sit side by side in the same two-column grid as the Updates / Session timeout pair, so the top of Settings reads as two tidy rows instead of four stacked bands. Both cards shrink cleanly — the logo drop zone is a fixed 44×44 and the name field…

All releases on GitHub ↗