Skip to main content

CERBERUS / GOVERNED OPERATIONS PLANE

One governed operations plane for teams and AI workers.

Bind tasks, resources, authority, approval, and duration. Revoke access and review decision, session, and outcome records.

Connection, authority, and session are separate decisions.

Set resources, authority, duration, and required approvals for user access and tasks for AI agents. Bound AI agent work by its assigned task and resources; decision and revocation authority stay with authorized users.

In the user-session example below, resource readiness and user–resource assignment are evaluated separately. When browser work ends, new access, any active session, and the decision trail are checked separately.

01 / 04

The resource stays put. A work path opens.

Add a Windows machine or terminal target to the workspace. Cerberus brings it into the work flow through an approved connection path suited to your environment.

Choose a Windows Agent, private-network Gateway, or existing approved path to fit the environment. Cerberus evaluates reachability and readiness through that path. Registering the resource does not yet grant an operator permission to work on it.

The machine and local network policy remain in your environment.

USER SESSION EXAMPLE
02 / 04

Access follows the task and the actor.

Who will work, on which resource, and for how long? Assignment scope and any required session approval are evaluated separately.

An assignment binds a person to a specific resource and duration. When session approval is required, the request is reviewed separately; approval does not replace the assignment. An expired or out-of-scope request cannot open a new work session.

Authority applies to the selected resource, not the whole network.

USER SESSION EXAMPLE
03 / 04

Work happens in the browser. Secrets stay separate.

The assigned operator opens a desktop or terminal session in the CerberusLite work surface. Target credentials are handled on the protected session path.

At launch, the assignment, time window, resource readiness, and session policy are evaluated again. An allowed decision opens the desktop or terminal surface for the selected protocol. Clipboard and file-transfer capabilities follow the effective session policy.

The work surface follows the protocol and effective session policy.

USER SESSION EXAMPLE
04 / 04

The task ends. The decision trail remains.

Revoke the assignment, close new access, and inspect the session lifecycle. The actor, resource, and closure decision remain in the same context.

Revoking the assignment or reaching its expiry blocks new session launches. If a session is still active, an authorized person closes it separately and checks the result. The assignment change, session state, and closure event remain distinguishable records.

Active-session termination depends on the protocol and deployment model. Session video is in development and is evaluated separately from decision and lifecycle records.

USER SESSION EXAMPLE

CONNECTION MODELS

The path to the resource fits its environment.

The Cerberus work flow stays consistent; the reachability path depends on the chosen model.

01

Optional Windows Agent

Best fit
Local readiness and health visibility for Windows machines.
What it contributes
Device identity, service health, telemetry, and reachability signals.
Stays in the resource environment
Operating system, target service, and local network policy.
02

Private-network Gateway

Best fit
Controlled reachability to RDP, VNC, SSH, and terminal targets on the same private network.
What it contributes
A configured connection path for the selected protocol through the Gateway.
Stays in the resource environment
Gateway operation, target services, and private-network access.
03

Existing approved path

Best fit
Resources with established approved reachability or a manual resource definition.
What it contributes
Brings the resource definition, existing path, and browser work surface together.
Stays in the resource environment
Target reachability, firewall rules, and network permissions.

The Windows Agent is optional. The other two paths are separate connection models.

Agent guide

WORK SURFACES

One control context, different work surfaces.

Protocols such as RDP, SSH, and VNC provide desktop and terminal work surfaces. Available capabilities depend on the selected protocol, deployment model, and effective session policy.

01

RDP

Graphical desktop

A Windows desktop session opens in the browser work surface.

  • Fullscreen
  • Secure attention
  • Clipboard / transfer policy
02

VNC

Graphical desktop

The VNC display and input scope run in the same browser shell.

  • Keyboard and pointer
  • Read-only mode
  • Reconnect
03

SSH

Terminal

The command line and optional file transfer project into a browser terminal.

  • Terminal input
  • SFTP transfer
  • Input policy
04

Kubernetes

Terminal session

A Kubernetes terminal joins the managed resource and session context.

  • Terminal projection
  • Input scope
  • Session status

TRUST BOUNDARY

Work is visible. The target secret stays separate.

While the operator works with the desktop or terminal, connection credentials pass through the protected session path to the protocol runtime.

The technical credential-custody boundary is explained in the docs.

01

Work in the browser

The operator uses the desktop or terminal surface while the target secret remains on the protected session path.

02

Authorized session context

Protected material is handed off only for the selected target and authorized session context.

03

Protocol runtime

Credential material required by the connection is processed on a work path separated from the user surface.

See the flow in the product.

Explore resource, assignment, and session surfaces in the demo. Compare access models in pricing.