Solutions / WordPress
Deploy WordPress on any Linux VPS with a single click. Molixa Forge installs nginx, PHP-FPM, MySQL, and WP-CLI, drops in a fresh wp-config.php, wires Redis object cache, and hands you a working HTTPS URL. You keep full root access and pay only for the server.
This page walks through how the WordPress installer works, what gets tuned on your server, how per-site PHP settings and caching fit together, and how backups and staging keep your site safe while you build. If you are moving off cPanel or a managed host, read the short guide on deploying WordPress without cPanel for a full walkthrough.
Pick a domain, choose PHP 8.3 or 8.2, click install. The panel creates the database, user, site files, and SSL cert in under a minute.
nginx with FastCGI cache, PHP-FPM with a per-site pool, MySQL 8 with query cache sized to your RAM, and Redis object cache wired in.
One server and one WordPress site on the free plan with nightly backups and auto SSL. Pay only when you add more sites.
Install flow
Point a domain at your VPS, click install, and you have a live WordPress site in about a minute. No SSH sessions, no config editing, no shell pipelines.
The panel handles the parts you do not want to touch. It provisions a MySQL database with a strong random password, generates fresh WordPress salts, writes wp-config.php, runs wp core install, and requests a Let’s Encrypt certificate before the first visitor arrives. You pick the admin email and PHP version; Molixa does the rest.
What gets installed
Molixa installs the same class of stack that managed hosts charge you for every month. It sits on the server you already own, runs on the CPU you are already paying for, and never meters requests.
Page cache lives in nginx with a 10-minute default TTL. Cached requests bypass PHP entirely, so warm pages ship in under 30 ms.
Every site gets its own PHP-FPM pool. A slow plugin on one site cannot starve another site on the same server.
innodb_buffer_pool and query cache are sized from the VPS memory on first boot, then re-tuned when you resize the server.
WP-CLI is installed globally and pointed at every site. Run plugin updates, database exports, or bulk user imports from SSH or the web terminal.
Redis is installed, bound to localhost, and registered in wp-config.php. The Redis Object Cache plugin is pre-activated so query-heavy pages stop hammering MySQL.
Connect a GitHub or GitLab repo to deploy a theme or plugin on push. Build steps, env vars, and release history all live in the panel.
Per-site PHP settings
Every WordPress site gets its own PHP-FPM pool with independent memory and upload limits. No shared pool, no noisy neighbors, no one-size-fits-all php.ini.
Pick PHP 8.2 or 8.3 per site. Set memory_limit, upload_max_filesize, max_execution_time, and worker counts from the panel. Molixa writes the values into the pool config and reloads PHP-FPM without taking the site offline. If you want to edit php.ini by hand, the file sits in the usual place on disk and your changes survive panel updates.
Caching
A proper WordPress cache setup has two layers. Molixa installs both and keeps them in sync.
Full-page cache in nginx with a configurable TTL and smart bypass rules. Logged-in users, cart pages, and admin paths skip the cache. Auto purge fires on publish, update, comment, and WooCommerce order so content stays fresh without a cron job.
Expensive database queries, transient data, and autoloaded options live in Redis instead of MySQL. The Redis Object Cache plugin is pre-activated with a random auth key. On plugin-heavy sites, this alone cuts admin load time in half.
You do not need W3 Total Cache, WP Rocket, or LiteSpeed Cache on top of this stack. The caching is handled outside WordPress so plugin conflicts and expired transients stop being a thing you manage.
SSL and domains
Add a domain, get an SSL certificate. Molixa handles the DNS check, the certificate request, and the renewal 30 days before expiry.
The panel supports free Let’s Encrypt certificates for any domain that points to the server, wildcard certificates over DNS-01 for supported DNS providers, and custom certificates if your security policy requires one. HSTS, OCSP stapling, and TLS 1.3 are on by default. Redirects from www to apex or apex to www are one checkbox in the domain settings.
Backups and staging
Real safety nets for your site. Backups ship off the server every night; staging sites let you test updates without risking the live copy.
mysqldump plus a tar of wp-content, encrypted with your key, shipped to S3, Backblaze B2, DigitalOcean Spaces, Hetzner Storage Box, or SFTP. Retention defaults to 30 dailies and 12 monthlies, and you can extend both. Restores are per site, so you can roll one blog back to Tuesday without touching the others on the box.
Clone production to a staging subdomain, test a plugin update or theme change, then push the diff back to live with a single click. Staging sites are isolated by PHP-FPM pool and database schema, so experiments never leak into production traffic.
If you would rather compare panels before you commit, the SpinupWP alternative page breaks down feature by feature. Pricing is on the pricing page and starts at free.
FAQ
Yes. Every WordPress install ships with WP-CLI wired in and available over SSH or through the Molixa web terminal. You can run wp plugin update, wp db export, wp user create, wp search-replace, and any other command you use today. The AI assistant can also run WP-CLI on your behalf when you ask it to.
Yes. You can pick subdomain or subdirectory multisite when you create the site. Molixa sets the correct constants in wp-config.php, adds the nginx rewrites, and maps custom domains to individual network sites with their own SSL certificates. Each network site gets its own cache zone so a busy store does not starve a quiet blog.
Export the database and the wp-content folder from your current host, then import both into a fresh Molixa site. You can use WP-CLI, the All-in-One WP Migration plugin, or rsync plus mysqldump for bigger sites. We keep both sides warm until you flip the DNS record, so visitors never see downtime during the cutover.
It is usually better. cPanel tends to run Apache with mod_php, which is slow under load. Molixa installs nginx with PHP-FPM, FastCGI page cache, and Redis object cache by default. On a small Hetzner VPS, cached pages ship in under 30 ms and uncached WooCommerce pages land around 300 ms.
Yes. FastCGI cache bypasses logged-in users, cart and checkout pages, and any path you exclude, so builders and stores behave exactly as they should. Auto purge fires on publish, update, comment, and WooCommerce order, so your product grid stays fresh without manual intervention.
Yes. You can flip auto-updates on per site for core, plugins, and themes, and route pre-update snapshots to your backup target. If an update breaks the site, rollback is one click from the panel or a single WP-CLI command from the terminal.