Policy lifecycle
Owners and Admins publish a versioned policy. Each enrolled device verifies its organization, expiration, and PonoLens signature before activation.
Company governance beta
Turn supported AI activity into policies your company can improve.
PonoLens inspects supported workflows locally and shares redacted activity records, review outcomes, and fleet health with authorized Owners and Admins. Encrypted originals stay on each Mac. See what’s stored, where, and what’s uploaded →
Available in the company-governance beta
Local inspection. Central policy and health.
Coverage is published per supported integration. PonoLens does not claim universal visibility, and it counts a block only when a supported before-send adapter confirms enforcement.
Verified integrations
See which supported tools are connected and whether local compatibility verification passed, failed, was not run, or became stale after 30 days or a detected version change.
Privacy-limited evidence
With explicit consent on each device, leaders can see finding categories, review status, approved corrective actions, and verified enforcement status—not the sensitive content itself.
Fleet health
Identify reporting devices and missing, outdated, stale, or unhealthy configured integrations. Missing evidence never proves that no activity occurred.
How it helps leadership
Supplement surveys with evidence from supported workflows.
Authorized leaders can see which supported AI coding tools are connected, which devices are reporting, where sensitive-data findings occur, which policies produced warnings or verified blocks, and where integration health needs attention. The company dashboard now uses deterministic analytics, not an LLM, to identify trends, repeat findings after remediation, policy-version changes, common approved corrective actions, and predefined policy areas for human review. It does not automatically publish or activate policy changes. The initial view analyzes up to 1,000 consented governance evidence records from supported workflows.
Roadmap
Expand carefully, verify continuously.
Roadmap items are plans, not currently available features, and priorities may change based on pilot evidence.
Current beta
macOS 13+, signed managed policies, organization-controlled retention, integration coverage matrices, local compatibility verification, fleet health, and redacted enterprise governance evidence.
Release hardening
The private Apple silicon v0.2.57 test build is signed, notarized, and stapled. Public download metadata may point to an earlier published build. Remaining release work includes automatic updates, clean-device testing, and repeated adapter conformance checks as supported tools change.
Broader integrations
A documented adapter framework, expanded post-action and MCP coverage, and re-verification when supported tool releases change their hooks.
Inbound network evidence
Start with a generic authenticated JSON bridge using a versioned ponolens.network-evidence.v1 schema, scoped tokens, strict validation, redacted receipts, read-only analytics, and fictitious-event conformance tests. Customer-authorized DNS, EDR, or SIEM tools would post findings into PonoLens. This is not automatic DNS monitoring, and it cannot prove attribution the source does not provide. Vendor-specific and outbound connectors follow later.
Cross-platform
Windows packaging is planned after the macOS lifecycle and integration behavior are proven. Linux follows as a later research and validation effort.
Pilot with evidence
Test the workflows your company actually uses.
We want feedback from engineering, privacy, security, education, healthcare, legal, and other teams evaluating AI coding tools. PonoLens supports privacy and compliance workflows but does not itself establish compliance.