Multi-Tenant vs. Single-Tenant Software: What It Means for a Freight Brokerage

"Multi-tenant" and "single-tenant" describe how a piece of software separates one customer's data from another's, and it's a legitimate question to ask any vendor before trusting them with a brokerage's carrier, customer, and financial records. In a single-tenant setup, each customer effectively gets their own dedicated instance of the software (and often a dedicated database). In a multi-tenant setup, many customers share the same running application and often the same database, with the software itself responsible for keeping each customer's data separated internally. Multi-tenant done well isn't a compromise — it's how most modern SaaS is actually built, and it can mean faster feature rollout (one update reaches every customer at once) and lower cost (shared infrastructure instead of a dedicated environment per customer). The part worth actually verifying with a vendor is how the isolation is enforced: is every piece of data scoped to a company by design at the data-access layer, or is it a shared table with a filter that a bug could bypass? That's the meaningful distinction, not the word "multi-tenant" itself. Ask specifically: is company/tenant scoping enforced at the point every query touches the database, or only in the parts of the application someone remembered to add a filter to? BZLoader is multi-tenant by design — every table is scoped to a company from the ground up, not a shared database with a filter added on top, and that isolation is enforced at the application's data-access layer rather than left to be remembered per feature.