Isolation isn't a feature — it's your foundation
Dedicated instance vs. shared SaaS: what multi-tenant architecture quietly decides about your performance, your data and your ability to leave.
In software, “tenancy” is one of those words that sounds like a billing detail and is actually a description of power. When a platform tells you your business runs on shared infrastructure, they’re not describing how the servers are arranged. They’re describing who gets to make decisions about your data when those decisions get hard.
I keep coming back to this because it’s the least-understood structural fact in the “move your business online” space, and it sits underneath everything I’ve written about RFQ data as a balance sheet and what you’d lose if your SaaS shut down. If you run a manufacturer’s web presence on a multi-tenant platform — a marketplace storefront, a shared cart SaaS — your business shares a database with thousands of others, and that single fact decides more about your outcomes than any feature list.
What “multi-tenant” actually means, without the jargon
Picture an apartment building. You rent a unit. The plumbing, the walls and the management company are shared, and that’s fine — until you want to knock down a wall, install industrial equipment, or take your fixtures with you when you leave. You don’t own the building; you own the right to occupy a unit under the landlord’s rules.
A shared SaaS platform is the same building. Your catalog and your buyers’ inquiries sit in a database shared with every other tenant. In practice that means three things you’ll feel long before you ever think about “tenancy”:
- Their load is your latency. When another tenant’s promotion spikes their traffic, the shared servers you both sit on feel it. You don’t control your own performance; you inherit the average behaviour of everyone else in the building.
- Their rules are your rules. Every feature, every export format, every limit on how much data you can pull — these are set for the median tenant, because a shared system can’t give one tenant something without giving it to everyone.
- Their incentives shape your access. If the platform monetises buyer relationships — and most that host your storefront do — then “how much of my inquiry history can I export” is answered in a meeting about their revenue, not your business. I’ve gone deep on why that contact data is exactly what platforms withhold in the post on where RFQs land.
None of this makes shared SaaS evil. It makes it shared — and sharing is the wrong model for the thing your whole company hangs on.
Why a manufacturer feels this more than most
Every business suffers from shared infrastructure eventually, but exporters and industrial suppliers feel it first, for three reasons.
Your buyers are doing serious due diligence. A procurement engineer comparing suppliers isn’t bouncing around a flashy storefront; they’re loading spec sheets, datasheets, certificates and — increasingly — asking whether the company they’re vetting looks like a real, stable operation. If your site slows under another tenant’s load, or your product pages live on a template that makes you look interchangeable with three hundred identical listings, you’re not competing on quality. You’re competing on the ceiling your landlord set.
Your product lines are deep and long-lived. A consumer brand rotates a few SKUs a season. A manufacturer carries hundreds of SKUs with specifications that stay accurate for years. That catalog is your institutional memory — and on a shared platform it lives in a schema designed for the average tenant, which is rarely the average factory.
Your buyer relationships are the whole asset. When you sell a component that goes into someone’s product, the RFQ, the qualification, the audit — that history is the relationship. Shared tenancy is where that history becomes the platform’s hold over you — it’s the data that keeps you renewing.
What a dedicated instance actually changes
A dedicated instance is the opposite choice: your catalog, inquiries, media and configuration live in a database that is yours alone. Nothing about that is magic, and it’s worth being precise about what it buys you, because the word “dedicated” gets thrown around loosely too.
- Your performance is yours. Nobody else’s promotion spikes your latency, because nobody else is on your instance.
- Your boundaries are yours. The decision about what your data export contains isn’t negotiated against a hundred other tenants’ needs and the platform’s revenue. It’s a decision about your business, and a complete export is the default rather than a special request.
- Your exit is real. Because the database is yours alone, leaving doesn’t mean untangling your records from everyone else’s. It means taking your copy and going — the thing shared tenancy makes structurally difficult.
This is why I keep saying isolation isn’t a feature. A feature is something you can add or remove from a checklist. Isolation is the shape of the building — it decides whether every other decision about your data is made in your interest or in the average tenant’s.
The honest counterargument
Let me argue the other side, because it’s real. Shared SaaS is cheap, fast to start, and maintained by people whose whole job is keeping it running. A dedicated instance costs more and asks more of you — and if you’re a small exporter, the day-one economics of a marketplace’s free tier are genuinely hard to argue with. I’m not going to pretend otherwise, and our pricing page doesn’t hide that a node is a paid, deliberate choice.
The argument for isolation was never that it’s the cheap option. It’s that the cost difference buys the thing that compounds: a foundation where your data decisions are made for you. Most businesses start in the shared building because that’s where the traffic is — and the sensible path is usually coexistence while you build the owned foundation underneath, not a dramatic leap. The mechanics of that move are in our migration playbook.
The question architecture answers
Next time a platform tells you what you can and can’t do with your own business data, ask one question: is this a decision about my business, or a decision about everyone in the building? If it’s the latter — and with shared infrastructure it almost always is — then the ceiling you’re bumping against isn’t a feature gap. It’s the architecture. And architecture, unlike features, doesn’t change when you ask nicely. You change it by choosing a different foundation.