Multi-tenant SaaS architecture cost in Dublin (2026)

The verdict in three sentences

For a B2B SaaS moving from SMBs to enterprise accounts, the right target is almost always a hybrid model: a shared schema with Row Level Security for most customers, and a dedicated database sold as an option to the accounts that contractually require it. This adds 15 to 25 % to the development budget instead of the 40 % of database-per-tenant for everyone. The real hidden cost sits in migrations and operations, not in the initial code.

The case below comes from a Casablanca HR SaaS, with figures in MAD (1 EUR is roughly 11 MAD); the same ratios apply to a Dublin team working with a nearshore agency.

The three isolation models compared

Multi-tenant means a single application serving several customer companies (tenants). The question an enterprise CIO asks is simple: "can my payroll data leak to another customer?". The answer depends on the model you pick.

With PostgreSQL, a shared schema relies on a tenant_id column in every table and RLS policies that stop any query from reading another customer's row, even if the application has a bug. It is serious and auditable, but a bank CISO often prefers to hear "your database belongs to you".

What each option really costs over 3 years

Take an HR SaaS built with an agency on a core budget of 1,200,000 MAD (about 110,000 EUR). The table estimates the full 3-year cost for 200 customers, 8 of them enterprise accounts.

Hybrid costs more than shared, but it pays for itself through a "dedicated isolation" option billed at 3,000 to 6,000 MAD (270 to 545 EUR) per month to enterprise accounts. Database-per-tenant for everyone destroys margin as soon as you pass about a hundred small customers.

Security, compliance and contract

In Morocco, law 09-08 and the CNDP regulate personal data processing; in Ireland the GDPR and the Data Protection Commission play that role. Employee payroll or health data is sensitive either way. An enterprise account will typically ask for: encryption at rest (AES-256), separate keys per tenant for dedicated databases, access logs kept for 12 months, an annual penetration test (40,000 to 90,000 MAD), local or EU hosting, and a reversibility clause with a full export within 30 days.

The isolation model must be decided before the first sprint: moving from shared schema to database-per-tenant after 18 months usually costs 2 to 3 times more than planning for it, because every query, job and report has to be reviewed.

Mini case study

Yassine, founder of an HR SaaS in Casablanca, has 140 SMB customers and has just signed two industrial groups with 3,000 employees each. Both require a dedicated database. Instead of migrating everything, his agency sets up tenant routing: the 140 SMBs stay on the shared schema, the enterprise accounts each get a managed PostgreSQL instance. Project cost: 180,000 MAD of development and 1,800 MAD per month of hosting per enterprise account. Yassine bills the option at 5,000 MAD per month per customer: the margin reaches 3,200 MAD per month per account, and the investment pays back in about 28 months with two customers, 14 months with four.

FAQ

Is Row Level Security enough for an enterprise account?

Technically yes if it is well tested, with automated tests that try to read another tenant's data. Commercially, roughly one enterprise account in two will still ask for physical isolation, hence the value of a dedicated option.

How long does it take to make an existing SaaS multi-database?

Count 6 to 12 weeks for a mid-sized SaaS, i.e. 120,000 to 300,000 MAD depending on technical debt. Routing, parallel migrations and monitoring make up most of the effort.

Can dedicated databases be hosted locally?

Yes, several local providers offer managed PostgreSQL or VMs for 800 to 2,500 MAD per month per instance. Check the service level (99.9 % minimum) and off-site backups.

How do you run migrations across 200 databases?

With an orchestrator that applies each migration database by database, stops on the first failure and logs the state. A well-tooled migration across 200 databases takes 15 to 40 minutes instead of a few seconds on a shared schema.

Which model should a new SaaS start with?

A shared schema with RLS and a data-access layer that centralises tenant_id. This keeps the hybrid door open for a future overhead limited to 10 to 15 %.

Let's scope your project. We design your SaaS multi-tenant architecture, from shared schema to a dedicated enterprise option, with an indicative budget from 250,000 MAD (about 23,000 EUR) and a 6 to 10 week timeline. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.