Excubitor platform · Open-Weight Model Governance

Your models. Your hardware. Your evidence.

Open-weight models come with no vendor standing behind them. Excubitor keeps a registry of the exact weights a named person approved, proves what each model server actually serves, and lets an agent reach a server only while the two match.

Ledger recordSample, illustrative values
{
  "type": "posture",
  "agent": "excubitor.models",
  "payload": {
    "decision": "model_attested",
    "server": "models.acme.internal",
    "model": "acme-assist-70b",
    "digest": "sha256:3f9e…a1",
    "approved_by": "security lead",
    "licence": "recorded"
  },
  "evidence": {
    "chain": "sha256-chain/2",
    "prev": "71d0…4b"
  }
}
Hashes, not content. Chained to the record before it.
What it gives you

Approve by fingerprint

A named person approves specific weights, with licence and source, by the fingerprint of every model file.

Prove what is served

Each model server attests the weights it serves. A swapped model is a high alert and its server is refused.

Revoke in one step

Revoking an approval cuts off every server serving those weights, and a CI step fails a build that ships weights nobody approved.

How it works

Open-Weight Model Governance, in four parts.

Fingerprints, not names

A model is its files, so approval is by content hash. Renaming a file approves nothing.

Attestation at the server

The server's attestation is compared with the registry before an agent's request reaches it.

In your pipeline

The CI step reads the registry and fails a build carrying unapproved weights, before anything ships.

Air-gapped

The registry, attestation and revocation all run inside your estate. Nothing is sent out.

Shipped

What is live, and since when.

Every item names the release that carries it. Releases are signed, and each lists the commands to check them before you install.

What it does not do

The limits, said first.

See it run on your own agents.

No standing vendor access, ever. Managed with evidence, never on faith.