Skip to content

[Implementation Guide] Multi-Tenant Deployment & Budget Separation #426

@nurkmez2

Description

@nurkmez2

Template version: v1.0 (from first slide – bottom left)

Slide number(s): Deployment, Architecture

Detail your feedback and suggestions:

Thank you for the great implementation guide, it is very helpful.

I have two questions related to a common multi-tenant use case:

  1. Deployment across tenants
    If we develop an agent (including child agents, tools, and connections) in the Test Environment of Tenant-A, is there a recommended approach to deploy this agent into the Production Environment of Tenant-B?
    If yes, what is the supported pattern?

  2. Budget / cost separation per department within the same tenant
    In the same tenant (Tenant-A), there may be separate departments (HR, Finance, Logistics, etc.) with independent budgets.
    What is the recommended approach to separate costs per agent?

  • Should each department have its own environment (e.g., HR-Environment, Finance-Environment)?
  • If so, what is the recommended deployment model from Dev → these environments?

Any guidance or documentation would be appreciated.

Thank you very much!

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions