KEEP Know · Evaluate · Enforce · Protect
Built for Managed Service Providers
This site is organized as one path for evaluating KEEP, in order: why it exists, how it works, what happens to your data, what it does today, and how to start — and end — an evaluation.
Start here 1 Why KEEP The problem KEEP addresses, and who it's built for. 2 How KEEP Works The Hub/Spoke architecture, evaluation flow, and trust boundaries. 3 Merlin The single AI identity inside KEEP, and how it's governed. 4 Security & Data Ownership What stays on your own infrastructure, and what reaches KEEP. 5 Capabilities What KEEP does today, labeled Validated, Evaluation, Planned, or Unknown. 6 Evaluate KEEP What to expect from an evaluation, start to finish. 7 Documentation Technical reference material, organized by what exists today.