Custom domains with HTTPS that arrives on its own
Add a hostname and the portal shows you the exact record to create. Press Check DNS, and only once the name resolves to your server is a router attached and a certificate requested.
What you get
No DNS API token
Certificates are issued over HTTP-01, so your DNS provider never has to hand the platform a credential.
DNS first, certificate second
Attaching a router before DNS resolves would burn Let’s Encrypt’s five failures per hostname per hour. Checking first means you are never locked out of your own certificate.
Behind Cloudflare
A hostname behind a proxying CDN cannot point straight at your server, so it verifies with a TXT record instead — offered only when every address it resolves to is the CDN’s.
Certificates you can see
Every issued certificate is listed with its issuer, validity, key type, and fingerprint, and an alert opens fourteen days before one expires.
In detail
- Once a hostname is attached, the application is no longer published on a numbered port; it keeps a loopback-only binding so the platform can still health-check it.
- Every routing label a Compose file declares is removed and replaced with the platform’s own, so no application can claim another’s hostname.
- One proxy per managed server, read from that server’s own Docker socket.
- The proxy’s own log is readable in the portal, next to its status.
- No private key is ever read: the certificate panel parses only the leaf certificates.
Works well with
Git deployments
Push to your branch and it ships itself — built, health-gated, and rollback-ready.
Request analytics
Every request to every app — read from the proxy, with no script to install.
Your own servers
One command connects a VPS you already own. Nothing inbound is opened.
Your server is ready when you are
Create an account, connect a VPS, and ship your first application.