Tenant Architecture #

A tenant is a logical workload namespace representing an application or service domain.

What is a Tenant? #

Tenants are the workload layer that runs within sites, on top of substrate infrastructure:

graph TB
    subgraph tenants["Tenants (Workloads)"]
        T["grooveiq, vintronics, moneyrouter, etc."]
    end
    subgraph substrate["Substrate Infrastructure"]
        S["Network, Compute, Management Plane"]
    end
    tenants -->|deployed on| substrate

Examples of tenants: grooveiq, vintronics, moneyrouter

Key Properties #

Tenants Live Within Sites #

Tenants:

Run within sites, not defining them
May be deployed to one or more sites
Are isolated from other tenants
Share substrate infrastructure (network, compute, management)

Intent Over Identity #

Tenants express intent (what’s running), not identity (what the host is):

A host has stable identity (hostname, MAC, IP)
A tenant workload can move between hosts
Services are addressed by DNS, not by host

DNS Naming Pattern #

Tenant services follow a hierarchical DNS pattern:

service.tenant.site.deevnet.net

Example: api.grooveiq.dvntm.deevnet.net

api — the service
grooveiq — the tenant
dvntm — the site
deevnet.net — the domain

Tenant vs Site #

Aspect	Site	Tenant
Purpose	Infrastructure boundary	Workload namespace
Contains	Network, compute, management	Applications, services
Lifetime	Long-lived, stable	May be created/destroyed frequently
Provisioning	Automation-first	Terraform-first
Example	`dvntm`, `dvnt`	`grooveiq`, `vintronics`

Multi-Site Tenants #

A tenant may be deployed to multiple sites:

api.grooveiq.dvntm.deevnet.net  — Development instance
api.grooveiq.dvnt.deevnet.net   — Production instance

The tenant is logically the same (grooveiq), but instances are site-scoped.

Child Documents #

Networking — Tenant network isolation and VLAN model
Management — Tenant lifecycle and observability
Building — Tenant provisioning