MSP / Managed Services
One skills library. Unlimited clients. Zero data leakage.
Purpose-built for managed service providers. Per-tenant isolation guarantees client data never crosses boundaries, while a shared Skills library lets your whole team leverage senior engineers' expertise on any customer network.
Common problems
- Tenant isolation is fragile — one misconfigured query can surface Client A data in Client B's view.
- Every client has their own SLA targets; tracking them requires spreadsheet discipline nobody has.
- Senior engineers' playbooks walk out the door when they do.
- Onboarding a new client means re-learning their environment from scratch.
- Billing hours for preventive work is impossible without automated evidence.
Typical scenarios
True multi-tenant by design
Native org-level isolation at the database + network level. No shared dashboards, no cross-tenant queries.
Skills library = team leverage
Codify 'check packet loss on all edge switches' once; any engineer, any client — one click to run.
Automated SLA reports
Workflow generates monthly health reports per client with charts, incident counts, and uptime — no spreadsheets.
One-week onboarding
New engineers start delivering value in a week because the Skills library is their training ground.
FAQ
How is tenant isolation enforced?
At the database layer: every row carries an org_id, every query is middleware-scoped to the current user's orgs. There is no 'super-query' across tenants available to application code. Network-level isolation ensures per-org Docker networks for MCP tools.
Can we brand the portal for each client?
Yes. Per-org branding (logo, colors, domain) is supported on every tier. Clients see a white-labeled portal when they log in.
How is SLA billing evidence tracked?
Every AI-triggered action, workflow run, and manual remediation is logged with timestamp, user, and outcome. Export as CSV or push to your billing system via Webhook.
Do you support delegated admin (super-admin across clients)?
Yes. The platform-admin role has a cross-tenant overview (for MSP internal use) while end clients see only their own environment. All cross-tenant actions are audit-logged.
How does tenant billing and metering work?
Per-tenant seat count, AI token usage, and workflow execution counts are tracked and exposed via API + dashboard. Price your clients however you want — per user, per device, or flat rate.
What if a client wants their data on-prem but we want SaaS for others?
Hybrid is supported: run a dedicated Pharaoh instance for that client while the rest stay on your shared SaaS deployment. One pane-of-glass via the MSP admin account.
Pharaoh Command · Book a demo