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.
- At your DNS provider, create an A record for that hostname pointing at the IP address the form shows you. Use an A record, not a CNAME — a CNAME to
compacthive.devdoes not work for a domain you own (it is a Cloudflare-proxied name in CompactHive's account, so foreign hostnames are rejected at Cloudflare's edge). - Click Check — CompactHive confirms the route for your hostname is configured. It does not check your DNS or certificate.
- Once your DNS record has propagated, traffic to your domain routes to your app or service.
TLS for custom domains
CompactHive 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 certificate warning, because the edge only holds certificates for CompactHive's own domains.
For trusted HTTPS today, put your record behind your own CDN/proxy. With Cloudflare: keep the A record proxied (orange cloud) and set the zone's SSL/TLS mode to Full — not Full (strict), which rejects the CompactHive edge certificate for your hostname. Cloudflare then serves a trusted certificate to your visitors.