Fleet Governance & Memory · govern any fleet

Govern the agents you didn't build.

Your org already runs agents from more than one vendor: Agentforce, Copilot, in-house builds, open-source runtimes. Fleet Governance is the one oversight plane they all answer to, and the memory they deposit into and recall from is Cortex, the company brain: governed, tenant-exact, every read audited.

Private alpha · design partners only Agentforce · Copilot · in-house · open-source Roster-gated memory Every read audited Value per vendor
01 The problem

Agents are arriving from everywhere. None of them answer to the same thing.

Agentforce, Copilot, the team's own builds, an open-source runtime someone stood up last quarter: each one is its own black box, with its own memory and no shared accountability.

01

No shared oversight

Each vendor's agents are governed, or not, on their own terms. There is no single place to see what the fleet did.

02

No shared memory

What one agent learns dies inside one vendor's box. The next agent re-learns it, or repeats the same mistake.

03

No per-vendor accountability

When something goes wrong, or right, you can't say which vendor's agent caused it, or what it was worth.

02 How it works

Deposit, govern, recall, across every vendor.

Every agent deposits its experience into Cortex, the company brain, one roster-gated, Shield-scanned, tenant-isolated memory, and recalls lessons from it. Every read is audited, and value is broken out per vendor.

01
Roster gate
Only agents on the roster reach Cortex. An unknown agent never deposits or recalls.
02
Shield scan
Every deposit and recall is screened for the prompt injection and the data-theft attempt.
03
Tenant isolation
One tenant's Cortex can never be read by another. The boundary holds across vendors.
04
Audited recall
Every read lands in the record, attributed to the agent and vendor that made it.
05
Per-vendor value
What each vendor's agents contributed, and recalled, rolls up by source.

One memory the whole fleet shares, and a record of every time any agent touched it. Self-hosted, air-gapped, or hosted by Daybreak Labs: log in and go.

03 An audited read

Every recall is attributed, and broken out per vendor.

An external agent recalls a lesson from Cortex; the read is roster-gated, Shield-scanned, and recorded against the vendor that made it. Value rolls up the same way.

cortex · fleet readtenant isolated
# external agent recalls a lesson
agent · agentforce-svc-07✓ on roster
shield scan✓ clean
tenant boundary✓ held
recall → record✓ audited

Fig. 03 · One recall by an Agentforce agent: gated, scanned, bounded, and written to the record against the vendor that made it.

value · per vendorattributed by source
# who contributed, who recalled
Agentforcedeposits + recalls
Copilotdeposits + recalls
in-housedeposits + recalls
open-sourcedeposits + recalls

Fig. 04 · Value broken out by the vendor whose agents deposited and recalled it, from the same record.

04 Why it stands alone

A product, not a feature.

Fleet Governance sells even to organizations that never run Lightwork's own runtime. It governs and learns from the agents you already have, whoever built them, which is what makes it a standalone product rather than a setting inside the platform.

01

Vendor-neutral by design

Agentforce, Copilot, custom in-house agents, open-source runtimes: they all deposit and recall through the same governed plane.

02

One record for the whole fleet

Every read audited, every deposit attributed. The oversight you can't get from any single vendor's console.

03

Included at Platinum

Standalone for organizations that want only the governance plane, and included at the Platinum platform tier.

Get started

Bring the agents you already have under one record.

We're working with a small number of design partners in regulated industries. If your fleet spans more than one vendor, let's scope it.