Multi-Tenant Chatbot Platform — One Installation, Many Tenants
Zentor App is designed from the ground up as a multi-tenant platform. A single installation can serve many independent tenants — with full data isolation, its own chatbot, and its own channels for each customer. Ideal for agencies, resellers, and SaaS providers.
Imagine you’re a digital agency managing chatbot solutions for various clients. Without multi-tenancy, you would need to run a separate platform instance for each client — with its own server, its own maintenance, its own updates. That’s costly, labor-intensive, and hard to scale.
Multi-tenancy solves this problem: a single Zentor App installation serves all your clients simultaneously — fully isolated from one another, each with its own configuration. You maintain one infrastructure, but offer each tenant its own individual chatbot environment.
This model is relevant for agencies and chatbot service providers, for SaaS companies that resell chatbot functionality as part of their offering, and for larger corporate groups that want to run multiple subsidiaries or brands on a shared platform.
Multi-tenancy is a software architecture principle in which a single application instance serves multiple independent user groups — so-called tenants — simultaneously. Each tenant is fully isolated from other tenants: it sees no data from other tenants, cannot influence other tenants’ configurations, and operates in its own self-contained area.
Shared use of infrastructure only affects the technical layer — servers, database engine, application logic. At the data level, each tenant is a completely separate area. For the end user, the platform feels like a dedicated installation — without the need to run separate hardware.
In Zentor App, each tenant is an independent, fully separated entity:
Each tenant can run its customer communication under its own visible identity. Depending on configuration, this includes its own name, logo, colors, slogan, contact details, links, as well as its own sender name and an explicitly assigned email address.
The technical infrastructure can be provided centrally by Zentor App. Communication toward end customers nonetheless remains clearly attributed to the respective tenant. A tenant uses only the branding and sender data released for it. Data, mailboxes, or visible identities of other tenants are never taken over.
Zentor App distinguishes two communication directions:
- Zentor App to a tenant: Contract, platform, security, package, and billing information is sent under Zentor App branding.
- Tenant to its end customers: Appointment, inquiry, callback, and service emails use the branding and assigned sender identity of the respective tenant.
This keeps it clearly identifiable who the functional sender of a message is.
Role-Based Access Control (RBAC) makes it possible to assign granular permissions to users within a tenant — depending on their role in the team. A customer service employee sees conversations and can reply. A team lead additionally sees reports and monitoring. An administrator configures channels and the knowledge base. A super admin manages the entire platform.
RBAC is available as an add-on module in the Custom plan and ensures that users can only access the data and functions required for their role. This corresponds to the principle of least privilege — an important principle of both the GDPR and general IT security.
For agencies managing multiple client tenants, RBAC also means: a client’s employees have no access to another tenant’s data — even when technically working on the same platform.
Zentor App connects the management of offers, packages, subscriptions, and access rights with integrated payment processing. Custom services are first compiled into an offer and approved by the customer. Only after that does the payment step follow.
The functional management of packages, prices, terms, approvals, and access rights takes place within Zentor App. PayPal is used for the supported payment processing. This keeps the offer, payment, contract status, and platform access traceably connected.
Agencies offering AI chatbots as a service often face the problem of having to build a separate technical environment for each client. This ties up resources and makes it harder to scale the business model.
With Zentor App as a multi-tenant platform, you manage all your clients from a central interface. Each client gets its own fully configured chatbot, its own knowledge base, and its own channels — while you, as the agency, retain oversight and control over all tenants.
Updates, new features, and security patches are applied once at the platform level and automatically benefit all tenants. This means less operational effort for you — and a consistent, up-to-date product for your clients.
Zentor App grows with your business. You start with a few tenants and a manageable infrastructure — and scale up as your customer base grows. The platform architecture is designed for growth from the start: new tenants can be added without changes to the infrastructure.
The Starter plan enables first steps with the chatbot for a website. The Custom plan freely expands to all six live-usable channels (web chat, email, WhatsApp, Telegram, SMS, telephony via the Zentor SIP-Voicebot), n8n workflows, RBAC, the calendar module, advanced automations, multiple process paths, additional tenants at €39/month each and 10 users included (expandable on request), as well as an on-premises option and SSO — the right foundation for agencies with a growing tenant base and higher inquiry volume.
Frequently Asked Questions About the Multi-Tenant Platform
What is a multi-tenant platform?+
A multi-tenant platform is a software architecture in which a single installation serves multiple independent customers (tenants) simultaneously. Each tenant has its own fully isolated area — with its own data, configurations, users, and channels. The underlying infrastructure is shared, without tenants being able to see or affect one another.
Are tenants isolated from one another?+
Yes, completely. Each tenant in Zentor App has its own knowledge base, its own chatbot, its own channels, and its own users. Data isolation is technically ensured: one tenant’s employee or chatbot has no access to another tenant’s data — not even accidentally.
How does billing per tenant work?+
Services, prices, terms, and billing models can be configured separately for each tenant. For individually assembled packages, Zentor App first creates a specific offer. After approval, supported payment processing via PayPal follows. Offer status, payment, contract status, and access rights are traceably linked within the platform. Tenants can therefore be managed independently of one another, without prices, contracts, or access of another tenant being carried over.
From which plan is multi-tenant available?+
The multi-tenant architecture is a fundamental feature of the Zentor App platform and is available in all plans. Advanced multi-tenant configuration options — such as RBAC, audit trail, advanced tenant management, and additional tenants at €39/month each — are available as add-on modules in the freely configurable Custom plan.
As an agency, can I manage different chatbot configurations per tenant?+
Yes. Each tenant receives its own chatbot configuration: its own knowledge base, its own channels (web chat domain, WhatsApp number, Telegram bot, etc.), its own conversation histories, and its own automation workflows. As an agency, you manage all tenants from a central interface, without configurations affecting one another.
Ready for Your Own Chatbot Platform?
Talk to us about how Zentor App as a multi-tenant platform can support your agency or SaaS model.
Further reading:
More in the Help Center