Types of WaaS in InstaWP
Website as a Service (WaaS) in InstaWP allows you to sell pre-built websites to customers. Depending on the use case, InstaWP provides three different types of WaaS setups: Public, Private, and API-Based. Let’s explore how each works and when to use them.
- Public WaaS
- Private WaaS
- WaaS API Integration and how it works
Best for: Selling or offering pre-configured websites openly to users
Public WaaS allows users to instantly launch a site from your template without requiring a unique access link. These sites are readily available on your storefront or any public-facing page where you choose to share the template.
Keep the Allow Public Access to the WaaS toggle on if you wish to keep your WaaS public. You can find this setting in WaaS Settings > Options.
Key Features
Openly accessible to all users (can be behind a paywall, depending on your settings)
Can be embedded in a landing page or store
Ideal for freemium website models
May or may not allow demo site creation based on your WaaS settings
When to Use Public WaaS?
Public WaaS is intended for testing, demonstrations, and internal use only. To sell a WaaS site, it must have a unique link, as seen with private WaaS. Otherwise, it functions more like a rental property or a model home—accessible for viewing by all, but not ideal for individual ownership.
Best for: Controlling access to demo or paid websites.
Private WaaS ensures that only users with a special link can access your template. It provides a controlled environment where you can manage who gets to launch a site.
Once a private link is used/clicked, WaaS owner need to generate link again before sharing it with another client/user.
Keep the Allow Public Access to the WaaS toggle off if you wish to keep your WaaS public. You can find this setting in WaaS Settings > Options.
For a Private WaaS, you can find the Private Mode option on the WaaS page in your InstaWP dashboard.
Click Private Mode to find the API call URL, edit email content or generate link for your private WaaS.
Alternatively, you can call the URL for provisioning WaaS links programmatically & get a private unique link each time.
Key Features
Requires a private link for access
Useful for exclusive previews or gated trials
Better control over who uses your templates
When to Use Private WaaS?
You want to share your demo with selected clients.
You’re offering exclusive previews to subscribers or partners.
You have a premium WaaS model requiring restricted access.
For Private WaaS where payments are handled via third-party integrations, hosting must be free.
Best for: Advanced integrations, bespoke user experiences, and automated site provisioning
API-Based WaaS is designed for businesses that need direct integration between their platform and InstaWP. This method allows complete customization and programmatic site creation, enabling a seamless user experience without requiring them to visit InstaWP manually.
While it can be private or public, you must turn off these 2 settings for successfully enabling API integration:
Skip InstaWP demo site creation
Use InstaWP Payments in WaaS Checkouts
In the Branding Settings, set the field Send Webhook after Site Creation to:
The waas_slug and waas_stat_id parameters are required and will be sent automatically in the API call.
Once the WaaS setup is complete, you can initiate site creation via API. In the API request body, you need to include the following parameters:
name: Customer’s site name
email: Customer’s email address
plan_id: The hosting plan associated with the WaaS
Plan IDs can be found in the Hosting Settings tab of your WaaS.
Once logged in to the WaaS site, user will be able to see a Go Live button.
To integrate a third-party checkout system (e.g., WooCommerce, EDD, SureCart), you must add the checkout link to the Custom Redirect for Demo Site [Go Live] input field in InstaWP. This ensures that users completing a checkout will be redirected to the appropriate next step.
Once the user completes checkout, the API call triggers the site migration process.
For more details on WaaS integrations, including WooCommerce, SureCart, and WHMCS, visit our WaaS Integrations page.
Key Features
Fully automated site creation via API.
Seamless integration with existing workflows or SaaS platforms.
Support for third-party checkout solutions (WooCommerce, EDD, SureCart, etc.)
Customizable user journeys with API-driven logic.
When to Use API-Based WaaS?
You want to integrate WaaS with an external platform or another programming language.
You wish to white-label your WaaS-enabled site creation services.
You need a scalable, automated way to deploy WordPress sites with a tailored checkout flow.
- Public WaaS
- Private WaaS
- WaaS API Integration and how it works
1. Public WaaS
Best for: Selling or offering pre-configured websites openly to users
Public WaaS allows users to instantly launch a site from your template without requiring a unique access link. These sites are readily available on your storefront or any public-facing page where you choose to share the template.
Keep the Allow Public Access to the WaaS toggle on if you wish to keep your WaaS public. You can find this setting in WaaS Settings > Options.
Key Features
Openly accessible to all users (can be behind a paywall, depending on your settings)
Can be embedded in a landing page or store
Ideal for freemium website models
May or may not allow demo site creation based on your WaaS settings
When to Use Public WaaS?
Public WaaS is intended for testing, demonstrations, and internal use only. To sell a WaaS site, it must have a unique link, as seen with private WaaS. Otherwise, it functions more like a rental property or a model home—accessible for viewing by all, but not ideal for individual ownership.
2. Private WaaS
Best for: Controlling access to demo or paid websites.
Private WaaS ensures that only users with a special link can access your template. It provides a controlled environment where you can manage who gets to launch a site.
Once a private link is used/clicked, WaaS owner need to generate link again before sharing it with another client/user.
Keep the Allow Public Access to the WaaS toggle off if you wish to keep your WaaS public. You can find this setting in WaaS Settings > Options.
For a Private WaaS, you can find the Private Mode option on the WaaS page in your InstaWP dashboard.
Click Private Mode to find the API call URL, edit email content or generate link for your private WaaS.
Alternatively, you can call the URL for provisioning WaaS links programmatically & get a private unique link each time.
https://app.instawp.io/api/v2/waas/:waas_slug/:waas_stat_id/create-siteKey Features
Requires a private link for access
Useful for exclusive previews or gated trials
Better control over who uses your templates
When to Use Private WaaS?
You want to share your demo with selected clients.
You’re offering exclusive previews to subscribers or partners.
You have a premium WaaS model requiring restricted access.
For Private WaaS where payments are handled via third-party integrations, hosting must be free.
3. API-Based WaaS
Best for: Advanced integrations, bespoke user experiences, and automated site provisioning
API-Based WaaS is designed for businesses that need direct integration between their platform and InstaWP. This method allows complete customization and programmatic site creation, enabling a seamless user experience without requiring them to visit InstaWP manually.
While it can be private or public, you must turn off these 2 settings for successfully enabling API integration:
Skip InstaWP demo site creation
Use InstaWP Payments in WaaS Checkouts
In the Branding Settings, set the field Send Webhook after Site Creation to:
https://app.instawp.io/api/v2/waas/:waas_slug/:waas_stat_id/create-siteThe waas_slug and waas_stat_id parameters are required and will be sent automatically in the API call.
Once the WaaS setup is complete, you can initiate site creation via API. In the API request body, you need to include the following parameters:
name: Customer’s site name
email: Customer’s email address
plan_id: The hosting plan associated with the WaaS
Plan IDs can be found in the Hosting Settings tab of your WaaS.
Once logged in to the WaaS site, user will be able to see a Go Live button.
To integrate a third-party checkout system (e.g., WooCommerce, EDD, SureCart), you must add the checkout link to the Custom Redirect for Demo Site [Go Live] input field in InstaWP. This ensures that users completing a checkout will be redirected to the appropriate next step.
Once the user completes checkout, the API call triggers the site migration process.
For more details on WaaS integrations, including WooCommerce, SureCart, and WHMCS, visit our WaaS Integrations page.
Key Features
Fully automated site creation via API.
Seamless integration with existing workflows or SaaS platforms.
Support for third-party checkout solutions (WooCommerce, EDD, SureCart, etc.)
Customizable user journeys with API-driven logic.
When to Use API-Based WaaS?
You want to integrate WaaS with an external platform or another programming language.
You wish to white-label your WaaS-enabled site creation services.
You need a scalable, automated way to deploy WordPress sites with a tailored checkout flow.
Updated on: 04/03/2025
Thank you!