Deploying for a Client (Tenant Provisioning)

Each client gets their own isolated DMOps.ai tenant — a dedicated application instance with its own database, agents, integrations, and users.

Prerequisites

• acpfleet.py installed and configured with your AWS credentials
• The client's AWS region confirmed (default: eu-central-1)
• A chosen tenant ID — short, lowercase, alphanumeric (e.g. acme, client01)

Provisioning a tenant

python acpfleet.py add <tenant_id> --tier 2

This creates:

• An ECS Fargate service for the DMOps API
• A dedicated PostgreSQL database on the shared Aurora cluster
• An S3 bucket for artefact storage
• A DNS entry on the shared ALB (<tenant_id>.app.dmops.ai)
• An initial admin user with a randomly generated password

The provisioning takes approximately 3–5 minutes.

Choosing a tier

Tier	Agents	Integrations	Recommended for
T1 — Entry	1–3	0–2	Demo / proof of concept
T2 — Light	3–6	2–4	Small team (< 20 users)
T3 — Standard	6–12	4–8	Mid-size deployment
T4 — Growth	12–24	8–16	Large team
T5 — Scale	24+	16+	Enterprise

Scaling a tenant

python acpfleet.py update <tenant_id> --tier 3

Downtime notice

Scaling triggers an ECS service replacement (~5 min downtime). Schedule with your client in advance.

Listing tenants

python acpfleet.py list

Checking tenant health

python acpfleet.py show <tenant_id>

Also check the tenant's /api/ping and /api/stats endpoints for live health.

Decommissioning a tenant

Never delete environments

Per our hard guardrail policy, tenant environments are never destroyed. Contact Dynamics Mobile if a client needs to be offboarded — we archive the tenant, preserve the data, and cease billing.