---
title: "About Custom Domains"
canonical: "https://help.cartinuum.com/space/WC/4538335304/About%20Custom%20Domains"
format: markdown
---
By default, deployed applications in Managed Experience Builder are hosted using a Cartinuum-managed URL.

Custom Domains allow you to publish applications using your organisation's own domain name, providing a more professional and branded experience for your users.

For example:

| Default URL | Custom Domain |
| --- | --- |
| `app.cartinuum.com/container-app/ex/exb-VE36936wmH/16` | `experiences.acme.com/16` |

### Why Use a Custom Domain?

Custom domains provide several benefits:

#### Consistent Branding

Users access applications using your organisation's domain rather than a third-party URL.

Examples:

- `experiences.acme.com`
- `maps.acme.com`
- `engage.acme.com`

#### Improved User Trust

Applications hosted on your own domain are often more familiar and trusted by end users.

#### Simpler URLs

Custom domains are easier to communicate in documentation, emails, training materials, and support resources.

#### Centralised Domain Management

Your organisation retains control over DNS and domain ownership while Cartinuum manages the underlying hosting infrastructure.

### How Custom Domains Work

When a custom domain is configured:

1. Your organisation creates DNS records for the chosen subdomain.
2. Cartinuum provisions and manages an SSL certificate.
3. Traffic is routed securely to the Managed Experience Builder hosting platform.
4. End users access your deployed applications using your domain name.

The underlying application hosting remains fully managed by Cartinuum.

### SSL Certificates

All custom domains use HTTPS.

SSL certificates are automatically provisioned and renewed by Cartinuum using AWS Certificate Manager.

You do not need to purchase, install, or renew certificates yourself.

### DNS Requirements

To enable a custom domain, you will typically create:

- A CNAME record for routing from the application subdomain.
- A TXT record used to validate ownership of the domain.

Exact DNS values are provided during the custom domain configuration process.

### Custom Domains and Deployments

A custom domain points to your deployed applications.

Updating your applications does not require any further DNS changes.

Once the domain has been configured, future application deployments continue to use the same custom domain automatically.

### What's Next?

To configure a custom domain, continue to:

[Configure a Custom Domain](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538564635)