Use case
Multi-Tenant MSP Operations
Multi-tenant boundaries and fleet-scale catalog APIs for growing MSP platforms.
- Pilot on one tenant
- Export audit slice
- Attach to customer SSP
<30min pilot target
Start free trialMulti-Tenant MSP Operations
Multi-tenant boundaries and fleet-scale catalog APIs for growing MSP platforms.
Multi-Tenant MSP Operations
Visual summary before detailed use case copy.
Why namespace separation matters
MSPs operating as SaaS platforms need customer namespace separation beyond a shared table with a customer_id column. Trustholm scopes each MSP tenant by design-customers, scripts, agents, and audit history stay within your organization boundary.
Fleet operations at scale
Fleet operations use lookup and catalog APIs - not full-list dropdowns - so 100k agent estates stay responsive. Scripts, policies, and audit exports respect tenant scope end-to-end.
Who this use case fits
This use case targets MSP platform builders and large regional MSPs consolidating script operations across acquired customer bases. Pair with /trust/security for evidence tables and honest limitations on dedicated cluster profiles.
Frequently asked questions
- Is this multi-customer within one MSP tenant?
Trustholm tenant maps to your MSP organization. Customer/group scoping inside the tenant uses catalog patterns documented in the product.
- Can we host dedicated databases?
Dedicated database connection profiles are supported for enterprise isolation requirements.
- How do agents authenticate?
Polling credentials issued at registration, plus tenant code headers on anonymous agent paths.
- What about rate limits?
Distributed rate limiting keys agent traffic by tenant and agent identity with Retry-After support.
- Where do I learn more about separation?
See /trust/security for evidence tables and architecture references for assessors.