InstaWP is a managed WordPress hosting provider with a built-in WaaS (Website as a Service) feature that lets agencies create, sell, and manage WordPress sites as subscriptions. By default, WaaS works natively with InstaWP hosting, which handles infrastructure automatically.
But some agencies already have existing contracts with other hosting providers, specific data center requirements, or infrastructure setups that make InstaWP hosting impractical for their situation.
The good news: InstaWP WaaS supports non-native hosting providers through a control panel bridge. This guide covers exactly who should use this approach, how to configure it step by step, how to troubleshoot common issues, and when you should simply switch to InstaWP’s native hosting instead.
Key Takeaways
- InstaWP WaaS natively supports InstaWP hosting; connecting a non-supported provider requires an intermediary control panel (Runcloud or ServerAvatar).
- You need a VPS or dedicated server with root access from your preferred hosting provider. Shared hosting is not supported for this integration.
- The six-step process: identify a supported control panel, provision a VPS, install and configure the control panel, connect it to InstaWP, verify with a test site, and assign it to your WaaS.
- Multisite WaaS only works with InstaWP hosting. Non-supported hosting integration is for single-site WaaS only.
- If you are starting fresh or have flexibility in your hosting choice, InstaWP hosting is strongly recommended as it eliminates server management entirely.
- Common integration failures are usually caused by firewall rules blocking API communication or incorrect API key entry. Both are fixable in under five minutes.
Table of Contents
Who Should Use Non-Supported Hosting with InstaWP WaaS?
This approach is appropriate in three specific scenarios:
- Existing hosting contracts: You have a prepaid VPS or dedicated server arrangement with a provider like DigitalOcean, Vultr, Hetzner, Linode, or AWS and want to run your WaaS on that infrastructure rather than paying separately for InstaWP hosting.
- Specific regional data center requirements: Your clients require hosting in a specific country for data residency or compliance reasons, and InstaWP hosting does not currently offer a data center in that region.
- Server customization needs: You need server-level control (custom nginx configuration, specific PHP extensions, custom security policies) that managed hosting does not expose.
If none of these apply to you, skip to the section below on InstaWP’s native hosting. The integration described in this guide adds significant complexity and server management responsibility. For most agencies, InstaWP hosting is the right choice.
Prerequisites
Before starting the integration, confirm you have the following in place:
- Active InstaWP account: Your InstaWP account must be on a paid plan that includes the WaaS feature.
- VPS or dedicated server with root access: Shared hosting is not supported. You need a VPS or dedicated machine from your preferred provider. Minimum recommended specs for a WaaS running up to 20 client sites: 4 CPU cores, 8 GB RAM, 100 GB SSD. Scale up as your subscriber count grows.
- Supported control panel: The integration works through a supported server management control panel that acts as the bridge between your hosting provider and InstaWP. Currently supported: Runcloud and ServerAvatar.
- Basic server management knowledge: You should be comfortable with SSH, running shell commands, and navigating a server control panel interface. If you are not, use InstaWP hosting instead.
Important: Multisite WaaS limitation
InstaWP WaaS multisite deployments only work with InstaWP hosting. Non-supported hosting integration is for single-site WaaS only. If you need to sell WordPress Multisite subscriptions through your WaaS, InstaWP hosting is required.
Step-by-Step Integration Guide
Step 1: Identify a Supported Control Panel
InstaWP connects to non-native hosting via supported server control panels. These control panels expose an API that InstaWP uses to provision WordPress sites, configure domains, and manage hosting resources on your server. Currently supported control panels are:
Both support modern server environments running Ubuntu or Debian, nginx or Apache, and PHP 8.x. Choose whichever panel you are more familiar with. Both provide a clean management interface and API documentation you will need later.
Step 2: Provision Your VPS
Log in to your preferred hosting provider (DigitalOcean, Hetzner, Vultr, Linode, or any VPS provider) and create a new server. Recommended base configuration: Ubuntu 22.04 LTS, 4 vCPU, 8 GB RAM, 100 GB SSD. Select a data center region appropriate for your client base.
Once the server is provisioned, note the public IP address. Connect via SSH as root: ssh root@YOUR_SERVER_IP. Confirm you have root access before proceeding. Without root access, the control panel installation will fail.
Make sure port 22 (SSH), port 80 (HTTP), and port 443 (HTTPS) are open in your provider’s firewall rules. Some providers block these by default. You will also need to open the control panel’s management port (varies by panel; check the documentation).
Step 3: Install and Configure the Control Panel
Follow the official installation documentation for your chosen control panel:
- For Runcloud: visit runcloud.io, create an account, click Add Server, and run the one-line installation script it provides on your VPS via SSH.
- For ServerAvatar: visit serveravatar.com, create an account, click Connect Server, and run the provided installation script on your VPS via SSH.
The installation typically takes 5 to 10 minutes. Once complete, verify that your server appears as connected and healthy in the control panel dashboard. Check that the web stack (nginx or Apache plus PHP) is running by visiting your server’s IP in a browser and confirming a default server page loads.
Step 4: Connect the Control Panel to InstaWP
Log in to your InstaWP dashboard at app.instawp.io. In the left sidebar, click Hosting. Click Connect Hosting.
From the list of Connect Providers, select your control panel (Runcloud or ServerAvatar). InstaWP will prompt you for API credentials. Retrieve these from your control panel’s API settings page:
- In Runcloud: go to Account Settings, then API Key, and generate a new key.
- In ServerAvatar: go to Profile Settings, then API Token, and generate a token.
Enter the API key in the InstaWP connection prompt and click Connect. If the connection succeeds, your server will appear in InstaWP’s Hosting list within a few seconds. If it fails, verify the API key was copied correctly and that your server’s control panel management port is not blocked by a firewall.
Step 5: Verify the Connection with a Test Site
Before connecting this server to your WaaS, verify that InstaWP can provision a WordPress site on it. From the Hosting page in InstaWP, click + New Site. Select Choose from Supported Providers as your method.
On the next screen, select your newly connected Hosting Account, the Server, a User, and the PHP version. Set a test domain name and optionally pre-select plugins and themes to install. Click Go Live, then confirm in the dialog that appears.
The site will provision within a few minutes. When it appears in your Hosting page dashboard, log in to your control panel and confirm the application is listed there as well. Visit the site’s domain in a browser to confirm it loads a default WordPress installation. If it does, the connection is verified and working.
Step 6: Connect Your WaaS to Your Server
Now that the connection is verified, you can create your WaaS product and assign it to this server. In InstaWP, go to Sell, then WaaS, then Add New. Complete the WaaS setup (name, templates, plans, branding) as you would for any WaaS.
The critical step is in the Hosting Settings of each pricing plan. Under Server Alias, select your connected hosting account instead of InstaWP hosting. Under Servers, select the specific server you configured. Set the remaining options (Pack, PHP version, user role) and save the plan.
When a client subscribes through your WaaS landing page and completes payment, InstaWP will automatically provision their WordPress site on your non-supported hosting server using the control panel API.
The client experience from their perspective is identical to InstaWP hosting: they receive a confirmation email with a Magic Login link and access their site through the Branded WaaS Portal under your domain.
Want to skip the server management entirely?
Use InstaWP hosting InsteadTroubleshooting Common Issues
When to Use InstaWP’s Native Hosting Instead
The integration described in this guide works, but it adds meaningful operational complexity. Before completing it, consider whether InstaWP hosting would serve your needs better.
Use InstaWP hosting when:
- You are starting a new WaaS and have no existing hosting contracts. InstaWP hosting eliminates server provisioning, control panel management, SSL configuration, and resource monitoring. You configure your WaaS plans and InstaWP handles everything from there.
- You want to sell multisite WordPress subscriptions. Non-supported hosting integration does not support multisite WaaS. InstaWP hosting is the only option for multisite.
- You do not have (or do not want to develop) server administration expertise. The non-supported hosting path requires comfort with SSH, control panel configuration, and server-level troubleshooting. If something breaks at 2 AM, you are the one fixing it.
- You want InstaShield, InstaCDN, and the Vulnerability Scanner to work natively. These InstaWP security and performance features are fully integrated with InstaWP hosting infrastructure and may not be available or require additional configuration on non-supported hosting.
Use non-supported hosting when:
- You have an existing VPS contract with significant remaining pre-paid capacity.
- You need to place client sites in a specific data center or country that InstaWP hosting does not serve.
- You need server-level configuration control that managed hosting does not provide.
Practical guidance: If you are evaluating this integration as a cost-saving measure versus InstaWP hosting, factor in the time cost of server management. A single unplanned server issue taking two hours to debug costs more in agency time than months of InstaWP hosting fees for a small WaaS. Calculate total cost of ownership, not just hosting line items.
Best Practices After Integration
- Automate server software updates: Configure unattended security updates on the server for the OS. Update the control panel and its web stack components on a regular schedule to stay current with security patches.
- Implement server-level and site-level backups separately: Your server control panel likely provides server-level snapshots. Use these alongside InstaWP’s per-site backup capability. Having both means you can restore a single site without touching the entire server, and restore the entire server without losing per-site data.
- Set resource monitoring alerts: Configure CPU, RAM, and disk usage alerts in your control panel or VPS provider dashboard. An alert at 80% disk usage gives you time to resize before sites start failing. An alert at 90% CPU gives you time to scale before performance degrades for clients.
- Configure a server-level firewall: Enable UFW (Uncomplicated Firewall) or your provider’s firewall to block all ports except 22 (SSH), 80 (HTTP), 443 (HTTPS), and any ports your control panel requires. This reduces your attack surface significantly.
- Test provisioning monthly: Subscribe to your own WaaS with a test email once a month and verify the full provisioning flow. Confirm the site provisions, the Magic Login link works, the Branded Portal shows the site correctly, and billing processes. Catching a broken flow in a test is far better than discovering it through a client complaint.
Conclusion
Connecting a non-supported hosting provider to InstaWP WaaS is a viable path for agencies with specific infrastructure requirements. The process involves installing a supported control panel (Runcloud or ServerAvatar) on a VPS, connecting it to InstaWP via API, verifying the connection with a test site, and assigning it to your WaaS plans.
The client experience is identical to InstaWP hosting from the subscriber’s perspective: Magic Login delivery, Branded WaaS Portal access, and automatic site provisioning on purchase.
That said, this path comes with server management responsibility that InstaWP hosting eliminates entirely. Evaluate honestly whether your situation requires a non-supported hosting integration or whether InstaWP’s native infrastructure is the simpler, more reliable path for your WaaS business.
Build your WaaS on InstaWP’s managed infrastructure
No server management. No control panels. Just templates, billing, and a branded portal.
Join the InstaWP Agency ProgramFAQs
Can I use shared hosting with InstaWP WaaS?
No. Shared hosting does not provide the root access or isolated server environment required for the control panel integration. InstaWP WaaS with non-supported hosting requires a VPS or dedicated server.
Which control panels does InstaWP support for non-native hosting integration?
Currently Runcloud and ServerAvatar. These act as the API bridge between InstaWP and your VPS. Check the InstaWP documentation for the most current list as this may expand.
Does non-supported hosting work for multisite WaaS?
No. Multisite WaaS requires InstaWP hosting. Non-supported hosting integration is for single-site WaaS deployments only.
Will clients see any difference if their site is on non-supported hosting vs InstaWP hosting?
No. From the client perspective, the experience is identical: they receive a Magic Login link by email and access their site and billing through the Branded WaaS Portal at your domain.
What happens if my VPS runs out of resources as my WaaS grows?
New site provisioning will fail or degrade. Monitor your VPS CPU, RAM, and disk usage through your control panel and set alerts at 80% thresholds. When approaching capacity, either upgrade the server tier at your hosting provider or add a second server and configure additional WaaS plans pointing to it.
Can I switch from non-supported hosting to InstaWP hosting later?
Yes, but it requires migrating existing client sites to InstaWP hosting and updating the hosting settings on your WaaS plans. New subscriptions after the change will provision on InstaWP hosting. Existing sites need to be migrated using the InstaWP Connect plugin and then reassigned.
Are InstaShield and InstaCDN available on non-supported hosting?
InstaShield and InstaCDN are InstaWP infrastructure features that are native to InstaWP hosting. Their availability and behavior on non-supported hosting may differ. Check the InstaWP documentation for the current feature matrix across hosting types.
