First seen Nov 10 · 1 event
Henryk Koval reached OpenAI on NW-SALES-03.
Openwake shows which AI tools people use at work, by person and machine, labels the kind of data sent to each one, and shows what each provider says it does with it.
No keystrokes. No screenshots. No prompt content kept by default. The kind of data is worked out on the machine.
In Chrome, Openwake checks what is about to go to an AI site. It can block an API key or a private key, and warn about customer data or source code sent from a personal account. Pick something to send, then change the mode or the account and try again.
In this demo you choose the account.
After each send, this says what happened and what the admin sees.
A simulation in your browser. Nothing you type leaves this page. The real control works in Chrome only. Only API keys and private keys are ever blocked. AKIAIOSFODNN7EXAMPLE is AWS's documentation example, not a real key.
A domain list shows where traffic went. Openwake shows who sent what kind of data to which provider, and what that provider's own documents say about it.
What the provider publicly promises and what is actually happening on your machines, in one record. The gap between the two is what you write policy about.
What providers say they do, in their own documentation.
What actually happens, in your environment.
Openwake turns activity and classification into one record a reviewer can act on. This one is from the demo organization, as it stands right now.
First seen Nov 10 · 1 event
Henryk Koval reached OpenAI on NW-SALES-03.
Wherever AI gets used, the record has the same parts: the person, the machine, the browser or agent, the provider, and the processors that provider lists in public.
Drawn from the demo organization. Open the demo · What each sensor sees
Sees what is submitted to an AI site in Chrome, and can warn on or block an API key or private key before it is sent.
How the browser sensor worksRuns on Windows, macOS and Linux and shows which AI providers each machine really talks to. It lists the AI tools installed on macOS and Linux, and on macOS reads Claude Code sessions and the MCP servers each tool is set to reach.
How the endpoint sensor worksNo keystrokes. No screenshots. Openwake keeps what kind of data was involved, not what people wrote, unless an owner turns on the Evidence Vault.
What Openwake collectsWhether each vendor says it trains on customer data, who is underneath it, and when its terms last moved, quoted from its own documents. Where a document could not be read, the record says unknown, never zero.
Install Openwake on up to 5 endpoints free and review your first AI activity. After that, Team is $2.50 an endpoint a month. No card required.