Custom Domains 101: How to Connect Your Brand to a Greta App

TL;DR: Connecting a custom domain to your Greta app is the single biggest credibility upgrade for a launched product. The work takes 30--60 minutes of clicking and waiting; the impact lasts forever. This guide covers domain registration, DNS basics (A records, CNAME, TXT, MX), the exact steps to point your domain at a Greta app, SSL certificate auto-issuance via Let's Encrypt, propagation timelines and troubleshooting, www vs apex domain decisions, branded email setup, and the post-domain checklist (OAuth callbacks, Stripe webhooks, social bios). By the end, your brand has the domain it deserves and your app looks like a real product.

Introduction

Your app at yoursite.greta.sh works fine. It loads, users can sign up, payments work, the experience is solid. But it doesn't feel like a real product. A custom domain is the single biggest credibility upgrade for a launched app. The same app at yourbrand.com feels professional. Users trust it. Press takes it seriously. Customers share it without embarrassment. The technical work is straightforward --- most builders finish it in 30--60 minutes --- but the impact compounds forever.

This guide covers everything a non-developer founder needs to know about custom domains. Registration, DNS, SSL, the exact connection steps for a Greta app, propagation timelines, common errors, www vs apex decisions, branded email setup, and the post-domain checklist that keeps your stack working after the switch.

Why custom domains matter (beyond vanity)

• Trust --- Users instinctively trust 'yourbrand.com' more than 'yourbrand.platform.com'
• SEO --- Search engines treat custom domains as the canonical version of your brand; better for ranking
• Email --- Branded email (you@yourbrand.com) signals real business; freelancers and customers respect it
• Portability --- Your domain is yours. If you ever migrate platforms, your URL doesn't change. Lock-in shrinks dramatically.
• Brand consistency --- Marketing materials, social bios, business cards all point to the same place
• Investor/partner credibility --- A serious business has a real domain. The signal is small but consistent.
• User retention --- Saved bookmarks, email signatures, social shares all point to your brand permanently

Custom domains are also a trust signal for launch moments. Whether you're shipping a soft launch, a Product Hunt push, or a niche community share, a custom domain reads as serious from the first impression.

Step 1: Buy the domain

Where to register

• Namecheap --- Long-time favorite. Reasonable pricing, decent UI, no aggressive upsell.
• Cloudflare Registrar --- Sells domains at wholesale (no markup). Requires using Cloudflare DNS (also free). Best total value.
• Porkbun --- Newer registrar with clean UI, fair pricing, and good support.
• Google Domains (now Squarespace Domains) --- Acquired by Squarespace. Still functional; UX changed.
• GoDaddy --- Avoid for new purchases. Aggressive upsells, mediocre support, higher prices.

.com TLD is always preferred for serious brands. Other TLDs (.io, .app, .ai) are reasonable for tech products but .com remains the default trust signal.

What to budget

• .com --- Typically $10--$15/year.
• .io --- $30--$60/year. Higher due to small country code economics.
• .app --- $15--$25/year. Decent tech-friendly TLD.
• .ai --- $70--$100/year. AI-themed; pricing is high but persistent.

Domain selection guidance

• Match your product name exactly when possible
• Avoid hyphens --- yourapp-name.com reads as less trustworthy than yourappname.com
• Keep it short --- 6--12 characters is the sweet spot
• Avoid easily misspelled words
• Check social handles are available too --- Don't pick a .com if @yourbrand on Twitter/X belongs to someone unrelated
• Skip the TLD novelty --- .ninja, .rocks, .lol are fun but reduce trust outside very specific niches

Step 2: Understand DNS basics

DNS (Domain Name System) maps domain names to servers. Three records matter for connecting a domain to a Greta app.

Record types you'll use

How DNS actually resolves

1. User types 'yourbrand.com' in browser
2. Browser asks DNS resolver (usually their ISP or 1.1.1.1, 8.8.8.8) for the IP address
3. Resolver queries the authoritative DNS servers for yourbrand.com
4. Authoritative DNS responds with the A record (the IP address)
5. Browser connects to that IP address, the server responds with your app
6. DNS resolvers cache results for the TTL (Time To Live) specified on the record

Step 3: Connect the domain to your Greta app

In Greta (or comparable AI app builder)

• Navigate to project settings → Custom Domain (or Deployment / Hosting settings)
• Click 'Add Custom Domain' or similar
• Enter your domain (yourbrand.com or app.yourbrand.com)
• The platform displays the DNS records you need to add at your registrar --- typically an A record (for apex) or CNAME record (for subdomain)
• Copy the values

In your DNS provider (registrar or Cloudflare)

• Log into your domain registrar's DNS dashboard
• Find the DNS records section
• Add the record(s) the platform specified --- Type (A or CNAME), Name (often '@' for apex or 'app' for subdomain), Value (the IP or domain the platform gave you), TTL (default 1 hour is fine)
• Save

Verification

• The platform typically auto-detects the DNS record within a few minutes
• Once detected, the platform issues an SSL certificate via Let's Encrypt (automatic, free)
• After SSL issuance (1--10 minutes typically), your domain is live with HTTPS
• Test by visiting https://yourdomain.com in a browser

Step 4: SSL certificates (the green padlock)

Modern browsers require HTTPS for trust signals. Every custom domain should have SSL.

How it works on modern platforms

• Platforms like Greta automatically issue SSL certificates via Let's Encrypt --- free, automated, trusted by all browsers
• Certificates auto-renew every 60--90 days; no manual intervention needed
• Your job: add the DNS record correctly. Platform handles everything else.
• If the certificate doesn't issue, the issue is typically DNS --- a misconfigured record or stale propagation

Common SSL issues

• DNS hasn't propagated yet --- Wait an hour and retry
• CAA record blocking Let's Encrypt --- Some registrars set CAA records; verify Let's Encrypt is allowed
• Mixed content warnings --- Your app loads HTTPS but includes HTTP resources. Fix by updating any hardcoded HTTP URLs.

Step 5: www vs apex domain decision

Should users reach your app at yourbrand.com (apex) or www.yourbrand.com (www subdomain)? Both work; pick one as canonical.

Apex (yourbrand.com) as canonical

• Modern preference for marketing-led brands
• Shorter, more memorable
• Slight technical complexity --- apex requires A record (CNAME flattening on Cloudflare makes this easy)
• Configure www.yourbrand.com to redirect to apex

www (www.yourbrand.com) as canonical

• Traditional preference; some performance advantages for very high traffic
• Easier DNS --- CNAME is simpler than A records
• Configure apex (yourbrand.com) to redirect to www

What matters either way

• Pick one; configure the other to redirect
• Update all marketing materials, social bios, email signatures to match
• Set canonical URL in your app's meta tags
• Submit the canonical version to Google Search Console

Step 6: Subdomain patterns (app.brand.com vs brand.com/app)

Some products use separate subdomains for marketing site and app. Common patterns.

Pattern A: Marketing on apex, app on subdomain

• yourbrand.com --- Marketing site (Webflow, custom built, or Greta marketing surface)
• app.yourbrand.com --- The actual application
• Pros: Clear separation, easier to swap marketing tools, common pattern users recognize
• Cons: Cookie domain considerations; auth flows need to handle cross-subdomain

Pattern B: Everything on one domain

• yourbrand.com --- Marketing landing page
• yourbrand.com/app --- The application at a path
• Pros: Single domain, simpler auth, SEO consolidation
• Cons: Marketing and app share the same infrastructure; harder to swap tools later

For solo founders shipping fast, single-domain pattern is simpler. For brands using separate tools for marketing (Webflow) and app (Greta), the subdomain pattern is cleaner.

Step 7: Branded email (you@yourbrand.com)

Branded email signals real business. The setup is separate from app hosting.

Email hosting options

• Google Workspace --- Most common. ~$6--$18/user/month. Gmail interface with your domain.
• Microsoft 365 --- Comparable pricing; Outlook ecosystem.
• Fastmail --- Independent provider, privacy-focused, ~$5/user/month.
• Zoho Mail --- Lower cost, free tier for personal use.
• Forwarding-only (free options) --- ImprovMX, ForwardEmail.net. Forwards you@yourbrand.com to your existing personal email. Free or very cheap; suitable until you need to send from yourbrand.com.

DNS records for email

• MX records --- Tell mail servers where to deliver email for your domain
• SPF record (TXT) --- Lists authorized sending servers; prevents spoofing
• DKIM record (TXT) --- Cryptographic signing; verifies email actually came from your domain
• DMARC record (TXT) --- Policy for what to do if SPF/DKIM checks fail

Your email provider gives you the exact values to add; copy-paste into DNS. Email deliverability depends heavily on these records being correct.

Step 8: DNS propagation and patience

DNS changes don't take effect instantly. Propagation is the process of changes spreading across DNS resolvers worldwide.

• Typical propagation --- 5 minutes to 1 hour for most resolvers
• Maximum propagation --- Up to 48 hours in rare cases (older resolvers with long TTLs)
• Check propagation status --- Use tools like whatsmydns.net to see what different resolvers are returning
• Test from different networks --- Mobile data, office Wi-Fi, friend's network. If they all see the new IP, propagation is done.
• TTL matters --- Lower TTLs (5 minutes) propagate faster; higher TTLs (24 hours) propagate slower. Set TTLs low before making changes; raise them after.

When to use Cloudflare

Cloudflare as DNS provider (free) adds capabilities beyond basic DNS.

Benefits

• Faster DNS resolution globally
• CNAME flattening --- Use a CNAME at the apex domain (normally not allowed)
• DDoS protection at the DNS layer (free tier covers most needs)
• Page Rules and redirects without app-level changes
• Analytics on traffic and DNS queries

Setup

1. Create Cloudflare account; add your domain
2. Cloudflare imports existing DNS records (verify them)
3. Update nameservers at your registrar to Cloudflare's
4. Wait for nameserver propagation (typically 1--24 hours)
5. Manage DNS in Cloudflare from now on

For most solo founders, Cloudflare as DNS is worth doing. Free, faster, and the DDoS protection is genuinely useful.

Post-domain checklist (don't skip this)

Once your custom domain is live, several things need updating. Skipping these breaks integrations silently.

• OAuth callback URLs --- Google, GitHub, Microsoft, etc. Add the new domain to authorized callback URLs
• Stripe webhook URLs --- Update from old subdomain to new domain in Stripe dashboard
• Email FROM addresses --- Update transactional email service (Resend, Postmark) to use new domain
• SPF/DKIM/DMARC records --- If sending from new domain, add proper records for email deliverability
• Social bios --- Twitter/X, LinkedIn, Instagram, Product Hunt all need the new URL
• Marketing materials --- Business cards, slide decks, email signatures, one-pagers
• Documentation --- Help docs, onboarding emails, in-app help all reference URLs
• Robots.txt and sitemap --- Submit new sitemap to Google Search Console under the new domain
• Analytics --- Set up new property in Google Analytics 4 or PostHog for the new domain
• Redirect old URL --- yourapp.greta.sh should 301-redirect to yourbrand.com to preserve any existing links
• Update any hardcoded URLs in the app codebase --- Often missed; search for the old domain string and replace

Common Mistakes Connecting Custom Domains

• Wrong DNS record type --- Using CNAME at apex when A record is required. Most registrars don't support CNAME at apex; use Cloudflare for CNAME flattening or stick with A records.
• Forgetting www vs apex consistency --- Users land on the wrong version because both resolve but only one has SSL. Configure redirect from non-canonical to canonical.
• Cached DNS confusing testing --- You see the old IP; users see the new one (or vice versa). Test from multiple networks.
• Skipping post-domain checklist --- OAuth, Stripe webhooks, email FROM addresses silently break. Run the full checklist before celebrating.
• Bad SPF/DKIM/DMARC --- Transactional emails go to spam after domain change. Set up email auth records properly.
• Ignoring expired registrations --- Set auto-renew. Forgetting to renew is the #1 way to lose your brand to domain squatters.
• Switching registrars unnecessarily --- Don't move registrars during launch period. Settle in, then optimize later if needed.
• Buying TLDs you don't need --- One .com is enough. Buying .net, .org, .io defensively is rarely necessary for indie SaaS.
• Not adding analytics under the new domain --- You think your launch is failing; actually analytics is misconfigured. Verify analytics before launch.

Frequently Asked Questions

Q1: How much does a custom domain cost? A .com is typically $10--$15/year. Cloudflare Registrar sells at wholesale (~$9). Other TLDs (.io, .ai) cost more. Plus email hosting if you want branded email ($5--$18/user/month) --- though forwarding-only is free.

Q2: Can I connect a custom domain to a Greta app on the free tier? Depends on the platform's plan structure. Most AI app builders include custom domain support in paid tiers. Greta typically includes custom domain in main subscriptions.

Q3: How long does the setup take? 30--60 minutes of work plus 5 minutes to 1 hour of waiting for DNS propagation. SSL certificate issuance takes another few minutes. Total from buying the domain to live HTTPS: usually under 2 hours.

Q4: Do I need Cloudflare? No, but it's free and worth using. Faster DNS, free DDoS protection, CNAME flattening for apex domains, and decent analytics. Most indie founders end up on Cloudflare eventually.

Q5: What if my domain has been registered by someone else? Check if they're actually using it. Some sit on aftermarket sites; some are abandoned. You can offer to buy. If the price is unreasonable, pick a different name.

Q6: Can I change my domain later? Yes, but it's painful. SEO suffers, social shares break, customers need to update bookmarks, integrations break. Better to pick the right domain from the start and stick with it.

Q7: What about international domains (.co.uk, .de, .au)? Useful if your audience is geo-specific. For global SaaS, .com remains the default. For country-specific products, the country TLD adds local credibility.

Conclusion

• Connecting a custom domain to your Greta app is the single biggest credibility upgrade for a launched product. 30--60 minutes of work; permanent impact.
• DNS basics worth knowing: A records (apex domain to IP), CNAME records (subdomain to another domain), TXT records (verification + email), MX records (mail servers). Most platforms tell you exactly what to add.
• SSL certificates are automatic on modern platforms via Let's Encrypt. Free, auto-renewing, trusted by all browsers. Add the DNS record correctly and SSL handles itself.
• Don't skip the post-domain checklist. OAuth callbacks, Stripe webhooks, email FROM addresses, social bios, marketing materials. The launch isn't complete until the checklist is.

Buy your domain today. Connect it to your Greta app in the next hour. Run the post-domain checklist this week. Your app stops being 'that thing I built on a platform' and starts being a real product with a real brand. The technical work is small; the credibility upgrade is permanent. Every minute of the build pays off the moment a customer types your URL into their browser and sees a real, branded, HTTPS-secured product.