Services
Odoo Multi-Tenant Deployment
Multi-tenancy is Odoo at platform scale: many isolated businesses served from shared, standardised infrastructure. It’s the architecture behind our largest proof point, our platform for Insight Technologies SAS, a digital payment provider serving over 150 merchants from a heavily customised multi-tenant Odoo 13 Community platform, and it’s a discipline very few partners have genuinely operated.
If you’re a SaaS operator, franchise group or platform business considering Odoo as your per-customer backend, this is that service.
What the work involves
- Tenant isolation architecture. Database-per-tenant or schema-level strategies chosen against your isolation, compliance and cost requirements, with the trade-offs made explicit.
- Automated provisioning. New tenant creation as a pipeline (database, configuration baseline, branding, users) in minutes, because manual tenant setup kills platform economics.
- Fleet-wide upgrades. Standardised module sets and staged rollout tooling so a fix or feature reaches 150 tenants safely, not 150 times manually. This is where multi-tenant operations live or die.
- Per-tenant customisation limits. A deliberate policy layer defining what tenants can vary, protecting the fleet’s upgradability from death by special cases.
- Operational tooling. Monitoring, backup and health dashboards at fleet level, sized from real production experience at 150+ merchants. See the case study.
How we work as your operations partner
- System audit first. Whether or not we built your system, we start by documenting what we’re taking responsibility for. The audit report is yours regardless.
- SLAs in writing. Response and resolution targets by severity, agreed before the retainer starts, so a production-down issue is treated like one.
- Onboarding and monitoring. Integration health, scheduled jobs and error queues wired into our monitoring, so we often see issues before your team reports them.
- A monthly rhythm. Small changes handled inside the retainer, a report of what was done and what it cost in hours, no surprises.
- Quarterly review. Usage against the retainer honestly discussed, upgrade posture assessed, and the plan adjusted. Senior eyes stay on your system permanently.
Common questions
What scale does this make sense at?
The automation investment pays from roughly a dozen tenants and becomes mandatory beyond fifty. Below that, well-run separate instances may be simpler; we'll do that maths with you.
How do upgrades work across a fleet?
Canary tenants first, automated test suites, staged waves with rollback points. The methodology exists because we've run it in production, not read about it.
Can tenants have their own integrations?
Within the policy layer, yes. The art is offering configurable integration options without forking the codebase per tenant.
What does per-tenant cost look like at scale?
It falls sharply with automation: infrastructure is shared, provisioning is minutes, and upgrades run fleet-wide. The economics are the reason to do this properly; we'll model yours from real operating numbers.
How is tenant data kept separate for compliance?
Database-per-tenant isolation means each tenant's data is physically separate, individually backupable and individually erasable, which keeps GDPR conversations short.
Not sure where to start? Book a free discovery call and we’ll map your current setup, or request a free Odoo health check if you’re already running Odoo.