Deployment & Multi-Tenancy
How Enterprise AI is hosted and secured: tenancy model, real-time sync, access control and integrations.
Tenancy model
Enterprise AI runs as SaaS with database-per-tenant isolation: your company's data lives in its own database, reached through your own tenant subdomain. The platform auto-scales with load, and self-hosted Docker deployment is available when data must stay on your own infrastructure.
Database per tenant
Hard isolation — no shared tables, no cross-tenant queries, simpler compliance.
Tenant subdomains
Your team signs in at your own subdomain with your branding.
Auto-scaling
Capacity grows with usage; month-end and seasonal peaks need no planning on your side.
Docker self-hosting
Run the full stack on your own servers with the provided Docker setup.
Real-time sync across branches
Multi-branch businesses stay consistent through Kafka-based real-time synchronization: a sale, stock movement or price change in one branch or location propagates to the others within moments, including back-office dashboards.
POS terminals combine this with offline mode — a branch that loses connectivity keeps trading locally and re-syncs through the same pipeline when it reconnects.
Security and access control
Access is governed by role-based access control, refined by data access policies that limit which records a role can see, and approval limits that cap what each person can authorize. API tokens grant scoped programmatic access, and audit logging records every significant action.
| Control | What it governs |
|---|---|
| RBAC roles | Which modules and actions each user can use |
| Data access policies | Which records a role can see, e.g. own branch only |
| Approval limits | Maximum document values a user may approve |
| API tokens | Scoped, revocable access for integrations |
| Audit logging | A tamper-evident record of who did what, when |
Integrations and notifications
Webhooks push events to your other systems as they happen, Stripe handles online and terminal payments, and SMS and email notifications keep customers and staff informed of orders, approvals and alerts.
Create a dedicated API token per integration and scope it to the minimum required permissions — revoking one integration then never affects another.