MSSP

Add AI action governance to your managed security offering.

Clients are adopting AI tooling faster than their controls are changing, and most have no answer to what their agents are permitted to do. Oconee Runtime provides the platform layer — detection, policy, enforcement and evidence — that a managed security provider can build a recurring service around: deployment, policy design, monitoring and reporting.

A new client requirement with no incumbent

AI governance is arriving in client conversations before most providers have an offering for it. The work is real — deciding what agents may do, deploying the controls, reviewing decisions, reporting on them — and it is recurring rather than a project.

What is missing is the technology layer underneath it, which is not a reasonable thing for a services business to build.

Example scenario

One action, evaluated

Proposed action

Client environment

Managed AI governance engagement

Context

Partner role
Deployment, policy design, monitoring, reporting
Oconee role
Platform, product support, enforcement layer
Client
Deployed in the client's own workspace
Commercials
Referral or managed engagement

Policy decision

ALLOW

Each client runs in their own Oconee workspace. The partner operates the service around it; Oconee provides and supports the platform.

Recorded as evidence

  • actor
  • agent
  • action
  • resource
  • context
  • policy
  • decision
  • timestamp
Examples illustrate Oconee Runtime workflows and policy scenarios.

How deployment actually works

This is the part worth being precise about. Oconee is deployed per client, in that client's own workspace, and a partner works within each one. There is no single console today that administers several client organisations from one screen — if your service model depends on a multi-tenant view, that does not exist yet and you should plan around its absence rather than around a roadmap.

  • One Oconee workspace per client
  • Partner-led deployment, policy design, monitoring and reporting
  • Referral and managed engagement models
  • Deal registration with a protection window, in the partner portal
  1. Actor
  2. Agent
  3. Action
  4. Resource
  5. Context
  6. Policy
  7. Decision
  8. Evidence

Relevant capabilities

  • Per-client deployment in the client's own workspace
  • Partner program with referral commission on collected subscription revenue
  • Deal registration and opportunity protection
  • Product support and demo support from Oconee

What the partner program is

A referral relationship pays a percentage of collected subscription revenue for a defined period, and stops if the customer churns. Managed and reseller arrangements are agreed individually rather than published as a fixed margin. The current terms are on the partner page.

Common questions

Can we manage several clients from one console?
Not today. Each client is deployed in their own workspace and a partner works within each. A centralised multi-client console is not a current capability, and this page does not assume one.
What does the partner program pay?
Referral partners earn a percentage of collected subscription revenue for a defined commission period, subject to program terms. Managed and reseller economics are agreed individually.

AI proposes. Policy decides.

All use cases