Custom Domains
Every web service on Stackpad gets a default URL at your-project.your-org.stackpad.eu. You can also connect your own custom domain with automatic HTTPS.
Adding a custom domain
- Go to your project and select the web service
- Open the Domains tab
- Click Add Domain and enter your domain (e.g.
app.example.com) - Configure your DNS as shown below
- Stackpad verifies the DNS record and provisions an HTTPS certificate
DNS configuration
You need to create a DNS record pointing your domain to Stackpad. The type depends on the domain:
Subdomains (recommended)
For subdomains like app.example.com or docs.example.com, create a CNAME record:
| Type | Name | Value |
|---|---|---|
| CNAME | app | your-project.your-org.stackpad.eu |
Root domains
For root domains like example.com, create an A record pointing to Stackpad’s IP address. The IP is shown in the dashboard when you add the domain.
| Type | Name | Value |
|---|---|---|
| A | @ | (shown in dashboard) |
HTTPS certificates
Stackpad automatically provisions and renews HTTPS certificates for your custom domains using Let’s Encrypt via Caddy. You don’t need to configure anything — certificates are issued as soon as DNS verification succeeds.
- Automatic provisioning — certificate is issued within minutes of DNS verification
- Automatic renewal — certificates are renewed before expiration
- HTTP → HTTPS redirect — all HTTP traffic is automatically redirected to HTTPS
Multiple domains
You can add multiple domains to a single service. One domain is marked as primary and the rest redirect to it. This is useful for:
www.example.com→ redirects toexample.com- Old domains redirecting to a new domain
Domain limits by plan
| Plan | Custom domains per organization |
|---|---|
| Starter | 0 |
| Pro | 5 |
| Business | 20 |
What’s next?
- Git push deploy — how deployments work
- Preview deployments — get unique URLs for pull request branches