ESProfiler Handbook
Platform Ops

New Tenant Creation

Create a new ESProfiler tenant through the DSS UI and configure its initial dummy admin user.

What is DSS?

The Deployment Support Service (DSS) automates the setup of new ESProfiler customer tenants. It creates the organisation and initial administrator, sets up the tenant databases and credentials, deploys the tenant applications in AWS, and configures routing and DNS.

Use the DSS management UI to create a tenant and review the record of its creation. DSS calls these records Birth Records.

Before you start

Create or update an issue in the admin repository to record the tenant request and its owner. Have the following details ready:

  • The organisation name, a short description, and its primary email domain.
  • A unique tenant alias, which will form the hostname <alias>.own.esprofiler.com.
  • The AWS region and platform, iEngine, and frontend versions agreed for the deployment.

For example, an organisation called Example Corp might use the alias example-corp and primary domain example.com. Its tenant would be available at https://example-corp.own.esprofiler.com.

Create the tenant

1. Open the creation form

Open the DSS management UI and sign in with your authorised ESProfiler account. Select Birth in the navigation, then click Create Tenant.

2. Choose the deployment

In the Deployment section, select the Region first. DSS then loads the available Platform Version and iEngine Version values for that region and selects an initial value for each.

Set Frontend Version to the published frontend version agreed for this tenant, for example v4-2-0. This field is prefilled with the DSS default and can be changed for each new tenant. Enter the version directory name using letters, digits, dots, underscores, or dashes. Use the version name rather than a full URL or path.

The frontend version controls the UI served by the tenant and is separate from Platform Version, which selects the backend image. DSS checks the format but does not verify that the frontend version has been published, so confirm that it is available before creating the tenant.

Check all three version selections against the versions agreed for this tenant before continuing.

3. Enter the organisation details

Complete the Organisation section:

FieldWhat to enter
Organisation NameThe customer's name, for example Example Corp.
AliasA unique alias using lowercase letters, digits, and dashes, for example example-corp.
DescriptionA short description of the organisation; this field is required.
Primary DomainThe organisation's email domain, for example example.com, without https:// or an email address.
Forgot Password EnabledLeave enabled unless the tenant's setup specifies otherwise.
Clients PermittedLeave enabled unless the tenant's setup specifies otherwise.

Check the alias carefully: DSS uses it to name the tenant's hostname, databases, and deployment resources.

4. Create the initial dummy admin user

We initially create a dummy administrator using test@<domain>, where <domain> is the organisation's primary domain. Use the name test.

The form requires both a given name and a family name, so enter test in both fields:

FieldValue
Admin Emailtest@<domain>, for example test@example.com.
Admin Given Nametest
Admin Family Nametest
Send Onboarding EmailUnchecked for this initial dummy account.

This is the initial setup administrator. Record it in the admin issue, together with the customer administrator onboarding that still needs to be completed.

5. Confirm and create

Review the deployment, organisation, and admin details. Enter confirm in the Confirmation field to enable the Create button, then click Create.

DSS displays a progress indicator while provisioning the tenant. Wait for the Tenant created successfully. notification. The dialog closes and the Birth Records list refreshes when creation succeeds.

Check the result

Find the tenant in Birth Records and check that its Status is Successful. Click the record to review its Host, Region, Database, Completed On, and organisation details.

Open https://<alias>.own.esprofiler.com/bootstrap and confirm that the tenant responds. Record the tenant URL and creation result in the admin issue.

As part of the tenant setup, follow the existing guidance for adding an uptime monitor and classifying the tenant in PostHog.

If creation fails, reopen or refresh Birth, find the failed record, and review its Failure Reason. Add the failure details to the admin issue and investigate the resources already created before retrying. Tenant creation can leave a partially provisioned organisation and deployment; it does not automatically undo every completed step.

Copyright © 2026