Skip to content

Domains

A domain is a hostname you connect to MicroApps and prove you own. Once verified, you can map it to any pod and turn on SSL. You bring the name; we handle the certificate and the routing.

Types

You do not pick a type when you add a domain. We derive it from the name you enter:

  • fqdn - a root domain like example.com.
  • subdomain - a subdomain like app.example.com.
  • local - an internal-only name, not exposed to the public internet.

The type shows up in the domain's details after you add it. That's the only place it lives.

Lifecycle

  1. Add - enter the domain name. That is the only input.
  2. Verify ownership - publish the verify-domain TXT record we show you. Until you do, the domain sits on your account unlocked, and anyone else who proves ownership can open a 48-hour claim on it (see below). Once verified, ownership latches to your account.
  3. Map to a pod - point the domain at a pod, choosing http or https and the internal port your app listens on.
  4. Enable SSL - publish the _acme-challenge CNAME from the DNS tab, then one click. We provision the certificate through that record and renew it before it expires, forever.

You can unmap a domain later without losing anything: unmapping keeps the SSL certificate, so re-mapping does not trigger a fresh issue.

Globally unique names

A domain name can only be owned by one account at a time. When you add a name someone else already registered:

  • If they added it but never verified it, you can claim it by publishing the verify-domain TXT record within 48 hours. First to verify wins.
  • If they have already verified it, it is locked to their account and cannot be claimed. You would need them to remove it first.

This is how a domain transfers between accounts: the old owner removes it (or lets an unverified claim lapse), and the new owner verifies.

Notes

  • A domain maps to one pod at a time, but a single pod can serve many domains, each with its own certificate.
  • You cannot map a domain to a database pod.
  • SSL certificates auto-renew. You never touch a certificate file.
  • The domain's DNS tab shows every record we expect, marks each as verified or not, and flags which are required versus recommended.

See also

Built for the long tail.