How to Deploy Your AI-Built App to a Custom Domain

TL;DR

Deploying your AI-built app to a custom domain takes 15–30 minutes once your app is working. Buy the domain ($10–$15), connect it in your vibe coding platform's settings, add the required DNS records at your registrar, wait for DNS propagation (5–60 minutes), and verify SSL is active. Greta, Lovable, Bolt, and v0 all support custom domains on paid plans — the steps are nearly identical across platforms.

Introduction

Your app works. You can share the URL with friends. But it ends in .lovable.app, .bolt.host, or some other platform subdomain — and that's killing the credibility you need to charge real money. Custom domains are the difference between "demo I made over the weekend" and "real product." They cost about $10 a year and take less than an hour to set up.

This guide walks through deploying your AI-built app to a custom domain on every major vibe coding platform. You'll get the exact steps for Greta, Lovable, Bolt, v0, Emergent, and Replit — plus the DNS gotchas that trip up most first-timers. By the end, your app will be live on yourdomain.com with SSL working and ready to charge customers.

Got an idea? Build it now!
Just start with a simple Prompt

Get Started Today

Why does deploying to a custom domain matter so much?

Custom domains affect three things: credibility, conversion, and SEO. A platform subdomain (yourapp.lovable.app) signals "side project that hasn't found product-market fit." Your own domain signals a real business. Users behave differently based on this signal — they're more likely to sign up, pay, and stick around.

The conversion difference is measurable. Studies show subdomain pages convert at significantly lower rates than equivalent custom-domain pages, even with identical copy and design. The signal cost is real, even when the product is the same.

SEO is the other half. Search engines index custom domains far more aggressively than platform subdomains, and shared subdomain reputation rarely benefits new apps. If you want any organic traffic over time, a custom domain is table stakes.

What you need before deploying to a custom domain

Three things are required before the deployment step itself: a working app on your vibe coding platform, a paid plan that supports custom domains, and a domain you've purchased.

Most platforms gate custom domains on paid tiers

Custom domains are usually a paid feature. Free tiers across Greta, Lovable, Bolt, v0, and Vercel exclude custom domains — you'll need at least the entry-level paid plan ($20–$50/month) to connect one. Worth knowing before you spend an hour debugging why it isn't working.

Where to buy your domain

For most builders, Cloudflare Registrar and Namecheap are the best options — both offer transparent pricing without renewal-spike tactics. Avoid GoDaddy unless you have a specific reason; their renewal pricing and upsells make total cost higher than competitors. Expect to pay $10–$15 for a .com and slightly more for premium TLDs like .app or .io.

Pick the right domain for your build

Short is better than clever. A 6–10 character .com beats a long .io. If your first-choice domain is taken at any reasonable price, pick a different name rather than going with .co, .app, or .xyz — modern users still treat .com as the default and trust it more.

How to deploy your AI-built app to a custom domain — step by step

The process is nearly identical across vibe coding platforms. Here's the universal sequence, with platform-specific notes where they differ.

Step 1: Verify your app is production-ready

Before pointing a domain at it, make sure the app actually works on the platform's default URL. Test the core flow, sign up as a new user, run a Stripe test transaction if applicable. Fixing bugs is easier on the platform subdomain than after DNS is involved.

Step 2: Buy your domain

Sign up with Cloudflare Registrar or Namecheap, search for your domain, complete the purchase. Skip add-ons like email forwarding, privacy protection upsells (Cloudflare includes WHOIS privacy free), and "SSL certificates" (your vibe coding platform provides these automatically).

Step 3: Open your vibe coding platform's domain settings

Each platform places this slightly differently:

• Greta — Project settings → Custom domain
• Lovable — Project settings → Domains (Pro plan required)
• Bolt.new — Project → Deploy → Domains
• v0 by Vercel — Project → Deployments → Domains (uses Vercel's domain system)
• Emergent — Project settings → Custom domain (Standard plan)
• Replit — Deployment → Custom domain

In each case, enter your domain (e.g., yourapp.com) and click connect. The platform will then give you DNS records to add at your registrar.

Step 4: Add DNS records at your registrar

The platform will show you 2–4 DNS records to add. Most commonly:

• An A record pointing to the platform's IP address (for the apex domain yourapp.com)
• A CNAME record pointing to the platform's domain (for www.yourapp.com)
• Occasionally a TXT record for domain verification

Go to your registrar's DNS management panel and add each record exactly as shown. Tiny mistakes (extra spaces, wrong record type, www vs apex confusion) are the most common cause of deployment failures.

Step 5: Wait for DNS propagation

DNS changes take time to spread across the internet. Most propagate in 5–15 minutes; some can take up to 48 hours, especially with older TTL settings. On Cloudflare DNS, propagation is usually under 5 minutes. Use a tool like dnschecker.org to verify your records have propagated to multiple regions before moving on.

Step 6: Confirm SSL is active

Modern vibe coding platforms auto-provision SSL certificates via Let's Encrypt once DNS resolves correctly. You should see https:// working with a green lock icon within 5–30 minutes of DNS propagation. If SSL doesn't activate within an hour, double-check the DNS records and the platform's domain settings.

Step 7: Test the live app end-to-end

Once the custom domain works, retest the entire flow: sign up, log in, complete the core feature, run a Stripe payment (still in test mode if you haven't switched to live), confirm transactional emails arrive. Some flows that work on platform subdomains break on custom domains because of CORS or session cookie configuration.

Got an idea? Build it now!
Just start with a simple Prompt

Get Started Today

Platform-specific notes worth knowing

Greta

Custom domains are bundled into Greta's paid plans alongside SEO and analytics tooling. The setup is one of the cleanest in the category — most builders finish the entire flow in 10–15 minutes. We cover Greta's bundled approach in detail in Greta vs Lovable.

Lovable

Lovable requires the Pro plan for custom domains. The platform provides clear DNS records and provisions SSL automatically. Once connected, Lovable apps run on the same React + Tailwind + Supabase stack regardless of domain.

Bolt.new

Bolt deploys to .bolt.host by default, with custom domains supported on paid plans. Bolt also integrates tightly with Netlify, so you can deploy to Netlify directly and connect the domain there if you want more control over edge functions or redirects.

v0 by Vercel

v0 inherits Vercel's deployment infrastructure, which is the most production-grade in the category. Custom domains, SSL, edge caching, and preview deployments all work seamlessly because v0 is built by the team behind Next.js. If your domain is already at Vercel, the setup is essentially one click.

Emergent

Custom domains are available on Emergent's Standard plan and above. The multi-agent build approach means the deployment configuration is generated specifically for your app's architecture.

Replit

Replit's deployments support custom domains across multiple deployment types (autoscale, reserved VM, static). The setup is slightly more technical than the consumer-focused platforms but offers more control over scaling.

Common deployment problems and how to fix them

Most custom domain deployments work on the first try. When they don't, the issue is almost always one of five things.

• DNS records typed wrong — Most common cause. Triple-check spelling, record type (A vs CNAME), and that the value matches exactly what the platform provided. Extra spaces or wrong record types are silent killers.
• DNS propagation incomplete — Wait at least 60 minutes before assuming something is wrong. Some regions take longer than others. Check propagation with dnschecker.org.
• SSL not provisioning — Usually because DNS isn't fully propagated yet, or the platform's verification is still pending. Wait 30 minutes, then try removing and re-adding the domain in platform settings.
• Old DNS cached on your computer — Even after DNS propagates, your browser may cache the old resolution. Open an incognito window, or flush the DNS cache to force a fresh lookup.
• App breaks on custom domain but works on subdomain — Usually a CORS or session cookie config issue. Confirm that allowed origins include your new domain and that cookies are configured for your domain rather than the platform's.

If none of these resolve it, contact your platform's support before assuming the issue is at the registrar. Custom domain setup is one of the most common support tickets, and platforms usually resolve it in under an hour.

What to do after the domain is live

The custom domain is the start, not the finish line. A few things to set up immediately after.

• Switch Stripe (or your payment provider) to live mode — A surprising number of vibe-coded apps ship to a custom domain with payments still in test mode. Switch before you share the URL.
• Add basic analytics — PostHog, Plausible, or GA4. You can't iterate on what you can't see, and analytics tags often need to be updated when the domain changes.
• Set up email at your domain — Even a simple hello@yourapp.com forwarder signals legitimacy. Cloudflare and Namecheap both include free email forwarding.
• Configure SEO basics — Title tags, meta descriptions, Open Graph image, sitemap. For UI prompts that produce strong landing pages, our guide on AI Prompts for Generating Beautiful UI Designs covers the layered approach.
• Submit to Google Search Console — Verifies your domain ownership and starts the indexing process. Free, takes 5 minutes.
• Test real-time features on the new domain — Some real-time setups have CORS configurations that break when the domain changes.
• Update any external links — If you've shared the old subdomain anywhere (Product Hunt, Twitter, your portfolio), update those links.

When custom domains aren't enough

Custom domains solve the credibility problem, but they don't solve every production concern. If your app is taking real customer revenue, a few additional considerations apply.

• Production-grade hosting infrastructure — Most vibe coding platforms handle hundreds of users comfortably. Beyond that, you may need engineering review to harden hot paths, add caching, and scale the database.
• Backups and disaster recovery — Don't assume the platform backs up your database. Verify, and add your own backup process if not.
• Monitoring and alerting — Set up Sentry or a similar error tracker before launch, not after the first production bug.
• Custom email infrastructure — For transactional emails at scale (10k+ per month), platforms like Resend, Postmark, or Loops are worth the setup time.

For mobile-specific deployment considerations (App Store and Play Store), see our guide on how to Build a Mobile App From a Single Prompt.

Common Mistakes to Avoid

• Buying the domain on a free tier — Free plans on most platforms don't support custom domains. Upgrade before you buy.
• Mistyping DNS records — Triple-check before submitting. Extra spaces, wrong record types, and apex vs www confusion are the most common deployment failures.
• Assuming SSL is instant — Allow up to an hour for SSL to provision after DNS propagates. If it's still failing after that, remove and re-add the domain in platform settings.
• Skipping the post-deployment retest — Some features that work on platform subdomains break on custom domains. Always retest the full flow after the cutover.
• Forgetting to switch Stripe to live mode — A surprisingly common oversight. Test mode payments don't actually charge anyone, including you.
• Pointing the domain before the app is ready — Connect the domain after the app works on the platform subdomain. Debugging app issues and DNS issues at the same time is painful.
• Using shady domain registrars — Stick with Cloudflare or Namecheap. The "$0.99 first year" registrars usually have $50+ renewals or hidden DNS limitations.

Frequently Asked Questions

1. How long does it take to deploy an AI-built app to a custom domain?

The hands-on work takes 15–30 minutes — buy the domain, connect it in platform settings, add DNS records. The waiting (DNS propagation, SSL provisioning) adds another 15–60 minutes. Most builders are fully live within an hour of starting.

2. Do I need a paid plan to connect a custom domain?

Yes — Greta, Lovable, Bolt, v0, Emergent, and Replit all gate custom domains behind paid plans (typically $20–$50/month). The free tiers exclude this feature.

3. Which domain registrar should I use for an AI-built app?

For most builders, Cloudflare Registrar and Namecheap are the best options. Both offer transparent pricing without renewal-spike tactics. Avoid GoDaddy unless you have a specific reason.

4. Do I need to set up SSL myself?

No — modern vibe coding platforms auto-provision SSL certificates via Let's Encrypt once DNS resolves correctly. SSL typically activates within 5–30 minutes of DNS propagation. You don't need to buy or configure SSL certificates separately.

5. What happens if my DNS records are wrong?

The domain won't connect, but nothing breaks permanently. Remove the incorrect records, add the right ones, and wait for propagation again. DNS mistakes are recoverable in minutes.

6. Can I move my app to a different platform later if I keep the same domain?

Yes — your domain is fully portable. To switch platforms, update the DNS records at your registrar to point at the new platform's IP or CNAME. The domain stays the same; only the records change.

7. Will my app's SEO transfer when I switch from a subdomain to a custom domain?

Mostly, but expect a temporary dip. The new domain starts with no search history, so it takes 2–4 weeks for Google to fully reindex. Set up Google Search Console, submit a sitemap, and add 301 redirects from the old subdomain if your platform supports them.

Got an idea? Build it now!
Just start with a simple Prompt

Get Started Today

Conclusion

• Deploying an AI-built app to a custom domain takes 15–30 minutes of hands-on work plus another 15–60 minutes of waiting for DNS and SSL. Total: under an hour.
• The universal sequence — buy domain, open platform settings, add DNS records, wait for propagation, verify SSL, test — works across every major vibe coding platform with minor variations.
• Custom domains affect credibility, conversion, and SEO meaningfully. Subdomain pages convert at significantly lower rates than equivalent custom-domain pages. The signal cost is real.
• Most deployment failures are caused by five common issues: typo'd DNS records, incomplete propagation, SSL provisioning lag, browser cache, and CORS configuration. All are quickly recoverable.

Buy the domain tonight, connect it in your platform's settings, and have your app live on yourdomain.com by tomorrow morning. The difference between yourapp.bolt.host and yourapp.com is small in effort and large in everything that actually matters — credibility, conversion, and how real your product feels to the people you're trying to charge.