Truss Labs Inc.

Browser-edge governance on infrastructure you control

Truss is an open-source governance layer for teams using public AI tools and shared agent workspaces. It checks prompts and file transfers against stateful YAML policies—blocking or redacting sensitive data before it leaves your boundary and writing a tamper-evident receipt for every decision.

One local policy engine and receipt ledger works across every surface where employees touch AI: browser tabs (ChatGPT, Claude, Gemini), shared Slack sandboxes, and wrapped CLI agents.

1. Browser-edge protection (ChatGPT, Claude, Gemini)

Intercepts prompts inside the browser tab before sensitive data reaches an external model provider.

chatgpt.com Truss Audit Layer: active
Patient lives at 1234 Main St. Summarize their case.
Policy decision: blocked before_send

PHI address matched local policy. Request did not leave the browser. Receipt committed to the local ledger.

2. Shared Slack & sandbox protection (Alice vs. Bob)

When a Slack thread shares one agent sandbox, Alice's uploaded CSV stays on disk. Watch Truss allow Alice's summary deck and block Bob from extracting her raw customer records.

Read the write-up →
Slack #planning · Thread
SANDBOX: ACTIVE
#
#planning thread ready
Click ▶ Run Leak Test below (or step through 1 → 4) to watch Alice and Bob interact with the @deckhand Slack bot.
What Truss Remembers READY
Staged File in Sandbox: —
File Owner: —
Sensitive Data Found: None
Latest Action: Waiting to start…
Policy Decision: —
View raw auditor receipt & session state JSON
 

What ships in Truss

Prompt & file interception

Hooks web AI clients and shared agent sandboxes directly, checking prompts and file exports before sensitive data crosses the boundary.

Session memory on disk

Policies remember file owners and cumulative risk across turns and 10-minute sandbox resets—stopping cross-user leaks that one-shot scanners miss.

Tamper-evident receipts

Every allow, redact, or block writes a hash-chained JSON receipt on infrastructure you control so auditors never have to reconstruct chat logs.

3. Process proxy underneath

The same local proxy powers the browser extension, Slack sandbox checks, and wrapped command-line agents: inspect payload, apply YAML policy, write a verifiable receipt, and forward only when allowed.

# Start the local policy & receipt engine
truss proxy start --policy examples/policies

# Wrap a local CLI agent
truss proxy exec -- gemini-cli

# Verify the receipt chain on disk
truss receipt verify ~/.truss/ledger/receipts

Proof and source

Source: github.com/trusslabs-org/truss-labs · Latest Lab Note: When a Slack thread shares one sandbox, Alice's file becomes Bob's leak · Live audit-proxy sandbox: demo.trusslabs.org