Custom domains
Starter Custom domains let you serve a deployment from your own domain — for example ops.yourcompany.com instead of the default your-app.qraptor.app.
By the end of this page you will have pointed your own domain at a deployment and seen it go live over HTTPS.
Prerequisites
- Starter or higher. The number of custom domains scales with your plan (Starter 1, Pro 3, Team 10, Enterprise unlimited).
- Admin role.
- A running production deployment.
- Access to your domain’s DNS settings.
How verification works
You add a custom domain by proving you control it. The Studio gives you two DNS records to add at your DNS provider:
- A CNAME record that points your domain at the deployment.
- A one-time TXT record that verifies ownership.
After you add them, the Studio checks for the records automatically and provisions an HTTPS certificate — there’s no manual “verify” button to press.
Adding a custom domain
Open the deployment’s domain settings
Open the deployment and go to its Settings, then the custom domain section. Enter your domain (for example ops.yourcompany.com).
Add the DNS records
The Studio shows the exact CNAME and TXT records to create. Copy them into your DNS provider.
The TXT verification value is shown once. Add it before leaving the page.
Wait for it to go live
The status updates on its own as it progresses: Pending DNS → Verifying certificate → Live. DNS changes can take a few minutes to propagate. If a check hasn’t picked up your records yet, use Recheck.
HTTPS certificates
- Certificates are provisioned and renewed automatically — nothing to upload.
- All traffic is served over HTTPS.
Removing a custom domain
In the deployment’s domain settings, choose Remove. Traffic reverts to the default qraptor.app URL. Clean up the DNS records at your provider afterward.
Removing a custom domain stops traffic on it immediately. Update anything that points at the custom domain before removing it.
Common issues
- Stuck on Pending DNS — the records aren’t visible yet. Confirm the CNAME and TXT values match exactly, wait for propagation, then Recheck.
- Verifying certificate for a long time — a conflicting CAA record at your DNS provider can block certificate issuance. Check your CAA records.
- Plan limit reached — custom domains are limited by plan. Upgrade your plan to add more.
- Domain already in use — a domain can attach to only one deployment. Remove it from the other deployment first.