By default, Metabase will automatically provision a domain name for your Metabase that ends in metabaseapp.com (e.g., yourcompany.metabaseapp.com).
Pro and Enterprise plans allow you to add a custom domain. Setting a custom domain will update your instance’s Site URL. The Site URL is used for things like creating links in emails, auth redirects, and in some embedding scenarios.
How to add a custom domain to your Metabase
Log in to your Metabase store account.
Find the Metabase instance that you want to add the custom domain to, and select Manage on the bottom right of the instance’s card. Then click on the Domains tab.
You’ll see something like this:
- In the custom domain field (the input prefixed with
https://in the Metabase store), enter your custom domain (e.g., your.custom.domain).
Talk to whoever manages your Domain Name System (DNS) records, and have them add a CNAME to wherever you manage your DNS records. Point that CNAME to this URL:
So your CNAME record would look something like:
CNAME your.custom.domain us-1.cd.metabaseapp.com
Just to be clear: you don’t enter this record in the Metabase store; you enter it in wherever you manage your DNS records.
- If you’ve already set up SSO (like SAML or LDAP) for your Metabase, you’ll need to update the return URL in your identity provider configuration to include this new custom domain.
That’s it. You may need to wait a bit for the CNAME to update (this delay is specific to how DNS works, and not something Metabase has control over). Metabase will take care of the rest: we’ll make sure that:
- the URL directs people to your Metabase,
- your domain has SSL certificates set up to serve your instance over HTTPS to the new domain,
- and that your metabase.com/cloud/login works as expected.
You’ll still be able to access your original, automatically provisioned domain (e.g., yourcompany.metabaseapp.com), so existing embedded links should continue to work.
Why you’d want to use a custom domain
- White-labeling polish: If you’re white labeling Metabase, a custom domain adds another bit of polish that abstracts Metabase away from the experience you deliver to your customers.
- Consistency: you may have several internal tools that follow a pattern, e.g., crm.yourcompany.com, ops.yourcompany.com, etc., and you want something like stats.yourcompany.com for your Metabase.