Self-hosted PaaS
Use subdy.io names with Coolify or Dokploy.
At the end your PaaS deploys apps on *.myapp.subdy.io with HTTPS.
Both Coolify and Dokploy work the same way: every app gets a hostname, the built-in proxy (Traefik/Caddy) answers on it. You need two records pointing at the PaaS server:
| Type | Name | Value |
|---|---|---|
A | @ | your server IP |
A | * | your server IP |
Set them in the dashboard or via set_record — the
* wildcard makes every anything.myapp.subdy.io land on the proxy.
Coolify (v4)
Settings → Instance domain: myapp.subdy.io. New apps default to
<app>.myapp.subdy.io; per-app domains are set in Domains. Coolify's
proxy fetches per-name certificates via HTTP-01 automatically — no
DNS-01 needed. For a true wildcard certificate instead, issue the
managed one and mount it — see Wildcard TLS.
Dokploy (v0.x)
Server → Domains: add myapp.subdy.io as the base domain; each
project gets <app>.myapp.subdy.io. Certificates: Let's Encrypt
per-domain (HTTP-01) out of the box.
Gotcha: propagation and first deploy
Deploy after the records are active (seconds on Subdy) — otherwise
the PaaS's first ACME attempt fails and you'll wait for its retry timer.
Check with dig +short anything.myapp.subdy.io.