Documentation
Documentation
This page organizes the technical material available today and lists what doesn't exist yet. It does not pretend an installation guide, configuration reference, or troubleshooting guide already exists — none of them do.
Every page below traces back to KEEP's implemented product and its approved architecture — the same evidence standard applied everywhere on this site, not a separate marketing track. For what's actually built and how thoroughly it's been validated, start at Capabilities.
A note on the "(Source: …)" markers throughout this site: each names the specific internal KEEP document a claim was checked against at the time it was written. That documentation isn't published externally yet, so the marker states what was verified rather than linking to it — if you need a claim confirmed directly, ask us.
Available Now
Available now
The Hub/Spoke architecture, evaluation flow, data flow, and trust boundaries.
What stays local, what reaches the Control Plane, authentication, and evaluation removal.
What KEEP does today, grouped by area and labeled Validated, Evaluation, Planned, or Unknown.
Evaluation prerequisites, what gets installed, what data is collected, and how to end an evaluation.
What creating a KEEP account actually does — and the distinction between an account and Evaluation access. (Source: KEEP Control Plane architecture documentation)
Merlin's capability classes, the credential boundary, and how approval works before anything executes. (Source: Merlin architecture documentation)
Nine diagrams of how KEEP is actually built — boxes, arrows, and trust boundaries, not narrative — with an explicit findings section for where a claim didn't hold up under code inspection. (Source: KEEP architecture documentation)
Planned
Planned documentation
Step-by-step setup for Hub and Spoke deployments, beyond the prerequisites already summarized on Evaluate KEEP. (Source: KEEP architecture documentation)
How to configure SLA targets, alerting, and integrations once a deployment is running. (Source: KEEP architecture documentation)
How to diagnose and resolve common operational issues after deployment.
Unknown