How keephq/keep works
Keep is an AIOps and alert-management platform: monitoring integrations send events into Keep, where alerts can be normalized, deduplicated, enriched, filtered, and correlated into incidents; operators investigate them in the UI and automate responses with workflows. The repository also includes dashboards, topology, maintenance, and identity management. The graph combines documented product capabilities with relationships visible in sampled source and the source index; several UI and backend subsystems are represented at directory level because their implementation was not sampled.
Main entry points: db.py Application database · (keep) Keep web UI · rulesengine.py Rules engine · workflowmanager.py Workflow manager
Components 20
Alert processing
- Provider integrations
keep/providers - Alert models
keep/api/models/alert.py - Rules engine
keep/rulesengine/rulesengine.py - Alert enrichment
keep/api/utils/enrichment_helpers.py - Alert search
keep/searchengine/searchengine.py - Incident models
keep/api/models/incident.py
Integrations and automation
- Workflow manager
keep/workflowmanager/workflowmanager.py - Workflow IO
keep/iohandler/iohandler.py
Operator experience
- Keep web UI
keep-ui/app/(keep) - Alert views
keep-ui/app/(keep)/alerts/[id]/page.tsx - Incident workspace
keep-ui/app/(keep)/incidents/[id] - Dashboards
keep-ui/app/(keep)/dashboard - Service topology
keep/topologies/topologies_service.py
Platform services
- Application database
keep/api/core/db.py - Execution context
keep/contextmanager/contextmanager.py - Identity and access
keep/identitymanager/identitymanager.py - Request verification
keep/identitymanager/authverifierbase.py - Identity selection
keep/identitymanager/identitymanagerfactory.py
Other components
- Monitoring tools
- Integrated services
Connections 22
- Monitoring tools → Provider integrations: sends events
README.md - Provider integrations → Alert models: supplies alerts
keep/providers/incidentmanager_provider/incidentmanager_provider.py - Rules engine → Application database: reads and writes
keep/rulesengine/rulesengine.py - Rules engine → Incident models: creates incidents
keep/rulesengine/rulesengine.py - Rules engine → Alert enrichment: uses enrichment
keep/rulesengine/rulesengine.py - Alert search → Rules engine: queries rules
keep/searchengine/searchengine.py - Alert search → Application database: queries alerts
keep/searchengine/searchengine.py - Incident models → Application database: reads and writes
keep/api/models/incident.py - Keep web UI → Alert views: presents alerts
- Keep web UI → Incident workspace: presents incidents
- Keep web UI → Dashboards: presents dashboards
README.md - Alert views → Alert search: filters alerts
- Incident workspace → Incident models: manages incidents
- Workflow manager → Execution context: uses context
keep/workflowmanager/workflowmanager.py - Workflow manager → Workflow IO: dispatches steps
keep/workflowmanager/workflowmanager.py - Workflow manager → Application database: stores executions
keep/workflowmanager/workflowmanager.py - Workflow IO → Provider integrations: invokes providers
keep/iohandler/iohandler.py - Workflow IO → Integrated services: calls integrations
README.md - Service topology → Application database: reads and writes
keep/topologies/topologies_service.py - Keep web UI → Service topology: explores topology
- Identity selection → Identity and access: selects manager
keep/identitymanager/identitymanagerfactory.py - Request verification → Identity and access: verifies identity
keep/identitymanager/authverifierbase.py