One console across every client
Each client is a separate tenant, and your analysts see all of them from one console. Open a tenant and you get the same detail a single-company deployment would show.
Protoxol gives MSPs a multi-tenant console with per-client SIEM, EDR, email, threat intelligence and SOAR. Per-endpoint billing — no GB-based licensing.
Most security tools are built for one tenant. Bolting on "multi-tenant" later usually means a client-picker dropdown, not real isolation. Here's what to check before you commit.
Each client is a separate tenant, and your analysts see all of them from one console. Open a tenant and you get the same detail a single-company deployment would show.
The reporting module produces the monthly report for each client on its own, from that client's data. You hand each customer their report without assembling it by hand from several tools.
Create the tenant in the console, enrol the client's endpoints through their MDM, connect their Microsoft 365 or Okta logs. Time to first telemetry depends on how fast those connect, usually days.
One client gets EDR only; another gets EDR, SIEM & search and email protection. Each of the ten modules is activated for the client that needs it, on the same platform.
Your cost is per endpoint across all tenants, by plan, with no per-GB ingest line. A known cost basis lets you set a per-seat service price and know the margin before you sign.
Protoxol is a platform, and it isn't a managed service. Your analysts run the console, approve playbook actions and own the client relationship. EU-hosted SaaS or self-hosted, as each client requires.
Most "MSP-ready" security platforms mean the vendor added a client selector on top of a single-tenant product. Real multi-tenant operations need per-client data isolation, an aggregated view across your whole book of business, and a pricing model that doesn't erode the margin you're trying to build a business on.
Protoxol was built multi-tenant from the data model up — not retrofitted. One console shows every client's posture at a glance; drilling into any one of them gives your analyst the same full context as a single-tenant deployment would. Talk to the MSP team about your current client mix.
You're billed per endpoint across your book of business, aggregated into one invoice. Per-client cost breakdowns are available in the console for your own repackaging and billing.
Client-facing reporting can carry your branding. The operating console itself is built for your analysts, not typically exposed directly to end clients.
A new tenant is provisioned in the console directly — it's a configuration step, not a new deployment. Time to first telemetry depends on how quickly the client's endpoints and log sources connect, typically days.
No. Protoxol sells the platform to MSPs to operate and resell — we don't go direct to your clients, and there's no reseller-bypass clause hiding in the contract.
30 minutes with our MSP team. Tell us your client count and mix, we'll show you exactly how the console and the numbers work for you.