Platform / For partners

For managed providers and integrators

You host it, you brand it, you keep the customer relationship.

The platform was built to run in someone else's environment, which makes a managed provider a first-class deployment rather than a special case. You licence per managed estate, run it on your own capacity, and put your name on the front of it.

One tenant per customer

Separation is structural, not a filter applied on the way out. A tenant's events, policies, cases and reports are addressed within that tenant, and a query written in one cannot reach another. That is what makes a shared deployment defensible to your customer's auditor.

Your brand on the surface

The console and the reports carry your identity — the visual system is token-driven, so it re-skins rather than being patched. Your analysts work in one place across every customer you manage; your customers see your product.

Licensed on volume, nothing else

You are charged on the volume your managed estates ingest per day — not per console, not per analyst, not per machine under management. Adding a customer costs you the volume they bring and nothing else, and your margin comes from the service you wrap around it, which is the part your customers are actually buying.

Why this suits a provider specifically

The gate is your liability shield

Acting inside a customer's estate is the riskiest thing a provider does. Every world-changing action here crosses one approval gate that records which guard allowed it, which held it, and who released it — so when a customer asks why you isolated a production host at 3am, the answer is one record rather than a reconstruction.

You can also set a customer's containment tier so that important machines are always held for a human. That is a contractual promise you can actually keep.

One platform instead of eleven integrations

The cost that kills managed-service margin is not licences, it is the integration tax — eleven products per customer, each with its own agent, its own console and its own idea of which host is which. One agent and one event shape collapses that, and onboarding a new customer stops being a project.

The detection content you author for one customer applies to all of them, versioned, without maintaining eleven copies of the same rule.

The honest limits

We publish these on every page. A partner deployment has its own.

Capacity is yours to plan

You are hosting it, so retention and event volume are your infrastructure decisions. We will size it with you honestly, including telling you when a customer's volume makes a deal unattractive.

Six lines are not sold yet

They are in the package and they work, but you cannot resell what has no commercial terms. Build your service catalogue on the two lines that are generally available — see pricing.

There is no marketplace to sell into

Signed third-party modules are part of the architecture and not part of the business yet. If you are betting on revenue share from your own content, that door is not open today.

We are early, and you would be too

There is no partner programme with tiers and badges. What exists is a direct line to the people who built it, which is better for the first few partners and worse for the fiftieth.

Start where a provider should start.

Take the trial against your own infrastructure first, with your own estate as the test customer. A provider who has not run it on themselves cannot sell it, and thirty days on your own machines tells you more than any deck we could send.

Start with a trial licence Read the capability index