Zango
· Platform Architecture

Actors at the top, a shared platform core in the middle, and the storage substrate at the bottom.

v1.1.0
© Healthlane Technologies
Actors
Who Zango serves
Builders
Build apps, modules, workflows, and AI agents.
Product Managers Developers
Administrators
Manage tenants, users, roles, and policies.
Product Managers Tenant Admins Platform Ops
App Users
Use the deployed pharma applications day-to-day.
HCPs · Patients Ops & Compliance
Platform
Apps & APIs
Tenant-built applications and developer surfaces
App Panel
Studio & admin console
App 1
Modules & packages
App 2
Modules & packages
App 3
Modules & packages
App n
Scale horizontally
Zango Core
Tenancy, roles, policies, tasks & packages — every app inherits these automatically
Tenancy
Management
User Roles
Policy &
Permissions
Task
Management
Packages
Management
Enterprise
Features
AI Layer

A first-class intelligence tier

Surfaced via Agent Studio
Configuration Tenant-scoped models
Shaped in the Studio — versioned, audited, no-code.
LLM Providers
Agents
Prompts
Tools
Guardrails
Runtime Framework engine
What apps invoke via zango.ai.
Provider Client
Agent Executor
Tool Executor
Memory / Sessions
Cost & Budget
Invocation Logs
Tenant-scoped · encrypted secrets · rate-limited · fully observable
from zango.ai import get_agent
Core Frameworks
Django · React · Celery — the runtime Zango is built on
React
Django
Celery
Async tasks · agent execution · schedules
Persistence & object storage
Redis cache · queue
Azure Blob objects
AWS S3 objects
Google Cloud storage