Truss Labs Inc.

Browser-edge governance on infrastructure you control

Truss is an open-source browser governance layer for teams using public AI tools. The Chrome extension hooks ChatGPT, Claude, and Gemini in the browser, checks each prompt against local YAML policies, and blocks or redacts sensitive data before the request leaves the employee's machine.

The proxy still exists, but it is now infrastructure rather than the headline. The product surface is the browser edge: real-time policy enforcement, fail-closed behavior when the proxy is unavailable, and hash-verifiable receipts written to infrastructure you control.

Browser-edge demo

Primary recording target: Chrome extension intercepting ChatGPT, Claude, or Gemini.

Legacy proxy MP4
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.

Current homepage visual updated for the browser-extension pivot. Next capture should show block, redact, and fail-closed flows.

What ships in the extension

Prompt interception

The extension hooks web AI clients directly, so policy checks happen at the user interaction layer rather than after data has already reached a model provider.

Local enforcement

Teams keep policy, receipt storage, and proxy execution on their own machines or private infrastructure. Truss does not become a SaaS middleman.

Fail closed

If the proxy is unreachable, the extension blocks submission instead of silently allowing sensitive prompts through.

Process proxy underneath

The CLI proxy remains useful for API gateways, local agents, and wrapped command-line tools. It is the same enforcement loop beneath the browser product: inspect payload, apply policy, write a verifiable receipt, then forward only if the decision allows it.

# Browser extension path
truss proxy start --policy examples/policies

# Legacy process wrap path
truss proxy exec -- gemini-cli

# Audit trail
truss receipt verify ~/.truss/ledger/receipts

Confidential deployment path

For enterprise pilots, the same proxy can run as a managed service or inside confidential compute. The browser extension becomes the enforcement point employees actually touch; the private proxy becomes the policy and receipt boundary the security team controls.

Proof and source

Source: github.com/trusslabs-org/truss-labs. Browser extension docs: extension/. Live audit-proxy demo: demo.trusslabs.org.

Status: pre-product as a SKU. Current public work is focused on the browser extension as the primary customer-facing surface for AI governance at the edge.