Why KEEP
Why KEEP
This page explains the problem KEEP was built to address and the thinking behind its design — not a feature list. For what KEEP does today, see Capabilities; for how it's built, see How KEEP Works.
The Problem
Knowing what devices exist on a network is a different question from knowing whether that network is in a known-good, documented state — and whether that can be shown to whoever needs to see it.
KEEP was built to answer the second question, not just the first. (Source: KEEP product positioning documentation)
The Challenges
The operational challenges KEEP was designed to address
Systems that don't talk to each other
Antivirus tooling, hardware and license records, directory services, and network infrastructure were never designed to share information. Reconciling them into one trustworthy picture typically requires manual, recurring effort.
Evidence is its own separate task
Producing documented evidence of that work — for a client review, an insurance renewal, or an audit — is a recurring task layered on top of doing the work in the first place.
One picture, many networks
An organization responsible for more than one network needs this picture for each one individually, and a way to see all of them at once without losing the separation between one client's data and another's.
(Source: KEEP product positioning documentation)
Design Principles
Design principles that guided KEEP
(Source: KEEP product positioning documentation)
Fit
Who KEEP is intended for
Multi-client MSPs
Managed service providers monitoring more than one client network, who need a single place to see all of them without mixing data between clients. (Source: KEEP architecture documentation)
Single-network IT teams
IT teams or organizations monitoring a single network of their own, without needing a separate client-management layer. (Source: KEEP architecture documentation)
Anyone needing documented evidence
Organizations that need documented, reviewable evidence of their security and compliance posture — for internal use, client reporting, or audit and insurance purposes. (Source: KEEP product positioning documentation)
Boundaries
Who KEEP is not intended for
- Not a helpdesk or ticketing system.
- Not a backup solution — it does not replace dedicated backup tooling.
- Does not certify compliance with any standard. Organizations that need formal certification need a qualified auditor — KEEP is not a substitute for that process.
- Not a large-enterprise IT service-management platform — scoped for MSPs and IT teams managing a bounded set of client networks.
(Source: KEEP product positioning documentation)