# Provision agents, teams, and workflows on demand for multi-tenant systems

> AgentFactory, TeamFactory, and WorkflowFactory let you create agents, teams, and workflows dynamically at runtime instead of defining them statically at startup.

- Published: 2026-04-23
- Author: Agno Team
- Category: Changelog
- Canonical: https://agno-com-nine.vercel.app/articles/provision-agents-teams-and-workflows-on-demand-for-multi-tenant-systems
- Markdown: https://agno-com-nine.vercel.app/articles/provision-agents-teams-and-workflows-on-demand-for-multi-tenant-systems.md

`AgentFactory`, `TeamFactory`, and `WorkflowFactory` let you create agents, teams, and workflows dynamically at runtime instead of defining them statically at startup. Each request can spin up its own configuration, drawing on per-tenant settings, runtime context, or user-specific permissions.

For platform teams running shared infrastructure across customers, departments, or business units, this removes a structural limitation. You no longer need a separate process or deployment to isolate configurations between tenants. One AgentOS instance can serve many distinct contexts with appropriate boundaries.

The factory pattern also makes A/B testing, gradual rollouts, and per-environment customization straightforward, since the agent definition is decided when the request arrives rather than baked into the deployment.

Learn more about [Dynamic Agents](https://docs.agno.com/agent-os/factories/overview) in our docs.