Clonext
Engineering· June 12, 2026 · 2 min read

Why every client gets a dedicated database and pool

Clonext
The Clonext team
Company · Clonext

Ask how a typical SaaS platform stores your data and you'll usually hear some version of "logical isolation" — your rows live in the same tables as everyone else's, separated by a tenant ID and a great deal of hope. At Clonext we made a different call: every client gets a dedicated database and a dedicated application pool. Here's the reasoning, and what it costs us.

Shared schemas optimise for the vendor

A single shared schema is wonderfully convenient — for the people running the platform. One migration updates everyone, one connection pool serves everyone, one backup covers everyone. The economics are excellent, right up until they aren't: a runaway query from one tenant degrades latency for all of them, a migration bug can expose data across the boundary, and "delete my data" becomes a forensic exercise instead of a single, clean operation.

Multi-tenancy quietly moves cost from the vendor's balance sheet to the customer's risk register.

What isolation means here

When we say isolated, we mean it at the level of infrastructure, not configuration.

  • Dedicated database — your tables, your indexes, your storage. No tenant column doing security's job.
  • Dedicated application pool — your processes, your memory, your CPU. A neighbour's spike isn't your problem.
  • Dedicated backups — encrypted nightly and restored against your instance alone.
  • Your own domain — DNS, TLS and email configured for you, end to end.

The trade-offs we accept

Isolation isn't free. We run more databases, more pools and more backup jobs than any multi-tenant platform would, and our automation has to treat a fleet of one as the default case. We accept that cost because it buys something you can't fake after the fact: a blast radius that stops at your boundary.

Crucially, isolation doesn't mean falling behind. Because every instance is built on the same proven core, upstream improvements still reach you on the platform's schedule — the velocity of a shared system without the shared failure domain.

Need this built for your business?
Tell us what you need — we scope a quote within days.
Tell us what you need
#Architecture #Isolation Share