Partner Network · MSSP track

Many clients.
One governed service.

Client tenants, service models and ingest allocation are modelled in the platform. Quotes carry your logo.

Platform → MSSP → client

Each client is a tenant with a server-enforced boundary. Platform administrators cannot act inside your clients' tenants without a time-limited break-glass grant.

SOCaaS or PaaS

Run the SOC for a client, or host a client who runs its own SOC — where you cannot see its data.

Ingest you control

Allocate ingest from your envelope to each client. An allocation beyond your envelope is refused, never silently overbilled.

Your clients stay yours

kymeer never contacts your clients. Their tickets come to you; you escalate to us. Platform incidents reach us and you together.

Provision from the portal

Request tenants and trials through the partner portal; kymeer invites each client's first administrator.

Run your own SOC on it

A free internal-use licence for your own operations.

What you can and cannot see

Three service models.

SOCaaS

You run the SOC for the client inside their tenant.

PaaS

You host a client who runs their own SOC. You cannot see their data.

Proof of concept

A trial tenant tied to a registered deal, with dates and success criteria agreed first.

Support chain

Client → MSSP → kymeer. Platform incidents reach kymeer and you in parallel.