Run your own WHMCS installation for hosting, domains, client billing and support workflows. We prepare a hardened KVM VPS around the requirements of your chosen WHMCS release, including PHP, ionCube Loader, a MySQL-compatible database, HTTPS and the system cron environment. You supply the WHMCS licence and application files, then manage the application after handover.
Full root & SSH NVMe storage Daily backups Anti-DDoS 99.9% uptime SLA 11 locations
Root and SSH access
Manage PHP, cron and server configuration.
Reserved resources
Dedicated vCores and RAM for your workload.
Daily backups
Automatic backup of the previous 24 hours.
Hardened handover
Baseline server security before you take over.
WHMCS depends on a compatible PHP stack and reliable scheduled tasks. A VPS gives you control over that environment and the resources it uses.
WHMCS requirements change by version. Confirm its supported PHP, ionCube Loader, database and extension requirements before choosing the runtime.
The WHMCS system cron performs recurring application tasks. Configure and monitor it using the command and interval documented for your release.
Use Linux ownership and web-server rules to protect configuration, vendor and storage paths as WHMCS documentation specifies.
Client count, invoice volume, ticket imports and modules affect CPU, memory and database load. Start with a measured workload and scale when needed.
A conventional Linux web stack with the exact versions and extensions required by your WHMCS release.
Request from a browser or app (HTTPS)
HTTPS and domain
A public domain, valid TLS and secure admin access.
Apache with rewrite
WHMCS documents Apache and rewrite rules for friendly routes; verify any alternate web server against its support guidance.
PHP and ionCube
Choose a compatible PHP release and matching ionCube Loader; align CLI PHP with web PHP.
MySQL-compatible database
Use a dedicated database and account with the privileges required for installation and updates.
WHMCS cron
Run the documented cron task on schedule and review system health after setup.
Client accounts, service billing and renewal workflows.
Registrar integrations and domain-related order workflows.
Client tickets, notifications and staff operations.
Recurring actions that depend on the WHMCS cron process.
Shared hosting is a good place to start. When a busy site keeps hitting its account limits, a VPS removes them.
A VPS is unmanaged: we install and secure it for you, then you run it. Prefer us to run everything? See managed hosting.
A small installation may fit VPS-1. Choose based on concurrent staff, client activity, database size, modules and any workloads sharing the server.
Small websites, APIs, bots and development servers.
Production apps, WordPress and online stores.
Busy stores, SaaS products and several projects.
High-traffic apps, large databases and agencies.
* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.
Prices exclude 18% GST, which is added to invoices for customers in India.
These are starting points, not WHMCS minimum requirements. Monitor actual PHP and database usage after launch.
| Workload | Start with | Why |
|---|---|---|
| New or low-activity installation | VPS-1 2 vCores · 4 GB RAM | A starting point for the app and database on one server. |
| Active billing with a small team | VPS-2 4 vCores · 8 GB RAM | More memory for concurrent admin and client activity. |
| Busy portal or heavier integrations | VPS-3 6 vCores · 12 GB RAM | Additional resources for database and background work. |
| Several substantial services together | VPS-4 8 vCores · 24 GB RAM | For larger combined workloads; separate critical services where appropriate. |
A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.
Check the exact WHMCS release requirements before selecting any host.
| Feature | Shared hosting | VPS |
|---|---|---|
| PHP and ionCube | Host-supported combinations | Choose a compatible stack with root access |
| Scheduled cron | May have limits | Configure the documented system cron |
| Server configuration | Provider controls it | You control it after handover |
| Resource isolation | Shared account limits | Reserved plan resources |
| Administration | Host manages server | Self-managed after setup |
| Explore Shared hosting | See Plans |
Use the requirements page for the exact WHMCS version and check every add-on separately. These commands are illustrative; adjust paths and PHP binaries to your release.
Record the WHMCS, PHP, ionCube, database and extension requirements before installation.
Use a unique database and strong database account; grant only the privileges WHMCS documents for the current task.
Follow the official installation steps, file ownership guidance and web-server rules.
Use the exact cron command from your WHMCS admin area and verify its execution.
# 1. Confirm supported versions
php -v
php -m
# 2. Create a dedicated database
mysql -u root -p
# 3. Install and protect the application
sudo apachectl -t
# 4. Configure scheduled automation
crontab -e
php -v
Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).
The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers do the first setup once, free, so you start from a hardened server with WHMCS in place.
Pick the resources you need and the datacentre closest to your users.
Versions, database and domain: at order or right after.
Server hardened, WHMCS installed and tested, HTTPS on your domain.
SSH access to a working server, ready for your code and data.
Not included in the free setup, but we can quote for it. No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost; cPanel and Plesk need their own licence.
The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.
| Virtualisation | KVM with reserved vCores and RAM |
|---|---|
| Storage | NVMe SSD on every plan |
| Network | Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan |
| Operating systems | Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD |
| Access | Full root over SSH, key-based login |
| Backups | Automatic daily backup of the previous 24 hours; snapshots and longer retention on request |
| Protection | Always-on anti-DDoS mitigation |
| Availability | 99.9% uptime SLA |
Asia-Pacific
Europe
North America
Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.
Teams that want control of their WHMCS files, database and server environment.
Operators who need a billing portal integrated with their own workflows.
People prepared to maintain WHMCS, PHP, modules, backups and security.
WHMCS is a third-party product. Siteharbour is not affiliated with WHMCS; a separate WHMCS licence may be required.
Not covered here? Ask an engineer before you order.
Choose a plan and share the WHMCS release requirements, PHP version and modules you plan to use. We prepare the server environment; you retain control after handover.
Check if the name you want is free. You can register a domain on its own, or choose it when you order hosting.
