Who Openwake is for.
The same platform, entered from the question your team asks first.
AI and agent governance
Your agents delegate, call tools, and reach vendors that route data to model providers. Openwake records who acted for whom, what was sent where, and whether policy allowed it.
Uses: Recorder, Registry, Policies, Evidence. Start with: Wrap one MCP server with Openwake Recorder and open the Live page.
Third-party risk
A vendor list is a snapshot. Openwake keeps the relationship: what each vendor declares, what you signed, what changed, and what your systems actually do with it.
Uses: Registry, Watch, Agreements, Reports. Start with: Import your vendor export and watch the ones that matter.
Vendor change monitoring
Privacy policies, DPAs, AI terms and subprocessor lists change without notice. Openwake re-reads them daily, quotes the change, and starts the potential objection window.
Uses: Watch, Registry, Evidence. Start with: Watch five vendors free; alerts arrive by email within a day of a change.
Shadow SaaS and AI
Nobody put Perplexity behind SSO. Openwake Scout sees the AI tools, MCP servers and model keys actually present on your machines and maps them to the Registry, without reading anyone's content.
Uses: Scout, Registry, Footprint. Start with: Run Openwake Scout on one machine and look at the footprint.
Privacy and data protection
Article 30, SOC 2 vendor management, DORA: every one asks what you knew and when. Openwake's record is cited, versioned and independently verifiable.
Uses: Registry, Watch, Agreements, Reports, Evidence. Start with: Export the data-flow summary and an evidence pack for one vendor.
MSPs and vCISOs
One console, many customers. Import each customer's vendor list, watch it, and hand them the Findings and the evidence packs with your name on the report.
Uses: Everything, one workspace per customer. Start with: Start with your own vendors, then add a customer workspace.