Custom Domains
Connect your own domain
Custom Domains
Connect your own domain to your Knitt project with automatic SSL certificate provisioning.
Overview
By default, your Knitt project is accessible at {'{'}tenant-id{'}'}.knitt.app. You can add your own custom domain (like api.yourcompany.com) to give your project a professional, branded URL.
SSL certificates are automatically provisioned for all custom domains using Let's Encrypt, ensuring your API and content are always served securely over HTTPS.
Adding a Custom Domain
Step 1: Add domain in dashboard
Navigate to your tenant dashboard and go to Settings → Domains. Click "Add Domain" and enter your custom domain or subdomain.
We recommend using a subdomain (like api.yourcompany.com) rather than your root domain.
Step 2: Update DNS records
After adding your domain, Knitt will provide DNS record values that you need to add to your domain's DNS settings.
For subdomains (recommended)
Type: CNAME Name: api (or your chosen subdomain) Value: hosting.knitt.app TTL: 3600
Example: api.yourcompany.com → hosting.knitt.app
For root domains
Type: A Name: @ (or leave blank) Value: 185.199.108.153 TTL: 3600
Some DNS providers support ALIAS or ANAME records, which work better for root domains.
Step 3: Verify DNS propagation
DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. You can check the status in the Knitt dashboard.
Check DNS manually
You can verify DNS propagation using these commands:
dig api.yourcompany.com # or nslookup api.yourcompany.com
Step 4: SSL certificate provisioning
Once DNS is verified, Knitt automatically requests and installs an SSL certificate from Let's Encrypt. This usually takes 1-2 minutes.
When complete, your custom domain will be live with HTTPS enabled. All HTTP requests are automatically redirected to HTTPS.
Managing Multiple Domains
You can add multiple custom domains to a single tenant. This is useful for:
- Supporting multiple brands on the same backend
- Providing regional domains (e.g.,
api.example.co.ukandapi.example.com) - Migrating from an old domain to a new one
Each domain gets its own SSL certificate and all work simultaneously.
Common DNS Providers
Cloudflare
When using Cloudflare, make sure the DNS record is set to "DNS only" (grey cloud) during initial setup. Once verified, you can enable Cloudflare's proxy (orange cloud).
Route 53 (AWS)
Use CNAME records for subdomains or ALIAS records for root domains. Set TTL to 300-3600 seconds.
Namecheap
Add a CNAME record with the subdomain as the host and hosting.knitt.app as the value.
GoDaddy
Use CNAME for subdomains. Forwarding (redirect) will not work - you must use actual DNS records.
Troubleshooting
Domain not verifying
- • Double-check DNS records are entered correctly
- • Wait for DNS propagation (can take up to 48 hours)
- • Ensure you're adding the record to the correct domain/subdomain
- • Try flushing your DNS cache locally
SSL certificate not provisioning
- • Verify DNS is pointing correctly
- • If using Cloudflare, temporarily disable the proxy
- • Check for any CAA DNS records that might block Let's Encrypt
- • Contact support if the issue persists after 24 hours
"Too Many Redirects" error
This usually happens with Cloudflare when SSL mode is set to "Flexible". Change it to "Full" or "Full (strict)" in your Cloudflare SSL/TLS settings.
Removing a Domain
To remove a custom domain, go to Settings → Domains and click the delete button next to the domain. The SSL certificate will be automatically revoked.
Removing a domain makes it immediately inaccessible. Make sure to update any applications or services using this domain first.
Next Steps
Last updated: February 7, 2026