Neon deploys as a lightweight browser extension and works with all major Chromium-based browsers used in enterprise environments — including Google Chrome, Microsoft Edge, Perplexity's Comet, OpenAI's Atlas, and others. No dedicated or enterprise browser is required. Neon is compatible with Windows and macOS managed devices and can be distributed via MDM, GPO, or direct user installation. Because Neon runs as an extension inside existing browsers rather than replacing them, there is no browser change management required and no risk of it becoming a single point of failure for your environment. Extension updates are handled automatically — no browser restarts, no additional policy pushes, and no IT intervention required when Neon updates.

Yes — this is one of Neon's core use cases. Rather than relying on employee training or retroactive log review, Neon enforces AI acceptable use policies at the exact moment a user interacts with an AI tool in the browser. Security teams can configure behavior-based policies that trigger context-aware interventions in real time — warning a user before they upload a document to an AI tool, or blocking a data submission that violates a defined policy. Policies can be applied by user, role, department, application, or data type, and configured to warn, block, or escalate depending on the sensitivity of the interaction. Every policy trigger event is captured — including user, application, action, and timestamp — giving compliance teams the audit trail needed to demonstrate enforcement. AI tools your organization has sanctioned can operate freely; unsanctioned tools are governed precisely at the point of use. The result is an AI policy that actually runs — not just a document that sits in a shared drive.

Neon is designed to monitor organizational risk — not to surveil individual employees. The platform operates in monitor mode, providing full visibility into security-relevant behaviors without actively capturing or intercepting personal activity. Security teams can define which detections to monitor, what triggers an alert, and what actions are allowed or blocked. What Neon observes is behavioral and contextual: which applications are accessed, what authentication methods are used, whether data is being submitted to risky destinations, and whether data being uploaded to an AI tool like ChatGPT, Gemini, or Claude is allowed. Neon is not designed to capture or store the personal content of general browsing unrelated to security policy. For organizations with employee monitoring disclosure requirements — particularly those operating under GDPR, CCPA, or state-level labor laws — Neon's deployment model supports transparent communication to employees about the scope of monitoring, consistent with your existing acceptable use and IT policies. Enterprise customers are encouraged to work with their legal and HR teams to ensure deployment documentation aligns with applicable privacy regulations and disclosure obligations for their jurisdiction. Neon's team is available to support this process.

Neon captures behavioral telemetry — security-relevant signals about how users interact with applications, forms, credentials, and data in the browser. This telemetry powers real-time detection, policy enforcement, and the forensic timeline available to your security team for threat hunting and incident response. Telemetry data is retained for up to 30 days by default, giving security teams immediate access to recent session history for investigations. Data beyond that threshold can be transferred — reducing cost while preserving the forensic record — or exported directly to your SIEM, allowing you to retain browser telemetry within your own data environment with no dependency on Neon's storage infrastructure. Organizations with strict data residency or retention requirements can configure Neon to minimize on-platform storage entirely by routing telemetry events in real time to their existing SIEM. This is particularly relevant for regulated industries where data sovereignty, retention policy compliance, or third-party data hosting restrictions apply. Neon does not capture or retain the full content of general browsing sessions. Detection is based on behavioral signals and contextual analysis at the point of interaction — not bulk session recording.

It's the right question to ask of any security vendor — and especially one that operates inside the browser. Here's how Neon addresses it directly: No endpoint agent, no proxy, no single point of failure. Neon deploys as a lightweight browser extension, not an endpoint agent or network proxy. This architecture matters because it means Neon cannot become a CrowdStrike-style incident — there is no kernel-level driver, no process that can crash a device, and no network routing dependency that could take down connectivity if something goes wrong. The worst-case scenario of a Neon failure is that the extension stops functioning. Your users keep browsing; your other security tools keep running. No privileged network position. Unlike proxy-based security tools — including many SASE and SSE solutions — Neon does not sit in the network path between your users and the internet. A compromised proxy gives an attacker a man-in-the-middle position across your entire organization's traffic. Neon holds no such position. It operates at the browser session layer only, which fundamentally limits the blast radius if a third-party browser extension were ever targeted. Automatic updates, zero IT burden. Browser extension updates propagate automatically through the browser's native update mechanism — no restart required, no IT intervention, no policy changes needed. This means Neon's own attack surface is continuously patched without creating a lag window that attackers could exploit, which is a known risk with enterprise tools that require manual patching cycles. Extension integrity and supply chain risk. Neon is distributed and managed through enterprise-controlled MDM and GPO channels which eliminates the class of supply chain attacks that target publicly listed extensions. Your IT team controls deployment, versioning, and removal centrally.