Multi-tenant
Why this feature?
I want to support multi-tenancy with data isolation, allowing an employee to belong to multiple enterprises while displaying the respective chat records for each enterprise separately.
Key Reasons to Support Multi-Tenancy
- Scalability & Cost Efficiency A single instance of the software can serve multiple organizations (tenants), reducing infrastructure costs.
Better resource utilization (CPU, memory, database) compared to single-tenant deployments.
- Easier Maintenance & Updates Updates and bug fixes apply to all tenants at once, reducing maintenance overhead.
No need to manage separate deployments for each organization.
- Broader Adoption & SaaS Compatibility Makes the project more attractive for cloud/SaaS providers who need to serve multiple customers.
Enables hosted versions of the software (e.g., like GitLab, Nextcloud).
- Data Isolation & Security Ensures tenant data remains segregated, preventing leaks or unauthorized access.
Critical for compliance (GDPR, HIPAA) in regulated industries.
- Customization Without Fragmentation Tenants can have custom configurations (themes, settings, plugins) without needing separate forks.
Reduces codebase fragmentation compared to single-tenant forks.
- Monetization Potential Enables freemium models (free tier + paid upgrades).
Cloud providers can offer managed multi-tenant hosting as a service.
Suggested Solution
Logical data isolation and Tenant fields
Additional Information
No response
Hello! Thank you for filing an issue.
If this is a bug report, please include relevant logs to help us debug the problem.
Join slack 🤖 to connect and communicate with our developers.
The multi-tenant feature obviously has many benefits. Unfortunately, we don't plan to develop this in the open-source version.