Introducing Tork: AI Governance for Every Framework

PII Detection & Redaction — 50+ PII types across US, EU, UK, and Australian formats. SSNs, credit cards, healthcare identifiers, biometric data. Detected and redacted before they leave your infrastructure.

Policy Enforcement — Define rules for what your agents can and cannot do. Block dangerous tools, restrict data access, require human approval for sensitive actions.

Cryptographic Receipts — Every governance decision generates an immutable, HMAC hash-chained audit entry, included in the daily on-chain anchor once it reaches Tork. On the on-device package that receipt is a local object: reaching your dashboard and the anchor requires an API key and an SDK version carrying attestation reporting (tork-governance 0.24.0+ on PyPI, 0.11.0+ on npm), and lands as a client attestation. Hand these to your compliance team for HIPAA, GDPR, SOC 2, or PCI-DSS reporting.

MCP Security — Purpose-built for Model Context Protocol. Scan MCP servers, govern tool calls, and enforce policies across Claude, Cursor, and Windsurf agents.

Kill Switch — Instantly halt any agent with a single API call. Because sometimes you need an emergency stop button.

Correction — 3 August 2026

The two paragraphs above describe one product where there are two, and the phrase “unless you choose to sync with Tork Cloud” made syncing sound like a setting on the same package. It is not — it is a different package with a different trust model, and readers who installed the local one and waited for a dashboard were waiting for something that was never going to arrive.

tork-governance (the pip/npm lines above) is the on-device family, entry class Tork. tork-governance makes the governance decision on your machine. PII detection, redaction and the returned verdict are computed on-device. With no API key it makes zero network calls: prompts, completions and detected PII values never leave the machine, and nothing appears in your dashboard.

Supply an API key and the SDK additionally reports a metadata-only attestation of each decision — the action taken, PII type labels and counts, a risk classification, policy labels and a salted fingerprint. It never sends input text, output text or PII values. The decision itself is still made on-device and is never delayed or changed by reporting. Those attestations appear in your dashboard and are included in the daily on-chain anchor — each one recorded as a client attestation (capture_mode=edge, attested_by=client), a claim Tork recorded but did not execute and cannot independently verify. Requires tork-governance 0.24.0+ (PyPI) or 0.11.0+ (npm).

A decision reported by an on-device SDK is recorded as a client attestation (capture_mode=edge, attested_by=client): a claim Tork recorded but did not execute and cannot independently verify. A decision made by @torknetwork/sdk is recorded as capture_mode=cloud, attested_by=tork — Tork made that call itself. Both are equally immutable once anchored; they differ in what is immutable. A client attestation freezes your claim. A server-governed receipt freezes Tork's own decision.

“Receipt generation happens locally” is true, but a local receipt is a local object returned to your code — not a dashboard row. Local governance is free and unlimited — decisions made on your own machine are never metered. Evidence is what is metered: attestations, receipts and anchoring.