The verdict in three sentences
For a software vendor in Amsterdam targeting 500 customers, a multi-tenant architecture costs 20 to 35% more to build but cuts hosting cost per customer by a factor of three. The right default in 2026 is a shared database with tenant ID isolation and Row Level Security, plus a dedicated database reserved for enterprise accounts. The two items you must never cut are data isolation and per-customer restore, because those are what fail security audits.
The three isolation models and their real cost
A B2B SaaS can house its customers in three ways. Each model shifts cost, either to initial development or to monthly operations.
| Criterion | Shared database (tenant_id) | Schema per customer | Dedicated database per customer |
|---|---|---|---|
| Extra initial development cost | +20 to 25% | +25 to 30% | +10 to 15% (but heavy deployment tooling) |
| Hosting per customer per month | EUR 5 to 12 | EUR 10 to 20 | EUR 25 to 40 |
| Comfortable number of customers | 500 to 10,000 | 100 to 1,000 | 10 to 200 |
| Schema migration time (500 customers) | 1 operation, a few minutes | 500 operations, 1 to 3 h | 500 operations, 3 to 8 h |
| Cross-customer leak risk | Medium without RLS, low with RLS | Low | Very low |
| Restoring a single customer | Complex, targeted export | Simple | Very simple |
| Enterprise sales argument | Weak | Fair | Strong |
For a vendor starting at 50 SMB customers and aiming for 500, the hybrid model pays best: shared database for 95% of customers, dedicated database sold as an option to the 5% that require contractual isolation (banks, healthcare, public sector).
Build and run budget, 2026 order of magnitude
The multi-tenant premium does not sit in a single line. It spreads across authentication, subscription management, backups and observability. Here is an estimate for a mid-complexity business platform built by a European team.
| Item | Single-tenant (one instance per customer) | Well-designed multi-tenant |
|---|---|---|
| Application core (business MVP) | EUR 60,000 to 90,000 | EUR 60,000 to 90,000 |
| Tenant management, roles, invitations | EUR 0 (duplicated by hand) | EUR 8,000 to 15,000 |
| Data isolation (RLS, automated tests) | EUR 2,000 | EUR 6,000 to 12,000 |
| Subscription billing and quotas | EUR 4,000 | EUR 7,000 to 12,000 |
| Backups and per-customer restore | EUR 2,000 | EUR 5,000 to 9,000 |
| Total build cost | EUR 68,000 to 98,000 | EUR 86,000 to 138,000 |
| Hosting at 500 customers per month | EUR 12,500 to 20,000 | EUR 2,500 to 6,000 |
The initial premium of EUR 18,000 to 40,000 pays back in two to four months of operations once the base exceeds 300 customers. Below 30 customers, one instance per customer remains defensible, especially if each customer pays more than EUR 1,500 per month.
The technical points that make the difference
- Row Level Security on PostgreSQL: the isolation rule lives in the database, not only in code. A forgotten filter can no longer return another customer's data.
- Automated isolation tests: every deployment checks that a tenant A user reads nothing from tenant B. Allow 3 to 5 days to set up.
- Per-tenant quotas: a customer importing 2 million rows must not slow down the other 499. Request limits and separate processing queues.
- Point-in-time backups with a documented procedure to restore a single customer in under 4 h, a frequent requirement in security questionnaires.
- EU hosting for GDPR, with a data processing agreement (Article 28) ready to sign.
Mini case study
Thomas, CTO of an Amsterdam vendor of practice management software for accounting firms, currently serves 50 customers on 50 separate instances at EUR 32 per month each, or EUR 1,600 monthly. His sales plan targets 500 customers by 2028. Keeping the current model, the hosting bill would climb to EUR 16,000 per month, not counting about 6 h of maintenance per release.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
He opts for a multi-tenant rebuild at EUR 32,000 (tenant management, RLS, per-customer backups). At 500 customers, hosting drops to about EUR 8 per customer, or EUR 4,000 per month. Monthly saving at full load: EUR 12,000. Even at 150 customers, the saving reaches EUR 3,600 per month: the project pays back in under nine months, and releases go from half a day to a few minutes.
FAQ
Is multi-tenancy compatible with enterprise security requirements?
Yes, provided you combine RLS, encryption at rest and automated isolation tests. For the 5% of customers who demand a dedicated database, offer it as an option billed EUR 150 to 400 extra per month.
From how many customers does multi-tenancy pay off?
As a 2026 order of magnitude, break-even sits between 40 and 80 customers for a premium of EUR 20,000 to 40,000. Beyond 300 customers, the single-instance model becomes very hard to operate.
Can an existing single-tenant platform be migrated to multi-tenant?
Yes, in 8 to 14 weeks for a mid-sized application. Migration happens customer by customer, with a 2 to 4 week parallel-run phase to limit risk.
Which host should a European vendor choose?
A European cloud (OVHcloud, Scaleway, or an EU region of AWS or GCP) covers most GDPR requirements. Budget EUR 300 to 1,500 per month for the infrastructure of a platform serving 100 to 500 SMB customers.
How long does it take to restore a single customer's data?
With a tooled procedure, 1 to 4 h on a shared database and under 1 h on a dedicated one. Without tooling, it can take a full day and block the team.
Let's scope your project. Send us your current customer count, your three-year target and your security constraints: we will price the architecture, the build budget and the hosting cost per customer. 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.
