What is multi-tenancy?
One system, many “tenants” — branches, brands, clients — with full data isolation. We explain it in plain terms: what it means, who it makes sense for and how it works in Open Mercato.
The definition in one sentence
Multi-tenancy is an architecture in which a single instance of the system serves many tenants — separate companies, branches or clients — on shared code and infrastructure, but with isolated data. Each tenant sees only its own data and can have its own configuration.
Analogy
Think of an apartment building: a shared structure, utilities and entrance, but every flat has its own key and private space. It's the same with a tenant in Open Mercato — a shared engine, private data.
When is multi-tenancy useful?
Multiple branches or locations
One company with several branches — a shared system, but each branch sees its own data and has its own settings.
Franchise networks
Headquarters and franchisees in one system: shared standards, separate data and accounting for every location.
Holding groups / several companies
Several companies under one technology roof — separate books and processes, shared oversight.
Agencies serving many clients
A single panel to serve many clients at once, each in its own, isolated space.
B2B portals and platforms
Many partners in one portal — individual price lists and data, a shared engine.
How multi-tenancy works in Open Mercato
Per-tenant data isolation
Every tenant sees only its own data. Queries are automatically scoped to its space — no one can peek at anyone else's.
Shared code and modules
All tenants run on the same codebase. A single update or fix reaches everyone at once — without copying the system N times.
Per-tenant roles and permissions
Permissions (RBAC) are set separately in each tenant — one way for headquarters, another for a branch or client.
Per-tenant configuration
Price lists, branding, settings and integrations can differ between tenants — despite the shared engine.
One hosting, lower cost
You maintain a single instance instead of many copies — less hosting, fewer updates and less administrative work.
Benefits
Lower cost of ownership (TCO)
One system instead of many separate installations — less hosting and maintenance.
Consistent updates
A new feature or security fix reaches all tenants at once.
Isolation and security
Every tenant's data is kept separate — also with GDPR in mind.
Fast scaling
A new branch, company or client is simply a new tenant — no need to stand up the system from scratch.
Per-tenant customization
A shared engine, but each has its own price lists, branding and settings.
Shared oversight
Headquarters sees the whole picture (with the right permissions), tenants — only their own.
Multi-tenant vs separate instances
| Multi-tenant (Open Mercato) | Separate instances | |
|---|---|---|
| Number of instances | One, shared | One per client |
| Maintenance cost | Lower — single hosting | Grows with every copy |
| Updates | Once, for everyone | Separately in each instance |
| Data isolation | Logical, per tenant | Physical, per instance |
| New branch/client | Fast — a new tenant | A fresh deployment |
| Customization | Per tenant, within the system's limits | Full, but costly to maintain |
Note: with very high isolation requirements (e.g. a regulated sector), separate instances are sometimes the better choice — we'll advise what fits your case.
Security and GDPR
Every tenant's data is logically separated, encrypted in transit and at rest, and hosting is in the EU — which supports GDPR compliance. Because Open Mercato is open source (MIT license), you can commission your own isolation and security audit. Learn more: github.com/open-mercato/open-mercato.
Frequently asked questions
Is the data of different branches or clients kept separate?+
Yes. In multi-tenancy each tenant has a logically isolated space — queries are automatically scoped to its data, so one tenant cannot see another's.
Can each tenant have its own price list and branding?+
Yes. Despite the shared code, the configuration (price lists, logos, settings, integrations) can differ for each tenant.
How does multi-tenancy differ from separate instances for everyone?+
With separate instances you maintain and update many copies of the system — pricier and slower. Multi-tenancy is a single instance with data isolation: cheaper to maintain and easier to update, while keeping data private.
Is it secure and GDPR-compliant?+
Yes. Per-tenant data isolation, encryption and EU hosting support GDPR compliance. Because Open Mercato is open source, you can also commission your own security audit.
Can I add a new branch or client later?+
Yes — that's one of the main advantages. You add another tenant to the existing system, without building everything from scratch.
Do you have many branches, brands or clients?
We'll show you how multi-tenancy in Open Mercato ties it all into one system — with data isolation and a lower cost of ownership.