Custom Domains
Default URLs
Every service and app gets a URL under *.compacthive.dev:
https://<your-slug>-<service>.compacthive.dev
Examples: https://acme-ci.compacthive.dev (Woodpecker CI), https://acme-grafana.compacthive.dev (Grafana), https://acme-my-api.compacthive.dev (a custom app). These work immediately after deployment; TLS is handled for you.
Adding a custom domain
Custom domains are available on every tier, with a per-tier limit on how many you can register:
| Tier | Custom domains |
|---|---|
| Basic | 3 |
| Team | 10 |
| Pro | 25 |
| Business | 50 |
| Enterprise | Effectively unlimited |
- Go to portal → Domains.
- Enter your domain and pick the service or app it should point to.
CreateAttheyour DNSrecordprovider,the form shows you — aCNAMEpointing atcompacthive.devis recommended (works cleanly behind Cloudflare or any CDN that supports CNAME flattening);create an A recordalternativefor that hostname pointing at the IP address the form shows you. Use an A record, not a CNAME — a CNAME tocompacthive.devdoes not work for a domain you own (it isalsoashownCloudflare-proxiedifnameyourinDNSCompactHive'sprovideraccount,requiressoone.foreign hostnames are rejected at Cloudflare's edge).- Click
VerifyCheck — CompactHivechecksconfirms the route for your hostname is configured. It does not check your DNSresolution.or certificate. - Once
verified,your DNS record has propagated, traffic to your domain routes to your app or service.
TLS for custom domains
TLSCompactHive does not yet issue certificates for custom domains. Plain HTTP works as soon as DNS points at CompactHive, but connecting over HTTPS directly shows a customcertificate domainwarning, isbecause managedthe onedge youronly side.holds Puttingcertificates your domain behind Cloudflare (or another CDN/proxy) in front offor CompactHive's edgeown isdomains.
For trusted HTTPS today, put your record behind your own CDN/proxy. With Cloudflare: keep the simplestA option;record CompactHive'proxied (orange cloud) and set the zone's SSL/TLS mode to Full — not Full (strict), which rejects the CompactHive edge acceptscertificate plainfor HTTPyour fromhostname. Cloudflare then serves a frontingtrusted proxy and routes based on the Host header. If you don't front it with a CDN, you'll needcertificate to terminateyour TLS yourself before forwarding traffic to CompactHive.visitors.