Custom Domain Hosting

What it is

Custom domain hosting means your ybuild app is served to the world on the domain you own — yourbusiness.com, not a throwaway subdomain. ybuild hosts the running app and handles the SSL certificate, DNS routing, and traffic. Your customers only ever see your brand.

Why it matters

A business system that lives on someone else's URL doesn't look like a business. Your own domain is where customers trust you, where you send traffic, and where your emails and payments make sense. Owning that address is the difference between a demo and a company.

How it works on ybuild

You point your domain at ybuild once, and the app you built stays hosted and served there automatically. There's no separate deploy step and no exporting the code to another host — the live app and the domain are managed together on ybuild. Change the app and the version on your domain updates in place.

What actually happens when you point a domain at ybuild

A domain is just a name. On its own it points nowhere — turning it into a live, secure address involves three moving parts most people never see, and ybuild runs all three for you.

First is DNS. When you connect yourbusiness.com, you add one record at your registrar that tells the internet where the name resolves — a CNAME for a subdomain like www, or an A / ALIAS-style record for the naked root domain (the apex can't take a plain CNAME under the DNS spec, which is exactly the kind of edge that trips people up doing it by hand). ybuild gives you the exact record to paste, then watches for it to resolve. Changes ripple out over minutes to a few hours as caches expire based on each record's TTL, and in rare cases up to 48 hours.

Second is the certificate. The moment your record resolves to ybuild, an automated ACME exchange — the IETF-standard protocol behind Let's Encrypt and modern certificate authorities — proves you control the domain and issues a TLS certificate for it. That is what turns http:// into a padlocked https://. These certificates are short-lived by design and renew automatically well before they expire, so the green padlock never lapses. You never touch certbot, a renewal cron job, or a private key.

Third is routing and delivery. Traffic to your domain lands on ybuild's edge, terminates TLS, and is served the current version of your app — the same build that holds your database, your logins, and your business logic. HTTP is redirected to HTTPS, www and the apex are reconciled to one canonical address, and the app answers on your domain the way it answered on the ybuild preview URL a minute earlier. The whole chain — name, certificate, delivery — is one connected thing you manage in one place, not four accounts you stitch together.

Wiring it yourself vs. getting it on ybuild

It is worth being honest about the DIY path, because the gap is where the real value sits.

Doing it yourself, going live on a custom domain is a checklist that never quite ends: provision a server or host, deploy the build to it, buy the domain, set A and CNAME records without breaking the apex, decide whether www or the root is canonical and 301-redirect the other, install an ACME client, pass the HTTP-01 or DNS-01 challenge, schedule renewals so the certificate doesn't silently expire at 2am, force HTTPS, add HSTS, and then keep the server patched forever. Every one of those steps is a place the site can go down, and an expired certificate or a mixed-content warning doesn't degrade gracefully — it slams a full-screen browser warning in front of every customer.

On ybuild, that entire column collapses into one action. You describe the app in a prompt and it is built as a running, hosted full-stack system — front end, backend, and database together. You connect your domain once with the record ybuild hands you, and the platform issues the certificate, renews it, redirects HTTP to HTTPS, canonicalizes www and apex, and keeps the app served. There is no export, no zip, no second host to sign into, no renewal you can forget. When you change the app — a new field, a new page, a new price — the live version on your domain updates in place, still hosted on ybuild, still on your address.

The distinction matters because the DIY stack isn't just more work up front — it's permanent operational surface. Someone has to own the renewals, the patching, and the 'why is the site down' page at midnight. Custom domain hosting on ybuild means that someone is the platform, and the thing you own is the part that makes you money: the domain, the data, and the app.

The gotchas that bite live sites, and what your own domain means for the business

A few edge cases catch almost everyone who runs a domain, and it's worth knowing ybuild absorbs them. The apex-domain CNAME limitation means yourbusiness.com and www.yourbusiness.com need different treatment; ybuild handles both and points one at the other so links never fork. DNS propagation delay is real — if the address looks unchanged for an hour after you add the record, it's caches expiring, not a failure. Certificate renewal is the classic silent killer: certificates are deliberately short-lived and getting shorter, and a missed renewal takes the whole site offline until it's fixed — which is precisely why automatic issuance and renewal is not a nicety but the core of the feature. Mixed content and stray HTTP links throw browser warnings even on an HTTPS site; serving everything over your one canonical HTTPS domain keeps that clean.

What you get in return is not cosmetic. Your own domain is the trust surface for the whole business. Browsers now flag any plain-HTTP page as 'Not Secure' in the address bar, and customers read that literally — an unbranded subdomain with a warning is a lost signup. A real domain with a valid certificate is the baseline for looking like a company that takes payments.

It also compounds over time. Search engines treat HTTPS as a ranking signal and index your domain, not a platform's — so every page you ship builds equity in an address you own, not a landlord's. Your invoice links, your booking confirmations, and your marketing all point to one name you control. If you ever need to change how the app is built, the domain and its accumulated trust, backlinks, and bookmarks stay put. That is the quiet difference between renting a spot on someone else's URL and owning the front door: on ybuild the app is hosted for you, but the address, and the business built on it, is unambiguously yours.

FAQ

Do I need to buy a domain separately, or does ybuild give me one?

You bring your own domain from any registrar — that name stays yours. ybuild hosts your running app on it: you paste the one DNS record ybuild shows you, and the live app is served on yourbusiness.com with SSL handled automatically. You own the address; ybuild runs the app behind it.

How long until my domain is live after I connect it?

Usually minutes to a couple of hours. Once you add the DNS record, ybuild watches for it to resolve, then automatically issues the TLS certificate so the site opens over HTTPS. DNS caches can take up to 48 hours to fully update in rare cases, but most domains are live and secured the same day.

Who manages the SSL certificate and its renewals?

ybuild does, start to finish. The certificate is issued automatically the moment your domain resolves, and it renews on its own well before it expires — the padlock never lapses. You never install an ACME client, run a renewal job, or touch a private key.

Can I use my root domain like yourbusiness.com, not just www?

Yes. ybuild supports both the apex (yourbusiness.com) and www, and reconciles them to one canonical address so links and SEO don't split. Subdomains like app.yourbusiness.com or book.yourbusiness.com work the same way — point them at ybuild and the app is served there.

What happens to my live domain when I change the app?

Nothing breaks. When you edit the app — add a field, a page, or a price — the new version updates in place at the same URL on your domain, still hosted on ybuild. Your domain, links, and bookmarks stay put; there's no re-deploy and no re-pointing to do.