Custom domains
Pointing your own domain at a Deploy project.
Every Deploy project gets a free *.apps.suzko.net subdomain. To
use your own:
Add it in the dashboard
/tools/deploy/ → Domains → Add
domain → type the hostname (e.g. app.example.com). We show you
the DNS records to add.
DNS
You'll need either:
Subdomain (app.example.com):
CNAME app <project-slug>.apps.suzko.net.
Apex (example.com):
Most DNS providers don't allow CNAME at the apex. Use an A record
pointing to our edge IP (shown on the domain page). Or use a CNAME-
flattening provider like Cloudflare or Suzko DNS.
Add the record at your DNS provider. Save.
Verification
We poll the DNS every 30 seconds. Once it resolves to our edge:
- Verified flag turns green
- We issue a Let's Encrypt cert via HTTP-01
- Traefik picks up the new route
- Your domain serves the app
Total time from "saved DNS" to "HTTPS works": usually 1–5 minutes.
Wildcards
For *.example.com patterns: add multiple individual domains (one
per subdomain you want). True wildcard certs require DNS-01
challenges and aren't supported on Deploy yet — workaround is one
domain per subdomain.
Removing a domain
Domains → Remove. The domain is unrouted within seconds. DNS at your end still points at us until you change it — make sure you do, otherwise you'll get connection errors.
Multiple domains, one project
Supported. Each is its own row with its own cert. Useful for www
- apex pointing at the same app.
www → apex (or apex → www)
Two domains added, both routed to the same project. To force one canonical, add a redirect rule from one to the other — most frameworks support this in their own config, otherwise we can add an edge-level redirect (open a ticket).