Skip to main content
Multi-tenant architecture lets you manage multiple independent chatbots from a parent account.
Child bots are available from Builder up (multi_bot). The white-label agency console (white_label + multi_tenant) is Agency and Enterprise.

Concept

Each child tenant is completely independent:
  • Separate corpus
  • Separate conversations
  • Distinct settings
  • Consolidated billing on parent

Use cases

Digital agency

Manage all your clients’ chatbots from a single dashboard.

Franchise

Each franchisee has their personalized chatbot, you keep central control.

Multi-brand

A company with multiple brands, each with its own chatbot.

B2B SaaS

Offer a chatbot to each of your enterprise clients.

Creating a Child Tenant

Via the Dashboard

  1. Dashboard > Tenants > Create tenant
  2. Fill in:
    • Unique slug (client-x)
    • Display name
    • Plan (inherited or specific)
  3. Save

Via the API

Access management

Parent administrator

Full access to all child tenants:
  • View/modify corpus
  • View conversations
  • Modify settings
  • Create/delete tenants

Child administrator

Limited access to their tenant:
  • Manage their corpus
  • View their conversations
  • Modify their settings
  • No access to other tenants

Client access

A child tenant has its own API key, and the white-label embed (/embed/:slug/*, Agency) gives your client a scoped console for corpus, settings and personality — see White label.

Multi-Tenant API

List child tenants

Access a child tenant

Use the child’s slug:

Tenant-scoped token

Create tokens limited to a child tenant:

Billing

Consolidated (default)

All child tenants billed to parent account:
  • Single invoice
  • Total volume = sum of children
  • Volume discounts available

Rebilling your clients

Animam bills the parent account only. Rebilling your clients is your invoice to them — there is no per-child billing or Stripe Connect integration today.

Limits by plan

Each bot carries its own allocation of 600 conversations a month (20 a day), pooled across the fleet — a quiet bot covers a busy one. Buying an extra bot raises the pool by the same 600.

Best practices

Slug naming

Use a consistent prefix:

Environment separation

Monitoring

Monitor metrics per tenant:

Reusable tools across the fleet

To define a tool once and deploy it to every client bot, use fleet tools (Agency): a template on the parent is materialised on children, with {{tenant.slug}} resolved per client. Drivable over MCP (list_fleet_tools, create_fleet_tool, propagate_fleet_tool).

Support

For Enterprise multi-tenant questions: