When you host your application with Sevalla, it’s automatically assigned a free sevalla.app domain as the primary domain upon successful deployment. This allows you to build, test, and preview your application before connecting your custom domain. When you’re ready to make your application live, you can add your custom domain on the Domains page. Every custom domain you add automatically includes a free SSL certificate. The temporary sevalla.app domains are automatically covered by the wildcard certificate of sevalla.app domain. (*.sevalla.app). If you want to add a custom SSL certificate, please contact our Support Team, who can manually upload this for you.Documentation Index
Fetch the complete documentation index at: https://docs.sevalla.com/llms.txt
Use this file to discover all available pages before exploring further.
Newly created applications use sevalla.app as the temporary domain. As Sevalla is a Kinsta product, we previously used kinsta.app temporary domains for applications. This is a normal part of the Sevalla experience. Your application will still be accessible and manageable through Sevalla’s interface even if it uses the kinsta.app domain.
If you use a Hobby pod for an application’s web process, you will not be able to add a custom domain to your application. You can upgrade your pod within Processes at any time in order to add a custom domain.
Add domain
In Sevalla, go to Applications > app name > Domains. Click Add custom domain and enter your domain name. If you want to cover all subdomains, select Wildcard and then click Add custom domain.If you add your domain without the wildcard subdomain, you should also consider adding the www version of the domain without the wildcard to ensure both versions are correctly configured.

Verify domain
To verify your domain, you need to add the TXT record and CNAME record shown to your domain’s DNS records. Some DNS providers, such as Namecheap, Spaceship, and Squarespace need the short version of DNS record names. Sevalla automatically provides both the full and short versions of each record, so you can use whichever format your DNS provider needs.
- Name:
_cf-custom-hostname - Value: Unique UUID value from Sevalla (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
- Name:
_acme-challenge - Value:
example.com.[unique verification token].dcv.cloudflare.com
Point domain
Once your domain is successfully verified, you can point it by adding the required A records to your domain’s DNS settings. Some DNS providers, such as Namecheap, Spaceship, and Squarespace, need the short version of DNS record names. Sevalla automatically provides both the full and short versions of each record, so you can use whichever format your DNS provider needs. If you select the Wildcard option, an additional A record for*.yourdomain.com appears to add to your domain’s DNS settings, which ensures all subdomains are covered.

Point WWW domain
We recommend that you point the www version of your domain to Sevalla (if you haven’t already). To do so, add the www version of the domain to Sevalla and repeat the steps to verify and point the subdomain.Change your primary domain
In the domains list, locate the domain you want to be the primary domain, click the kebab (three-dot) menu, and click Make primary domain. Verify that the correct domain is selected, then click Continue.
IP address
The IP address is shown when you point your domain. We use Cloudflare to secure our hosting infrastructure, so the corresponding IP you see for your application is a Cloudflare IP address. This means the owner of the IP address is Cloudflare, Inc., located in the United States of America. The IP address doesn’t reflect the physical place where your application is hosted, nor does it add any further latency to your application. Your application files are stored in the data center location you choose. We do not create copies of your application and store those copies elsewhere. We do not offer dedicated IP addresses because they aren’t necessary for most configurations. Since our infrastructure is secured by Cloudflare, sites, applications, and databases hosted on Sevalla use a range of shared IP addresses provided by Cloudflare. Our Cloudflare IP addresses are reserved for Sevalla customers only, so you won’t share an IP address with spam or adult sites or applications hosted elsewhere.Troubleshoot domain issues
Most domain problems happen during verification or pointing, and they usually come down to a conflicting or mis-entered DNS record. Work through the checks below in order.Domain won’t verify
If your domain stays unverified after you’ve added the TXT and CNAME records, check the following:- Remove any existing A or CNAME record on the root domain. If your domain already has an A or CNAME record (for example, pointing to a previous host), Cloudflare tries to verify ownership through that record, and verification fails. Remove the old A or CNAME record before verifying, then add the records Sevalla provides.
- Confirm the
_acme-challengerecord is a CNAME, not a TXT. The_acme-challengevalue Sevalla provides (ending indcv.cloudflare.com) must be added as a CNAME record. A common mistake is pasting it into a TXT record, which prevents the SSL certificate from being issued. - Disable the Cloudflare proxy on the verification records. If you use Cloudflare as your DNS provider, set the verification records to DNS only (grey cloud). Proxied (orange cloud) records don’t resolve publicly, so verification can’t complete. You can re-enable the proxy on your A or CNAME records after the domain is active.
- Remove conflicting or stale records. If you previously added and removed this domain in Sevalla, an old
_cf-custom-hostnameTXT value may still be in your DNS. Delete any outdated_cf-custom-hostnameor_acme-challengerecords and re-add the exact values shown in Sevalla. - Confirm the value matches exactly. Copy the value directly from Sevalla. A trailing space, a missing character, or a wrong record name causes verification to fail.
- Check the Time-to-Live (TTL) setting. This controls how long internet providers and other services remember your DNS settings before checking for updates. It is usually set to Auto or 5 minutes, but if it has been changed to a longer period, DNS propagation can take longer to take effect.
SSL certificate isn’t issued
Sevalla issues and renews your SSL certificate automatically once the domain is verified. If the certificate stays pending:- Keep the
_acme-challengeCNAME record in place. Removing it stops Sevalla from renewing your certificate, and you would need to re-add it. - Check for a CAA record conflict, described in Fix domain error below.
Fix domain error (CAA record conflict)
During the domain verification process, if a Fix domain error button appears next to the domain, this means a CAA record conflict is occurring. A CAA record is an optional DNS record that lets you specify which certificate authorities (CAs) are allowed to issue SSL certificates for your domain. If a domain has no CAA records, any CA can generate an SSL certificate for it if requested. If a domain has a CAA record, only the CA(s) specified in the CA record can generate an SSL certificate for the domain. To resolve this error, click the Fix domain error button and update the CAA record as indicated in the modal/pop-up. Alternatively, if you do not need a CAA record on your domain, you can remove the CAA record.Domain verified, but the application doesn’t load
If the domain verifies but doesn’t serve your application:- Confirm the A record (or CNAME) matches the exact value shown on the Point domain step in Sevalla. If you reused an old record, update it.
- If you use the Cloudflare proxy, make sure it’s enabled only on the A or CNAME records that point to Sevalla, not on the verification records.
- For wildcard domains, confirm you also added the
*.yourdomain.comA record.



