Your Own Instance Instead of a Big Platform: Run Separately, Stay Separate

Two offers can look identical at first glance: same features, similar price. And yet a fundamental decision separates them. On a multi-tenant platform, many customers share one common installation and usually one common database — separated only by software logic. With your own instance, each organisation receives its own complete installation: its own files, its own data, its own place. A note on my own products: this is how I ship them – one dedicated instance per customer, on their own German web hosting.

The radius of a failure

The most important difference shows itself when things go wrong. If a security vulnerability or a configuration error hits a platform, potentially all customers are affected at once — the association's membership list just as much as the appointment data of the practice next door, even though the two never had anything to do with each other. With separate instances, an incident stays confined to one installation. Plain downtime follows the same logic: if the platform goes down, everyone is down; a single instance affects only its own organisation.

Separate also means: maintained independently

A platform changes for everyone at the same time — a new interface, altered workflows, or discontinued features hit every law firm and every cultural centre on the same day, whether it suits them or not. Your own instance gets updated when it suits your organisation. And it can be adapted without a thousand other customers having to carry the same adaptation: your own terminology, your own design, your own modules.

What platforms do well

To be fair: shared operation has its advantages — professional monitoring around the clock, updates instantly for everyone, onboarding in minutes. For non-critical data, that is legitimate. The balance shifts once sensitive data comes into play: a practice's health data, religious affiliation in a membership database, a law firm's professional secrets. Then the limited blast radius weighs more heavily than the convenience.

In short

"One instance per organisation" is not a marketing label but an architecture decision: a smaller damage radius, independent maintenance, genuine adaptability. Where that instance should live is covered in the article Your Server, Your Data.

Frequently asked questions

What exactly is an instance?

A complete, standalone installation of a piece of software for exactly one organisation — with its own files and its own data set, usually under its own domain.

Isn't a big platform safer because it is professionally operated?

Professional operation is a genuine advantage — but it changes nothing about the radius: an incident on the platform affects all customers at once. A well-maintained instance of your own combines a limited radius with solidly operated technology.

Will I notice a difference in everyday use?

Hardly — and that is precisely the point. The difference shows itself not in everyday use but in exceptional situations: during outages, price increases, customisation requests, and when leaving.

Last updated: August 2026

Ask a question — I always reply personally.