Tenant and Environments

In Agile Data Engine, a tenant is a customer-specific, dedicated instance of the platform. Each tenant has a unique ID (e.g., s1234567) and includes its own configuration, Designer, and Runtime environments.

ADE includes both tenant-specific and multi-tenant services:

Tenant-specific services: e.g. Designer, Runtime environments
Multi-tenant services: e.g. External API, Admin UI, Insights

Contact us to request a new Agile Data Engine tenant. In case you need help with your existing tenants, send a request in our support portal.

Tenant service URLs

ADE tenant service URLs are constructed using the following attributes:

Attribute

Examples

Description

tenant_id

s1234567

Unique identifier assigned to your ADE tenant.

service_name

datahub

Name of the ADE service.

Default is datahub, but this can be customized when a new tenant is created.

environment_name

design, dev, prod

Name of the environment.

Each tenant includes one Designer environment called design, and any number of Runtime environments (e.g., dev, test, prod).

Runtime names must be 2–8 characters long.

The URL pattern is:

CODE

https://external[-api].<environment_name>.<service_name>.<tenant_id>.saas.agiledataengine.com

Example service URLs:

Designer:
https://external.design.datahub.s1234567.saas.agiledataengine.com/modeler/
DEV Workflow Orchestration:
https://external.dev.datahub.s1234567.saas.agiledataengine.com/dagger/
DEV Notify API:
https://external-api.dev.datahub.s1234567.saas.agiledataengine.com/notify-api

Runtime settings

ADE tenants can have multiple Runtime environments. Runtime environments are used to separate workloads e.g. between development, testing and production.

Runtime size

Each Runtime environment is assigned a runtime size, which determines the maximum level of parallelism for active task execution within that environment. Runtime size directly impacts:

Execution capacity (number of concurrent tasks)
Platform pricing

For details on available sizes and how they affect execution, see Pools.

Deployment settings

Deployment settings define how changes made in the Designer are promoted and deployed to Runtime environments. These settings are configured when creating a new tenant or adding environments to an existing tenant, and can be modified later in the Admin UI.

Example setup with three Runtime environments:

Runtime	Automatic promotion	Automatic deploy	On error continue deploy
DEV	true	true	true
TEST	false	false	false
PROD	false	false	false

AUTOMATIC PROMOTION: Automatically promotes commits from the Designer to this Runtime environment.
AUTOMATIC DEPLOY: Automatically deploys promoted content to the environment.
ON ERROR CONTINUE DEPLOY: Allows deployment to proceed even if errors are encountered.

These settings help define the release process and level of automation per environment.

For further details, see Deployment settings.

Target database instances

Target database instances define database connection configurations within ADE Runtime environments.

You can configure multiple target instances per Runtime environment, though typically only one is used per environment.
Each target instance includes connection details such as host, port, database name and authentication credentials.

For setup instructions and supported platforms, see Target Database Setup.