Selling websites one at a time is slow. Building each project from scratch, configuring hosting, setting up domains; it eats into your margins and limits how many clients you can serve. That’s why more agencies and WordPress professionals are turning to the WaaS (Website as a Service) model, where customers pick a template, choose a plan, and get a fully working website delivered to them automatically.
This guide covers the full journey: building your WaaS, configuring a branded suffix domain so every new site carries your name, and mapping custom domains to individual client sites when they’re ready to go live. Whether you’re launching your first WaaS product or cleaning up the domain setup on an existing one, every step is laid out here.
Table of Contents
What Is WaaS on InstaWP?
Before diving into domain mapping, it helps to understand what WaaS actually is on the InstaWP platform.
WaaS stands for Website as a Service. It is a feature within InstaWP that lets you create pre-built WordPress templates, pair them with hosting plans, and offer them to your customers as a self-serve product. Your clients visit a branded landing page, pick a template, choose a hosting plan, and get a fully provisioned WordPress website; all without you lifting a finger.

Think of it as your own mini website builder platform, powered by InstaWP behind the scenes. You set the pricing, branding, templates, and hosting configurations. InstaWP handles the infrastructure.
The problem? By default, every site your customers create gets an InstaWP-generated domain like sitename.instawp.xyz. That’s fine for staging and testing, but it’s not going to cut it when your client wants to launch their actual business website. That’s where domain mapping comes in.
Why Having a Custom Domain Matters for Your WaaS Business
When someone pays for a website through your WaaS, the URL is one of the first things they notice. A domain like clientsite.instawp.xyz immediately tells them they’re using someone else’s platform. A domain like clientsite.youragency.com tells them they’re using yours. That difference shapes how they perceive your entire service.
- It establishes trust before the first conversation: Clients researching your offering will judge it by the details. A branded domain signals that you’ve invested in your product. It tells them this isn’t a side project; it’s a business. The moment they see a generic third-party URL, that confidence takes a hit, and you haven’t even spoken to them yet.
- It makes your service feel like a product, not a resale: Without a custom domain, your WaaS looks like a thin wrapper around someone else’s infrastructure. With one, it feels like a standalone platform. Clients don’t need to know what’s running behind the scenes; they just see a polished, consistent experience under your name.
- It protects your brand as you scale: If you build a reputation on InstaWP-generated domains and later decide to switch providers or bring hosting in-house, every URL your clients rely on breaks. A custom domain that you own and control stays with you no matter what happens to the underlying infrastructure.
- It simplifies your client’s path to going live. When a customer is ready to launch, having a clean domain structure already in place means fewer steps, fewer DNS headaches, and fewer support tickets. They either keep the branded subdomain you’ve provided or map their own domain; either way, the foundation is already solid.
- It unlocks white-label positioning: InstaWP’s domain mapping works alongside its white-label features. Once your suffix domain is active and the InstaWP branding is removed, there is nothing visible to your client that points back to InstaWP. As far as they’re concerned, this is your platform, built by you, for them.
How to Create a Website-as-a-service With Custom Domain
The best way to create a Website-as-a-Service with a custom domain is through InstaWP, an all-in-one cloud for WordPress that handles the hosting, provisioning, and delivery while you control the branding, pricing, and templates.

InstaWP stands out because it was designed specifically for this use case. You’re not stitching together five different tools to make it work. Everything lives under one roof: template creation, hosting plan configuration, pricing setup, branded landing pages, domain mapping, SSL provisioning, and white-label customization. That level of integration is hard to find anywhere else without building a custom stack from scratch.

- No infrastructure management. You don’t need to manage servers, configure nginx, or set up load balancers. InstaWP provisions every site on its own hosting infrastructure. You pick the server plan, and the platform handles deployment, scaling, and maintenance.
- Templates built from real WordPress sites. Your WaaS templates aren’t limited to a drag-and-drop builder. You can turn any fully built WordPress site into a template, complete with plugins, themes, content, and settings. Every customer who signs up gets an exact copy of that site, ready to customize.
- Built-in billing and plan management. InstaWP lets you create multiple pricing tiers with different hosting allocations, template costs, and suffix domains. You set the monthly or yearly pricing, and the platform handles the checkout flow for your customers.
- Self-serve experience for your clients. When a customer visits your WaaS link, they see a branded landing page where they can pick a template, choose a plan, enter their information, and get a working website in minutes. No back-and-forth emails, no manual setup on your end.
- Domain mapping at every level. This is where InstaWP really shines for WaaS. You can set a branded suffix domain so every new site automatically carries your name. Your customers can then map their own domains when they’re ready to go live. InstaWP generates SSL certificates for both www and non-www versions, verifies DNS records, and completes the mapping without you touching a single config file.
- Full white-label support. Between the custom suffix domain, branded landing page, logo and color customization, and custom email templates, there is nothing in the customer-facing experience that reveals InstaWP as the underlying platform. Your clients see your brand and only your brand.
The sections that follow break down the exact steps for building your WaaS with custom domain.
Step 1: Create a Template from Your WordPress Site
Everything starts with a template. This is the WordPress site your customers will receive when they sign up through your WaaS. Take your best build, whether it’s a starter theme, a niche-specific design, or a fully loaded site with plugins, content, and settings, and save it as a template on InstaWP. Every customer who signs up will get an exact clone of this site, ready for them to customize.
You can create multiple templates if you want to offer variety. A restaurant template, a portfolio template, a local business template. Each one can be attached to your WaaS later.
To create a template, you need to first create a site on InstaWP with the lements of your choice and then save it as Template.

Must Read: Create Site | InstaWP Docs
Step 2: Set Up Your Payout Method
Before you can charge customers, InstaWP needs to know where to send the money and set-up a payment method.
Head to your account settings and configure your payout details.

Get this done before you build your WaaS so the billing side is ready from the moment you launch.
Must Read: How to Setup Payout Method | InstaWP Docs
Step 3: Create Your WaaS with the Suffix Domain
With the templates saved and payouts configured, you can now create the actual WaaS product. overview of the WaaS creation process:
Navigate to Sell → WaaS in the InstaWP sidebar. Click Add New.

Give your WaaS a name, choose a design layout (side navigation or bottom navigation), select your templates, and pick a default language.

Create your hosting plans. For each plan, set the plan name, choose free or paid, select an InstaWP hosting tier, set your pricing (monthly or yearly), configure template pricing (waived off or add price), and choose the WordPress user role for customers. Click Save & Continue.

Optionally add features to each plan under the Features tab. Customers will see these when comparing plans on your landing page.
Add branding details, your logo, brand colors, custom CSS, and email customization.

Click the Share button to get a shareable link for your customers.

At this point, your WaaS is functional but every site it creates will use an InstaWP-generated URL like clientsite.instawp.xyz.
The key detail here is in when configuring pricing plans, you’ll see a Suffix Domain option. This lets you assign different suffix domains to different plans if you want.

For example, your basic plan might use basic.youragency.com while your premium plan uses pro.youragency.com.
Must Read: Create WaaS | InstaWP Docs
Step 4: Set Up Your Suffix Domain
The suffix domain is the branded domain that all new WaaS sites will automatically use. This is the single most impactful thing you can do for your WaaS branding.
How to Configure It
Log into your InstaWP dashboard. Click on your team name in the top-right corner of the dashboard.

Click the settings icon next to your team name. This opens the team settings page. Scroll down to the White Label section.

Toggle on the Enable White Label option. A Suffix Domain input field will appear. Enter your branded domain (for example, sites.youragency.com). Click the Add button.

The white-label feature is available as a paid add-on. If you’re not already on a paid plan, you’ll see an upgrade prompt at this stage.
After adding the suffix domain in InstaWP, you need to point that domain to InstaWP’s servers. This is done through your domain registrar (such as Cloudflare, Namecheap, GoDaddy, or Google Domains).
You’ll need to create a CNAME record in your DNS settings:
- Type: CNAME
- Name: The subdomain portion (e.g.,
sitesif your suffix domain issites.youragency.com) - Target/Value: The hostname provided by InstaWP (typically something like
your-site-name.instawp.xyz)
Once the DNS propagates, every new site created through your WaaS will automatically use the suffixe domain.
If you’re using Cloudflare, make sure the proxy is disabled (the cloud icon should be grey, not orange) while the DNS is being verified.
Once the DNS propagates, your suffix domain is active. Now go back to your WaaS plan settings: you’ll see a Suffix Domain option in each plan where you can assign this domain. You can even use different suffix domains for different plans, such as basic.youragency.com for your free tier and pro.youragency.com for your premium tier.
Step 5: Test Your WaaS
Before sharing your WaaS with real customers, test the entire flow yourself.
Open your WaaS link in an incognito browser. Fill in some test details and create a site. Instead of seeing testsite.instawp.xyz, you should see something like testsite.sites.youragency.com. Check that the branding looks right, the suffix domain is working, and the SSL certificate is active. If everything checks out, you’re ready to go live.

Click the Share button at the top of your WaaS page to get the shareable link for your customers.

Step 6: Map a Custom Domain to the Customer’s Site
When a customer is ready to go live with their own domain (like www.clientbusiness.com), they can map it directly from their site dashboard. You can also do this on their behalf.
Make sure the WaaS site is fully configured with the details below:
Enter Your Information, Confirm, and Setting up your Site.

Once these details are entered, the site is fully configured. Now, click on Manage Site.

Find and click the Map Domain option.

A modal window will appear. InstaWP will display A Records that need to be added to the customer’s DNS. Copy these records.

Go to the domain registrar where the customer’s domain is registered (e.g., Namecheap, Cloudflare, GoDaddy). Navigate to the DNS settings and create new A records, pasting the values copied from InstaWP.

Save the DNS records in the registrar.
Return to InstaWP and click the Map Domain button. Enter these details here.

The domain mapping will process and the site will be accessible via the custom domain within a few minutes.
Important Notes on A Records vs CNAME Records
Depending on your server integration (RunCloud, ServerAvatar, or InstaWP’s own hosting), the records you need to create may differ:
- A Records point a domain directly to an IP address. These are used when mapping root domains (like
example.com). - CNAME Records point a domain to another domain name. These are typically used for subdomains (like
www.example.comorblog.example.com).
InstaWP will tell you exactly which type of record to create. Just follow the instructions in the modal window.
Step 7: Handle www and Non-www Versions
This is a detail that many people overlook, and it can cause problems if not handled correctly.
InstaWP generates an SSL certificate for the non-www version of the domain automatically. However, if your customer wants both www.example.com and example.com to work, they need to create A records for both versions.
This means there will be four A records in total; two for the non-www version and two for the www version. Make sure all four records are saved in your DNS settings before clicking the Map Domain button in InstaWP.
If only one version is configured, visitors who type the other version into their browser will see an error or a security warning.
Step 8: Manage Cloudflare and Proxy Settings
If you or your customers use Cloudflare for DNS management, there are a few important things to keep in mind.
During Domain Mapping
You need to disable Cloudflare’s proxy (the orange cloud icon) while the domain mapping is being processed. This is because InstaWP needs to verify the DNS records directly, and Cloudflare’s proxy can interfere with that verification.
To disable the proxy: go to your Cloudflare DNS Records page, find the relevant record, click the orange cloud icon to turn it grey, and save.
After Domain Mapping
Once the domain is successfully mapped, you can re-enable the Cloudflare proxy if you want. The proxy provides DDoS protection, SQL injection prevention, and spam filtering.
However, if you’re using the CDN provided by InstaWP, you don’t need Cloudflare’s proxy at all. Using both could cause conflicts.
Step 9: Delete or Change a Mapped Domain
Situations change. A client might rebrand or switch domains. Here’s how to remove a mapped domain.
- Go to the site’s domain management page in InstaWP.
- Click the Delete button next to the domain you want to remove.
- A confirmation window will appear. Click Remove Domain.
The domain is removed immediately. You can then map a new domain by following the same process outlined above.
Best Practices for WaaS Domain Management
- Set up your suffix domain first. Do this before creating any WaaS products. It ensures every site starts with your branding from day one.
- Document the process for your customers. Create a simple guide or video showing your clients how to map their own domains. This reduces support tickets and empowers them to self-serve.
- Use consistent naming. If you’re offering multiple WaaS products, use a logical suffix domain structure (e.g.,
starter.youragency.com,business.youragency.com) so everything stays organized. - Test with a sample domain. Before rolling out your WaaS to real customers, test the entire domain mapping flow with a test domain to make sure everything works smoothly.
- Keep your DNS tidy. Regularly audit your DNS records. Remove old CNAME and A records for sites that no longer exist to avoid confusion and potential security issues.
Conclusion
Building a WaaS on InstaWP gives you a repeatable, scalable way to sell websites without rebuilding everything from scratch for each client. The templates handle the design, the hosting plans handle the infrastructure, and the branded landing page handles the sales experience. But it’s the custom domain that ties all of it together and makes the service feel like yours.
Setting up a suffix domain takes a few minutes and immediately transforms how every new site looks to your customers. Mapping individual client domains when they’re ready to go live is equally straightforward, with InstaWP handling the SSL certificates and DNS verification behind the scenes.
The entire process, from creating your first WaaS product to delivering a fully branded, custom-domain website to a paying client, can be completed in a single afternoon.
If you’ve been thinking about offering websites as a recurring service, start with InstaWP today with $25 free credits after sign-up!
Frequently Asked Questions
Can I map multiple domains to one WaaS site?
Yes. InstaWP supports mapping both a primary domain and alias domains to the same site. The primary domain is the main URL, while alias domains redirect visitors to it.
Do I need to buy domains through InstaWP?
No. InstaWP does not sell domains. You can purchase domains from any registrar — Namecheap, GoDaddy, Cloudflare, Google Domains, or any other provider — and point them to InstaWP using DNS records.
Does InstaWP provide free SSL?
Yes. InstaWP automatically generates SSL certificates for mapped domains, including the non-www version.
Can my customers map their own domains?
Yes, but they need to be on a paid plan. Once they’ve upgraded, the Map Domain option becomes available in their site dashboard.
What happens to the old InstaWP URL after mapping?
The InstaWP-generated URL (e.g., sitename.instawp.xyz) continues to work alongside the mapped domain. Both URLs will reach the same site.
Is this process the same for all domain registrars?
The general process is the same, but the interface for adding DNS records varies between registrars. InstaWP’s documentation has been tested across most major registrars including Namecheap, Cloudflare, and others.