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
3 stepsagent, signed script, audit export
Request Govern early accessMulti-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 gives each MSP tenant its own PostgreSQL schema and binds portal tokens to one tenant. Customer scope inside a tenant (software deployment, agent commands, probes) is a Gap while fixes are in progress.
Fleet operations at scale
Fleet operations use lookup and catalog APIs, not full-list dropdowns, so large fleets do not load into one list. Customer-scope fixes for software deployment, agent commands and probes are in progress; see the Gap rows on the trust hub.
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 /govern/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 /govern/trust/security for evidence tables and architecture references for assessors.