# Domains

**Summary:** Point your own domain at Subrite with a CNAME record for production and stage. Subrite sets up HTTPS automatically.

- Space: [Developers](https://www.subrite.no/developers)
- Source: https://www.subrite.no/developers/domains
- Updated: 2026-09-23
- Markdown index: https://www.subrite.no/developers/llms.txt

To ensure that your Subrite deployment is accessible via a custom domain, you need to set up a CNAME record. Follow the instructions below to configure the CNAME for both production and stage environments.

<a id="setting-up-cname"></a>
## Setting up CNAME

<a id="production-environment"></a>
### Production environment

For the production environment, configure your DNS settings to include the following CNAME record:

```text
cname.webapp.subrite.no
```

<a id="stage-environment"></a>
### Stage environment

The stage environment is used for testing and development purposes before deploying changes to the production environment. This allows you to validate new features and fixes in a controlled setting.

When setting up the stage environment, we will automatically add `[yourname].stage.subrite.no`. If you want a custom name for staging, you must include the following CNAME record in your DNS settings:

```text
cname.stage-webapp.subrite.no
```

<a id="automatic-https-ssl-setup"></a>
## Automatic HTTPS (SSL) setup

Subrite automatically applies HTTPS (SSL) to your custom domains, ensuring that all traffic to your site is secure and encrypted. There is no additional configuration required on your part for SSL certification. Once you have set up the CNAME records, Subrite will handle the SSL setup automatically.

By correctly setting up these CNAME records, you will ensure that your Subrite instances are properly accessible through your specified domains with secure HTTPS connections.