The verdict in three sentences
Multi-tenant remains the default architecture for B2B SaaS in 2026: 3 to 15 EUR of infrastructure per customer per month, versus 80 to 400 EUR for a dedicated instance. Yet enterprise customers (banks, insurers, public sector) increasingly demand strong isolation and contractual data residency, which pushes Amsterdam vendors towards a hybrid model. The right call is a multi-tenant design able to move a customer onto a dedicated database or instance, at an upfront development premium of 15 to 30%.
Three isolation levels, three cost structures
"Multi-tenant" covers several technical realities. The CTO must pick the isolation level before the first enterprise contracts, because switching models later often costs more than the original build.
| Model | Infra cost per customer per month | Isolation | Operational complexity | Typical profile |
|---|---|---|---|---|
| Multi-tenant, shared database (tenant_id column) | 3 to 8 EUR | Logical (RLS) | Low | SMBs, freemium |
| Multi-tenant, schema per customer | 5 to 15 EUR | Reinforced logical | Medium | Mid-market, 50 to 500 customers |
| Dedicated database per customer | 30 to 120 EUR | Physical (data) | Medium to high | Regulated customers |
| Dedicated application instance | 80 to 250 EUR | Complete | High | Banks, insurers |
| Dedicated instance in the customer's cloud | 150 to 400 EUR (recharged) | Total, sovereignty | Very high | Public sector, defence |
These figures cover compute, database, backups and monitoring, as a 2026 order of magnitude on a European cloud. They exclude human operating time, which is where the real difference lies.
The hidden cost: operations and updates
With 100 multi-tenant customers, an update ships once. With 100 dedicated instances, you need 100 deployments, 100 database migrations and 100 monitoring endpoints. Without serious automation (infrastructure as code, per-tenant pipelines), operating time explodes.
| Item (100 customers, annual) | Shared multi-tenant | Schema per customer | Dedicated instances |
|---|---|---|---|
| Infrastructure | 6,000 to 9,600 EUR | 6,000 to 18,000 EUR | 96,000 to 300,000 EUR |
| Operations time (DevOps) | 0.2 FTE | 0.3 FTE | 1 to 1.5 FTE |
| Duration of a global deployment | 10 to 20 min | 30 to 60 min | 1 to 3 days |
| Upfront development premium | Baseline | +10 to 15% | +15 to 30% |
| Realistic minimum selling price | 50 EUR per month | 200 EUR per month | 1,500 EUR per month |
| Portability (full export) | Must be built | Simple per schema | Native |
The conclusion is financial: a dedicated instance only pays off when sold as a premium option, typically charged 1,000 to 3,000 EUR more per month.
What enterprise customers really require
Procurement and security teams at Dutch banks and insurers ask precise questions in their questionnaires. Few demand a dedicated instance on principle; most want verifiable guarantees.
- Data residency: hosting in the EU, sometimes with a sovereign cloud provider for public sector work.
- Encryption at rest with customer-owned keys (BYOK), achievable in multi-tenant with a dedicated database.
- Portability: full export within 30 days at most, in a documented format.
- Penetration tests every year, shared under NDA.
- DORA compliance for financial customers, which requires an assessment of critical ICT providers.
A "schema per customer with a dedicated-database option" architecture meets roughly 80% of these requirements without multiplying instances.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Thomas, CTO of a compliance software vendor in Amsterdam (illustrative persona), has 60 SMB customers and is negotiating with two banks that demand data isolation. Option A: dedicated instances for everyone, 60 x 150 EUR = 9,000 EUR a month of infrastructure, plus 1 DevOps FTE. Option B: schema per customer for the 60 SMBs (60 x 10 EUR = 600 EUR) and a dedicated database for the two banks (2 x 100 EUR = 200 EUR), or 800 EUR a month. Option B's extra development cost: 18,000 EUR, recovered in two months compared with option A. Each bank pays an isolation option of 1,500 EUR a month, or 36,000 EUR of additional annual revenue.
FAQ
How much does one multi-tenant SaaS customer cost in 2026?
Between 3 and 15 EUR of infrastructure a month depending on isolation level and data volume. That is 10 to 30 times less than a dedicated instance.
Is multi-tenant GDPR compliant?
Yes, GDPR does not require physical isolation. It requires appropriate security measures, reliable logical separation (Row Level Security, for instance) and a data processing agreement.
When does a dedicated instance become unavoidable?
When the customer requires it contractually, often in banking, insurance or the public sector. It should then be billed as an option, typically 1,000 to 3,000 EUR more per month.
Can you move from multi-tenant to a dedicated instance later?
Yes if the architecture planned for it from the start, for a 15 to 30% upfront premium. Without that preparation, the migration can cost 30,000 to 80,000 EUR.
Schema or database isolation?
Schemas are enough up to a few hundred customers and cost 5 to 15 EUR per customer. A dedicated database, at 30 to 120 EUR a month, is for regulated customers.
Let's scope your project. Tell us your customer count, isolation requirements and data residency constraints: we will propose the architecture, its monthly infrastructure cost and the rollout schedule. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
