Custom domains
Attach your own domain to a web service with automatic TLS.
Every web service is born with a free *.appentic.app subdomain and a valid TLS certificate. That's fine for development, staging, and internal tools, but most production apps want their own hostname. Appentic handles the certificate lifecycle for you, so once DNS is pointing at the right place you can forget about it.
Adding a domain
From the service dashboard, open Domains, then click Add domain. Enter the hostname you want to attach (for example api.example.com) and Appentic will show you the DNS records you need to create: a CNAME for subdomains or an ALIAS/ANAME for apex domains.
Add the record at your DNS provider, then come back to Appentic and click Verify. Appentic polls your DNS until the record resolves, then provisions a TLS certificate via Let's Encrypt. Certificate issuance usually takes under a minute, and the domain goes live the moment the cert is ready.
Apex domains
For apex domains (example.com without a subdomain), your DNS provider needs to support ALIAS, ANAME, or flattened CNAME records. Cloudflare, Route53, DNSimple, Namecheap Advanced DNS, and most other modern providers all do.
If your provider only supports standard CNAME records at the apex (which isn't valid DNS), the usual workaround is to point www.example.com at Appentic with a CNAME and set up an HTTP redirect from the apex to the www subdomain. Any provider can do that.
Automatic renewal
TLS certificates are renewed automatically well before they expire. There's nothing for you to configure, no cron job to run, and no expiry calendar to maintain. If a renewal ever fails (for example, because you removed the DNS record) Appentic emails you before the old cert expires.