Customizing your workspace's URL

Edited

A new Opendatasoft workspace has a default URL in the form <workspacename>.opendatasoft.com.

To improve discoverability, branding, or access, you can request additional custom URLs. These options aren’t managed in the back office. To set them up, contact support with the information described below.

Configuring custom DNS aliases

You can customize the base URL of your Opendatasoft workspace using a custom hostname under a DNS you control. For instance, if your workspace is named "example", its default URL is "example.opendatasoft.com", but you might prefer to use "data.example.com".

To set this up, follow these steps:

  1. Create a CNAME DNS record for your desired alias pointing to the default workspace hostname.

data.example.com IN CNAME example.opendatasoft.com

Important! Omitting the trailing dot may result in a relative DNS entry. Consult your DNS provider’s documentation for guidance.

  1. Register the new alias in your Opendatasoft workspace via the support form in the back office.

You can add multiple aliases—any of them can be used to access the workspace, though the first alias added will be used by default in URLs generated externally (e.g., in emails). Note that login sessions are specific to each alias, so users authenticated under one alias may appear anonymous under another.

Use of web redirects is not equivalent to a CNAME and cannot be used for this customization. A or AAAA records are also not supported, since workspace IPs may change. 

Subject Alternate Names must also be declared in the ACME certificate if there are multiple domains attached to one certificate (eg. a principal "foo.example.com" with a secondary "www.foo.example.com").

HTTPS and TLS (SSL) certificates

Opendatasoft enforces the use of HTTPS. If you configure a custom alias (e.g. "data.example.com"), Opendatasoft will automatically generate and renew the required TLS certificate using Let’s Encrypt—no manual action required. These certificates are domain‑validated, free of charge, and renew every three months, ensuring continuous security. 

Using your own certificate via ACME  (license‑dependent)

If your license supports the “Custom SSL Certificate” option with ACME automation, you now have the ability to manage your own certificate lifecycle using the ACME protocol (Automatic Certificate Management Environment)—a widely recognized industry standard for automating certificate issuance and renewal.

Why use ACME?

  • ACME enables fully automated issuance, validation, and renewal of SSL certificates—no manual steps required

  • It aligns with ever‑stricter browser requirements for certificate lifetimes

  • Opendatasoft initiates renewal when two-thirds of the certificate’s validity period has elapsed, in accordance with industry best practices, ensuring uninterrupted service and compliance with current security standards

How to enable ACME automation

To enable this functionality, simply provide Opendatasoft with:

  • The URL of your ACME server (from your certificate provider)

  • A KEY_IDENTIFIER (identifier)

  • A HMAC_KEY (secret key)

Validation of the certificate is performed over HTTP.

Many certificate authorities—such as Certigna or Digicert—support ACME.

Important notes

  • This option is only available if included in your Opendatasoft license or plan.

  • To enable this feature or receive assistance with transitioning, contact your customer success manager or our support team.

Summary of options

Option

Description

Automation

License required

Let’s Encrypt (default)

Automatically generated TLS certificate via Let’s Encrypt

Yes

Included in all plans

Custom certificate via ACME

Fully automated solution using your own ACME-compatible certificate provider

Yes

Requires specific license add-on

Handling multiple languages

If you have multiple languages in your workspace and use language-specific aliases, you can request each alias to be linked to a specific language.

For instance, if there are two aliases, "data.example.co.uk" and "daten.example.de," you can ensure that users accessing the workspace through the first alias will be served English content, and those accessing the workspace through the second alias be served German content. Naturally, users can still switch languages on their own as usual.

To set up specific language handling, contact your customer success manager or our support team.