01The DNS part is yours either way
No host escapes DNS. You bought the domain at a registrar; records pointing it at a host get added by you, at that registrar, on both platforms. Any page promising otherwise is selling you something. What differs is everything after the records: who watches certificates, who notices a renewal, and who answers when a name will not resolve on the morning a campaign launches. The pillar page keeps the wider hosting context.
So the comparison below is narrow on purpose. It is about the managed half of a custom domain, not the DNS half, because the DNS half is identical.
02Where managed takes over
Add the domain in the portal
Type it in and the site starts answering on it once DNS lands. There is no file to edit and no redeploy to schedule.
Point the records
The portal names the records to add at your registrar. You add them once; they are yours, and they stay yours if you ever leave.
Certificates arrive
HTTPS is issued for the custom domain automatically, alongside the free yourname.loomweb.co address the site already had.
Renewals run themselves
Certificates renew for as long as the site runs, on both names. There is no expiry date in a calendar anywhere, which is the entire feature.
03Certificates, issuance and renewal
Credit where due: Pages also issues certificates for custom domains, and renewal there is automatic too. A table that made that row look one-sided would be lying by layout, which is why the table below refuses to.
The managed difference lives at the edges of those automatic systems. When issuance stalls, on a misconfigured record, on a propagation delay, on something the documentation does not quite cover, the Pages path is documentation, community threads and whatever patience is left over. The managed path is an email inbox where the person replying can see your portal. Neither is magical. One of them has a human in it. For the whole-host picture rather than the domain slice, the alternative guide is the broader comparison.
04What you are actually comparing
| Pages custom domain | LoomWeb custom domain | |
|---|---|---|
| DNS records | Added by you, owned by you | Added by you, owned by you |
| Certificate issuance | Automatic | Automatic |
| Certificate renewal | Automatic | Automatic |
| Included address | username.github.io | yourname.loomweb.co |
| When verification stalls | Documentation and community | A support inbox |
| Hosting cost | Free | 14-day trial, then $39 a month |
Read honestly, that table says the domain features match. They do. The managed part is the operator behind them, and the deployment pipeline sitting around them.
05Domain questions
Can I use a domain from GoDaddy, Namecheap or VentraIP?
Yes. Any registrar works; you point the records wherever the portal names them.
Apex or www?
Both can be served. Add the records the portal asks for and certificates follow either name.
I am live on a Pages custom domain already. Is moving risky?
DNS repointing always carries a window where caches disagree, and nobody honest promises zero downtime. Do it at a quiet hour; the records are the same kind on both sides.
Do I have to give up the loomweb.co address?
No. It is included from the start; the custom domain joins it, and both keep certificates.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.