Custom Domain for AI Built App: The 2026 Setup Guide
Add a custom domain to your AI-built app in under 15 minutes. Covers Replit, Base44, Azure, and flat-rate options. No DevOps degree required.

Adding a custom domain for an AI-built app shouldn't require a DevOps degree, but most platforms make it feel that way. I learned this the hard way in 2024 when a client asked me to move their Cursor-built dashboard from a replit.app subdomain to their actual company URL. Three hours, two support tickets, and one DNS propagation nightmare later, I had a working domain and a firm resolve to never repeat the process. Since then, I have shipped over a dozen AI-built apps to production on custom domains, and I have mapped the exact steps, costs, and gotchas across every major platform. Here is everything you need to know to go from an AI prompt to clientname.com in under 15 minutes.
Table of Contents
- Why Your AI-Built App Needs a Custom Domain
- The Real Cost of Custom Domains: Free vs. Metered
- Step-by-Step: Adding a Custom Domain on Major Platforms
- DNS Record Types You Actually Need to Know
- SSL/TLS Certificates: Who Handles Them and Who Charges
- Troubleshooting Common Custom Domain Problems
- Domain Purchase Guidance for AI-Built Apps
- The AI-Specific Domain Considerations Nobody Talks About
- When to Hand Off the Domain to Your Client
- Final Checklist: Before You Go Live
- The Bottom Line
Why Your AI-Built App Needs a Custom Domain
A replit.app or base44.app subdomain screams "prototype" to anyone who looks at the browser bar. Clients notice. Users notice. Investors definitely notice. A custom domain signals that the app is production-ready, not a weekend experiment.

Search engines treat custom domains with more authority than subdomains of free hosts. When you build on someone else's domain, you are building their SEO equity, not yours. If you ever switch platforms, the domain comes with you. The URL stays the same, the backlinks stay intact, and your search rankings survive the migration.
Professional handoff demands a custom domain. Clients expect to see their own brand in the URL, not a random preview link. And if you want to send branded email from hello@yourdomain.com instead of a Gmail address, a custom domain is non-negotiable. Email credibility alone justifies the setup time.
The Real Cost of Custom Domains: Free vs. Metered
What "Free" Actually Means on AI Hosting Platforms
Only four AI website builders offer genuine free plans with custom domain support in 2026: Kleap, Wix, WebWave, and Canva. That is the full list. Every other platform either restricts custom domains to paid tiers or buries the feature behind usage limits that make "free" functionally useless for anything beyond a landing page.
Base44 gives every app a free myapp.base44.app URL, but custom domains require a Builder, Pro, or Elite plan. Azure App Service flat-out refuses custom domains on its Free tier; you need at least the Basic tier. Replit's free subdomains work for testing, but the moment you want a real domain, you are on Autoscale or Reserved VM pricing.

Free tiers that do support custom domains typically cap bandwidth, storage, or page counts. Fine for a static portfolio site. Risky for a data-driven app that might actually get traffic.
Metered vs. Flat-Rate Pricing: The Surprise Bill Trap
Here is where things get expensive. Replit Autoscale and Reserved VM plans charge by compute usage. A traffic spike on your custom domain, maybe from a Product Hunt launch or a client demo that goes viral, can double your monthly bill overnight. You will not know until the invoice arrives.
Azure App Service Basic tier starts around $55 per month and then charges extra for bandwidth overages and SSL certificate management features. The base price is not the real price.
Flat-rate hosting eliminates this problem entirely. You pay one price regardless of traffic, database queries, or function invocations. Shiply's $0, $8, and $24 per month plans include custom domains with no usage meter. Before committing to any platform, run the numbers through a hosting bill calculator to compare flat versus metered costs. The difference over a year is often hundreds of dollars.
Step-by-Step: Adding a Custom Domain on Major Platforms
Base44 (The 350-Domain Option)
Base44 starts every app with a free myapp.base44.app URL. To add a custom domain, you need a paid plan. Once upgraded, the platform supports linking up to 350 domains to a single app, which is overkill for most solo builders but useful if you are running a multi-tenant SaaS or white-label setup.
DNS changes for external domains can take up to 72 hours to propagate. That is three full days. Plan your launch accordingly and do not schedule the domain switch for a Friday afternoon. SSL certificates provision automatically once the domain is verified. Removing a domain later requires finding the "Unlink Domain" or "Delete" icon, which is not immediately obvious in the UI. It is there, just buried.
Replit (The Automatic Setup Option)
Replit provides free subdomains in the <subdomain>.replit.app format. Custom domains work with Autoscale, Reserved VM, and Static deployment types. The standout feature is automatic DNS setup: you sign into your domain provider through Replit, and it configures the DNS records for you. No manual A record hunting. No copying IP addresses.
DNS propagation can take up to 48 hours. If you use Cloudflare's proxied mode, the orange cloud icon, Replit explicitly warns that multiple A and AAAA records may conflict. Disable proxying during setup and re-enable it after propagation completes. Also, www is treated as a separate subdomain. You must configure it independently from the apex domain, or visitors typing www.yourdomain.com will hit a dead end. TXT verification records are required before Replit issues an SSL certificate.
Azure (The Enterprise Option That Costs You)
Azure App Service does not support custom domains on the Free tier. Period. You upgrade to Basic or you move on. Azure Static Web Apps is more generous, supporting custom domains with free SSL certificates automatically generated for both the default and custom domains.
CNAME records are the standard DNS requirement. Azure's documentation is thorough but dense. Expect to spend 30 to 60 minutes on your first setup, mostly reading through pages of configuration options that do not apply to your use case. There is no automatic DNS configuration. You will manually add records at your domain registrar, then wait for Azure to verify them.
Shiply (The One-Call Option for AI Agents)
Shiply is built specifically as the production backend for anything an AI agent builds. You deploy from Claude, Cursor, or ChatGPT with a single API call, and the platform provisions a live URL with a per-site database, edge functions, email, and a custom domain. No separate services to stitch together.
Custom domains use auto-DNS via Cloudflare. You point your nameservers to Cloudflare once, and DNS records configure themselves. SSL certificates are automatic and renewable with no manual renewal reminders. The atomic site ownership transfer feature, powered by Stripe Connect, lets you hand off the domain and hosting to a client in a single transaction. No DNS handoff. No shared passwords. The client pays you, and the site becomes theirs.
Flat-rate pricing at $0, $8, or $24 per month means adding a custom domain does not trigger metered costs. The price stays the same whether your app gets ten visits or ten thousand. For the full setup walkthrough, the custom domains documentation covers every step.
DNS Record Types You Actually Need to Know
A records point your apex domain, example.com, to the platform's IP address. Replit and some static hosts require these. CNAME records point subdomains, like www.example.com, or the apex via CNAME flattening, to the platform's default domain. Azure and most modern hosts prefer CNAME records because they survive IP address changes on the host side.
TXT records handle domain ownership verification. Every platform requires a specific TXT value before it will issue an SSL certificate. Copy and paste this value directly from the platform's dashboard. A single typo breaks the verification chain.
NS records come into play when using auto-DNS services like Cloudflare. You point your nameservers to the platform's DNS servers, and they handle the rest. Shiply's Cloudflare integration uses this approach.
The most common mistake is forgetting to configure www as a separate subdomain. Visitors who type www.yourdomain.com will hit a dead end if you only configured the apex. Set up both, or redirect one to the other.
SSL/TLS Certificates: Who Handles Them and Who Charges
Base44, Replit, and Azure Static Web Apps all provide automatic SSL provisioning and renewal for custom domains at no extra cost. The certificates just appear. Azure App Service Basic tier includes SSL but charges for additional certificate management features beyond the basics.
Manual SSL setup, uploading your own certificate, is possible on most platforms but adds complexity and renewal risk. You will forget to renew it. The certificate will expire. Your app will show a security warning. Let that sink in.
Let's Encrypt powers most auto-SSL setups. Certificates renew every 90 days, and platforms handle this transparently. If your platform does not auto-provision SSL, you will need Cloudflare's Universal SSL, which is free, or a paid certificate. Factor this cost into your platform comparison. A $10 per month host that charges $50 per year for SSL is not cheaper than a $15 per month host that includes it.
Troubleshooting Common Custom Domain Problems
DNS Propagation Delays
Base44 can take up to 72 hours. Replit up to 48 hours. Azure typically resolves in one to two hours with proper configuration. Check propagation status using tools like whatsmydns.net or dnschecker.org. They show you which global DNS servers have picked up your changes.
TTL, Time to Live, settings affect propagation speed. Lower TTL to 300 seconds before making DNS changes, then raise it after propagation completes. If you forgot to lower TTL before the change, you are waiting for the old TTL to expire. That can take hours.
Certificate Errors
A "Your connection is not private" error usually means SSL has not finished provisioning. Wait 15 to 30 minutes and refresh. If you are using Cloudflare's proxied mode, the orange cloud, disable it during setup. Replit explicitly warns that proxied domains cause conflicts. Mixed content warnings appear when your app loads resources over HTTP while the domain uses HTTPS. Browsers block those resources. Use relative URLs or update all resource links to HTTPS before going live.
Domain Verification Timeouts
TXT record verification fails most often because of a typo in the value. Copy and paste directly from the platform's dashboard. Do not retype it. Some registrars take longer to propagate TXT records than A or CNAME records. Verify with a DNS lookup tool before contacting support. If verification keeps failing, remove the domain from the platform, delete all DNS records, wait 30 minutes, and start fresh. This nuclear option works more often than it should.
Domain Purchase Guidance for AI-Built Apps
Choosing the Right TLD
.com remains the gold standard for credibility and user trust. Everyone types .com by default. .ai domains signal AI-native apps but cost two to five times more and renew at unpredictable rates. The .ai TLD is managed by the government of Anguilla, and prices shift without notice.
.app domains require HTTPS by default, which is good for security but redundant on platforms that already enforce HTTPS. .dev domains also enforce HTTPS and are popular among developer tools and API products. Avoid obscure TLDs like .xyz, .top, or .click for client-facing apps. They trigger spam filters and reduce trust. No client wants to explain to their customers why their business lives on a .buzz domain.
Best Registrars for AI Projects
Cloudflare Registrar sells domains at cost with no markup, includes free DNS and DDoS protection, and integrates cleanly with any platform that supports Cloudflare auto-DNS. Namecheap offers competitive pricing, a good UI, and supports auto-DNS integrations with Replit and Base44. Porkbun is the cheapest option for .ai domains and has a simple interface with CNAME flattening support. GoDaddy is widely known but charges more and pushes upsells aggressively. Only use GoDaddy if the client already has an account there and insists on staying.
The AI-Specific Domain Considerations Nobody Talks About
Some AI platforms, including Google AI Studio, restrict custom domains by region. Your app may work perfectly in the US but fail in the EU with the same domain. Test from multiple geographic locations before launch.
AI chatbots with custom domain knowledge integration require the domain to be configured before training data ingestion. Changing the domain later can break knowledge base links, and retraining is not always straightforward. Lock in the domain early.
If your AI app serves users globally, ensure your platform supports multi-region DNS routing. Cloudflare's global load balancing handles this, but not every hosting platform integrates with it.
.ai domain transfers are slower than .com transfers. The Anguilla registry processes changes on their timeline, not yours. If you plan to transfer a .ai domain, budget extra days.
When to Hand Off the Domain to Your Client
Atomic site ownership transfer, available on Shiply via Stripe Connect, moves the domain and hosting to the client in a single transaction. No DNS handoff. No shared passwords. The client pays, and the site becomes theirs. This is the cleanest way to close a project and get paid.
Traditional handoff is messier. Export DNS records, transfer domain registration to the client's registrar account, then delete your access. Never hand over your platform login credentials. Create a separate client account or use a transfer feature. Include a handoff document with DNS record screenshots, SSL renewal dates, and platform support contact information. Set expectations clearly: after handoff, the client owns the domain and any ongoing hosting costs. Your responsibility ends at transfer.
Final Checklist: Before You Go Live
Domain purchased and registered under your or your client's name. DNS records added at the registrar, whether A, CNAME, or NS depending on the platform. Domain verified on the hosting platform with TXT record check passed. SSL certificate provisioned and showing a green lock in the browser. www subdomain configured to redirect or resolve to the same app. Email routing set up if applicable for custom domain email. App tested on the custom domain with all pages, forms, and API calls working. Propagation checked via whatsmydns.net across multiple global locations. Client, if applicable, has login access or domain ownership transferred.
The Bottom Line
Custom domains separate hobby projects from production apps. Clients and users notice the difference immediately. Free custom domain support is rare. Most platforms require a paid tier, and some add metered costs that spike unpredictably with traffic. Flat-rate hosting eliminates the surprise bill problem: you pay one price regardless of traffic, database queries, or function invocations.
AI agents like Claude, Cursor, and ChatGPT can deploy directly to production with a single call. On platforms that support auto-DNS, no manual DNS configuration is needed. Shiply offers flat-rate hosting with auto-DNS via Cloudflare, real databases, edge functions, and atomic ownership transfer, built for the solo builder who wants to ship fast and get paid without worrying about a usage meter ticking in the background.