Skip to main content
AIWA lets you connect your own custom domain to a published project. Instead of sharing an AIWA-provided project URL, you can launch your website or application at an address such as:
or:
AIWA continues hosting your application while your custom domain becomes the address your users see. Build with AIWA. Publish with AIWA. Launch on your own domain.
Custom domains are available on eligible AIWA plans, starting with Solo.

​
What Is a Custom Domain?

When you first publish a project, AIWA provides a live URL you can use to access and share it. A custom domain lets you replace that public-facing address with a domain you own. For example:
Your application remains hosted by AIWA. The domain simply provides your branded address.

​
Before You Start

You’ll need:
  • A published AIWA project
  • A domain you own
  • Access to the domain’s DNS settings
  • An AIWA plan that supports custom domains
Your domain may be registered with providers such as Cloudflare, GoDaddy, Namecheap, or another domain registrar/DNS provider. You don’t need to transfer ownership of the domain to AIWA. You only need to configure the required DNS records.

​
Root Domains and Subdomains

You can connect a root domain or use a subdomain depending on how you want your application to be accessed. Root domain
This is useful when the AIWA project is your primary website. For example:
Subdomain
This is useful when your main website already exists somewhere else. For example:
could remain your marketing website, while:
points to your AIWA application. Other examples include:
Choose the structure that fits your product.

​
Connect a Custom Domain

First, publish your AIWA project. Then open the publishing/domain settings for the project and choose the option to connect a custom domain. Aiwa Custom Domain Enter the domain or subdomain you want to use. For example:
AIWA will provide the DNS information required to connect your domain.

​
Configure Your DNS

Your domain’s DNS tells browsers where your application is hosted. After entering your domain in AIWA, you’ll be given the DNS record or records required for the connection. Aiwa Dns Records Open the DNS management area at the provider managing your domain. Add the records exactly as AIWA provides them.
Always use the DNS values displayed by AIWA for your project. Don’t copy DNS values from another AIWA project or from an example in this documentation.

​
Understanding DNS Records

Depending on the domain configuration, you may encounter records such as:
or:
A CNAME commonly maps a hostname such as:
to another hostname. An A record maps a hostname to an IP address. You don’t need to understand the networking behind these records to connect your domain. The important part is to copy the exact values AIWA provides into your DNS provider.

​
Example: Connecting a Subdomain

Suppose your company owns:
Your existing marketing website is already running at:
You build a customer portal with AIWA and want it available at:
Inside AIWA, add:
as your custom domain. AIWA provides the required DNS configuration. You then add that configuration to the DNS settings for acme.com. Conceptually:
Your existing website doesn’t need to move.

​
Example: Business Website

Suppose you build a construction company website with AIWA. You own:
You can connect that domain to the AIWA project so customers visit:
instead of the original project URL. The final experience becomes:

​
Example: SaaS Application

For a SaaS business, you might separate the marketing website from the application. For example:
Marketing website and:
Web application The application subdomain can point to the project you’ve built with AIWA.

​
Verify Your Domain

After adding the required DNS records, return to AIWA. AIWA needs to detect the DNS configuration before the domain can become active. Aiwa Custom Domain Status Depending on your DNS provider, changes may not appear immediately. DNS updates can require some time to propagate. During this period, AIWA may still show the domain as pending or unverified.

​
DNS Propagation

When you change DNS records, the update has to propagate across DNS infrastructure. This means your domain may not start working instantly. You might see:
If you just added the records, allow time before assuming something is broken.

​
Don’t Repeatedly Change DNS Records

If you’ve entered the exact records AIWA requested, avoid repeatedly deleting and recreating them while waiting for propagation. Doing so can make troubleshooting more difficult. Instead:
  • Confirm the record is correct.
  • Confirm you’re editing the correct domain.
  • Wait for DNS propagation.
  • Check the domain status again.

​
Existing DNS Records

Be careful when your domain is already being used for other services. Your DNS may contain records for:
  • Your existing website
  • Email
  • Verification services
  • Other applications
  • Subdomains
Don’t delete unrelated records just because you’re connecting an AIWA project.
Removing or replacing the wrong DNS records can interrupt your website, email, or other services using the domain.
If you’re unsure, add only the records AIWA specifically requires.

​
Connecting a Client’s Domain

If you’re an agency, you can also connect a client’s domain to the project you’ve built for them. For example:
You’ll need access to the client’s DNS configuration or assistance from whoever manages their domain. A simple agency workflow is:

​
Multiple Client Projects

If you’re managing multiple projects, each client can use their own domain. For example:
The domain is associated with the appropriate published project. Your plan limits and available domain features depend on your AIWA plan.

​
Custom Domains and Hosting

Connecting a custom domain doesn’t mean you’re moving the application to another hosting provider. The architecture remains:
AIWA continues hosting the published project. This is different from exporting the application and deploying it to your own VPS.

​
Custom Domain vs Self-Hosting

These are two different options. Custom domain + AIWA hosting
AIWA manages the hosting. Self-hosting
You manage the hosting. If your only goal is to use your own branded domain, you don’t need to self-host.

​
Updating Your Project

Once a custom domain is connected, you can continue improving your application. For example:
You make changes:
Then the updated version becomes available through the same custom domain. You don’t need to reconnect the domain every time you publish an update.

​
SSL and HTTPS

Your production application should be accessed securely over HTTPS. Once your domain is correctly connected and activated, AIWA’s hosting infrastructure handles the secure connection for the published application. Users should be able to access your project through an address such as:
Domain verification and secure certificate activation may require the DNS configuration to be fully propagated first.

​
Using www

You may want visitors to access:
instead of, or alongside:
Configure the domain arrangement supported by AIWA and your DNS provider. You may also want one version to redirect to the other so users have one consistent canonical address. For example:
or the reverse.

​
Common Problems

​
Domain stays pending

If the domain remains pending, check:
  • The DNS records match AIWA exactly
  • You’re editing the correct domain
  • The hostname is correct
  • No characters were accidentally added
  • DNS has had enough time to propagate

​
Domain verification fails

Compare the record AIWA requested with the record currently configured at your DNS provider. Pay particular attention to:
  • Type
  • Name / Host
  • Value / Target
A small difference can prevent verification.

​
My domain still shows my old website

Your DNS may still point to the previous hosting provider, or the updated record may not have propagated yet. Check the records for the specific hostname you’re trying to connect.

​
Subdomain doesn’t work

For example:
doesn’t work while:
does. These are different hostnames and may require different DNS configuration. Make sure you’ve configured the exact subdomain entered in AIWA.

​
Domain works without www but not with www

example.com and www.example.com are separate hostnames from a DNS perspective. Check whether both have been configured according to your intended setup.

​
I changed DNS but nothing happened

DNS updates aren’t always immediate. First verify that the record matches the values AIWA provided, then allow time for propagation.

​
My email stopped working

If this happened immediately after changing DNS, you may have accidentally modified records used for email. Don’t remove records such as mail-related MX records unless you specifically intend to change your email provider. Restore the appropriate email DNS configuration through your provider if necessary.

​
Debugging a Custom Domain

A useful support or Debug Mode report looks like:
Domain: app.example.com AIWA Status: Pending Verification DNS Provider: [Provider] Record Type: CNAME Host: app Expected Target: [VALUE SHOWN BY AIWA] Current Target: [VALUE IN DNS] The AIWA live URL works correctly, but the custom domain doesn’t. Help me identify the domain configuration issue.
DNS records are generally intended to be public, but don’t include passwords, API keys, registrar login details, or other account credentials when asking for help.

​
Test After Connecting Your Domain

Once AIWA shows the domain as active, open it and test the application. Check:
  • Homepage loads
  • HTTPS works
  • Navigation works
  • Authentication works
  • Forms work
  • Images load
  • API functionality works
  • Integrations work
  • Mobile layout works
  • Redirects behave correctly
  • www/root domain behavior is correct
Don’t stop testing simply because the domain resolves.

​
A Good Domain Setup Workflow

The complete process is:
Once connected, the domain becomes the branded gateway to your AIWA application.

​
Your Project. Your Brand.

AIWA handles the application and hosting. Your users see your brand.
This makes custom domains particularly useful for businesses, SaaS products, agencies, client projects, and production applications.

​
Next: Version History & Restore

Next, we’ll cover Version History & Restore. This is important because building software is iterative, and sometimes a change doesn’t work the way you expected. We’ll cover:
  • What versions are
  • How AIWA tracks project changes
  • Viewing previous versions
  • Restoring an earlier version
  • When you should restore vs ask AIWA to fix something
  • Protecting working functionality while iterating

Version History & Restore

View project versions and restore a previous version when needed.