What Is Multi-Tenant Hosting for Agencies?
Published September 2, 2026 · Updated September 5, 2026
Multi-tenant hosting is a platform that lets one provider run software for many separate client companies from a single console. The word doing the work is tenant: each client is a tenant, and the platform’s job is to keep tenants apart while making the whole fleet manageable as one thing. How far apart they are kept is the only question that matters, and providers answer it very differently.
Here’s what to look for, and what to ask before you put a client on anything.
The two kinds of multi-tenancy
Almost every platform calling itself multi-tenant is one of these two things, and the difference is not marketing:
Shared instance, logical separation. One application and one database serve every client, with a tenant_id column on every table and application code that filters by it. It is cheap to run, which is why it is common. It also means every client’s records sit in the same tables, and the only thing between them is code written correctly on every query, every time. One missing filter is a data breach, and one client’s heavy Monday is everyone’s slow Monday.
Dedicated instance per app. Each client app gets its own virtual machine, with its own application, database, storage and domain. There is no shared table to leak across, because there is no shared table. It costs more per client to run, and it is the answer a client’s security questionnaire is actually asking for.
Note what “dedicated” does and does not mean here. It does not mean a physical server per client. Nobody sells that at these prices, and you should be suspicious of anyone implying it. It means a virtual machine per app, with processors, memory and disk allocated to it alone, on shared infrastructure the provider keeps efficient. That is a real boundary and an honest one.
What real isolation should cover
Ask a prospective platform which of these are per client, and which are shared:
| Shared instance | Dedicated instance per client | |
|---|---|---|
| The unit | One app for everyone | One virtual machine per client app |
| Database | One, with a tenant column | One per machine |
| File storage | One pool | One per machine |
| Domain | Usually a subdomain of theirs | The client’s own domain |
| Backups | Fleet-wide, restore is surgery | Per client, restore one alone |
| A client’s traffic spike | Everyone’s problem | That client’s instance only |
| Offboarding a client | Delete rows and hope | Remove their machines |
The bottom two rows are the ones partners underestimate. On a shared system, restoring one client to last Tuesday means either rolling everybody back or hand-picking rows out of a dump, and offboarding means proving you deleted the right rows and only the right rows. On dedicated machines both are one operation on one machine.
The management problem isolation creates
Dedicated machines have an obvious catch: ten clients means ten of everything to install, patch, back up, watch and renew certificates for, and more again if your clients run more than one app each. That is why partners end up on shared systems despite knowing better. It is not that the isolation argument is unclear; it is that the operational cost of doing it properly grows linearly with the client list.
A platform is worth paying for exactly when it solves both halves: real isolation underneath, one fleet view on top. If a platform gives you isolation and hands you ten management problems, you have bought a hosting bill and kept the work.
There is a third half worth asking about, and most providers do not have an answer: what your client sees. A platform that gives you a fleet view and gives your client nothing leaves you as the human status page, answering “is it up?” by email. Kosnomos splits it in two: a partner portal holding every client you run, and a client portal for each client, scoped to their own apps and carrying your brand rather than ours.
What “managed” should mean at fleet scale
For each client instance, a genuinely managed platform takes:
- installing and configuring the software, and connecting the client’s domain with a certificate
- applying updates and security fixes as they are released, across every client, so the fleet never drifts
- taking backups per client and restoring one on request
- noticing when a client instance goes down, at any hour, and fixing it
- resizing a client without a migration project
If any row still lands on your team once per client, it is a rented fleet with the software pre-installed, and it will get more expensive as you grow, not less.
What stays yours
The point of hosting open-source software for clients, rather than reselling a closed product, is that nobody sits between you and the relationship:
- Each client runs their own copy, not an account inside a vendor’s product.
- Any client is exportable at any time, in standard formats, with no exit fee.
- The address is the client’s, so changing platform never means changing their domain.
- No vendor sells past you. There is no supplier with a direct sales team and your client list.
Who it’s for
Multi-tenant hosting fits agencies, studios and consultancies who already carry the client relationship, and solo developers running one or two apps of their own, and want to host the software behind it without staffing a hosting operation. If you have infrastructure engineers with genuine spare capacity, building it yourself is a legitimate choice. The trade is your team’s attention, permanently.
What it costs
Pricing models vary, and the one to avoid is per seat: it quietly reintroduces the problem open source removes, because your cost then grows every time a client hires. The model to look for is pricing by instance size, which is flat whatever a client’s headcount does. Kosnomos works this way: one virtual machine per client app, from $49/month, with isolation, daily backups kept 30 days, fleet-wide patching, monitoring, the client’s own domain, a client portal and support included at every size, never a per-seat fee, and a published volume ladder that drops the rate 10% from 10 clients and 20% from 50. The pricing page shows every size in plain words, and the platform pages spell out exactly what the managed bundle includes.