awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
keephq avatar

keephq/keep

0
View on GitHub↗
keephq.dev↗

Keep

Keep is an open-source AIOps alert management platform that aggregates, deduplicates, and orchestrates the lifecycle of alerts from multiple monitoring tools. It functions as a multi-provider integration hub to centralize the flow of data between observability, ticketing, and communication tools.

The platform distinguishes itself through incident workflow automation and AI-powered enrichment. It uses a declarative workflow engine to execute multi-step operational sequences and integrates large language models to summarize event data and correlate technical logs for faster incident resolution.

The system provides broader capabilities for unified alert routing and bi-directional state synchronization across external platforms. It includes a containerized observability stack for telemetry and employs role-based access control and database-backed authentication to secure system entry.

The platform is deployed as a series of containerized services, including frontend, backend, and websocket layers.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Features

  • Alert Managers - Functions as an alert manager that routes and groups system alerts from multiple monitoring tools based on defined rules.
  • Multi-Provider Integration Hubs - Functions as a multi-provider integration hub to centralize the flow of data between observability, ticketing, and communication tools.
  • Notification Deduplication - Filters redundant notifications by grouping related events into single incidents to reduce alert noise.
  • Alert Correlation - Filters and groups redundant notifications while linking related events to reduce noise and identify root causes.
  • Bi-Directional State Synchronizations - Maintains consistent data across ticketing and communication tools by mapping lifecycle events to remote API updates.
  • Observability Tool Synchronizations - Maintains bi-directional data flow with observability and communication platforms to ensure external systems remain synchronized.
  • Integration Abstraction Layers - Implements an integration abstraction layer to standardize third-party API communications from observability tools.
  • Workflow Logic Engines - Uses a workflow logic engine to execute multi-step operational sequences based on predefined logic rules.
  • Alert Routing - Coordinates the routing and response of system alerts to appropriate teams and communication channels.
  • Alerting Systems - Consolidates alerts from multiple monitoring tools into a single interface to provide a unified view of incidents.
  • Ticketing System Synchronizations - Integrates with ticketing systems to automatically create and update records based on alert lifecycle events.
  • AI-Powered Enrichment - Integrates large language models to summarize event data and correlate technical logs for faster incident resolution.
  • Automated Incident Response Workflows - Implements automated incident response workflows to gather technical context and execute responses when alerts fire.
  • Alert Management Systems - Provides a complete alert management system that aggregates, deduplicates, and orchestrates the lifecycle of alerts.
  • Automated Alerting Workflows - Defines declarative triggers and multi-step sequences to automatically process alerts and execute operational responses.
  • Alert Context Enrichers - Provides capabilities to fetch additional technical details and business context from external tools to enrich active alerts.
  • Notification Routing Platforms - Dispatches alert and incident updates to various communication platforms and messaging services to keep teams informed.
  • LLM Contextual Integrations - Integrates large language models to summarize event data and correlate technical logs for automated analysis.
  • AI-Powered Incident Analysis - Leverages large language models to summarize events and correlate data for faster technical incident resolution.
  • Observability Tool Synchronization - Syncs incident states and alert data bi-directionally between monitoring platforms, ticketing systems, and communication tools.
  • Observability and Monitoring - CLI tool for managing and routing infrastructure alerts.
11,938 stars·1,410 forks·Python·71 views

Star history

Star history chart for keephq/keepStar history chart for keephq/keep

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

Frequently asked questions

What does keephq/keep do?

Keep is an open-source AIOps alert management platform that aggregates, deduplicates, and orchestrates the lifecycle of alerts from multiple monitoring tools. It functions as a multi-provider integration hub to centralize the flow of data between observability, ticketing, and communication tools.

What are the main features of keephq/keep?

The main features of keephq/keep are: Alert Managers, Multi-Provider Integration Hubs, Notification Deduplication, Alert Correlation, Bi-Directional State Synchronizations, Observability Tool Synchronizations, Integration Abstraction Layers, Workflow Logic Engines.

Which projects share features with keephq/keep?

Projects with overlapping indexed features include: victoriametrics/victoriametrics — VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term… prometheus/alertmanager — Alertmanager is a monitoring notification gateway and routing service that deduplicates, groups, and directs alerts to… ccfos/nightingale — Nightingale is a Prometheus-compatible monitoring and alerting platform designed to centralize telemetry management… stefanprodan/dockprom — dockprom is a monitoring stack based on Prometheus and Grafana designed to track the performance of Docker containers… apache/hertzbeat — HertzBeat is an agentless monitoring platform designed to collect performance metrics from network devices, databases,… hyperdxio/hyperdx — HyperDX is an OpenTelemetry observability platform that provides centralized log management, distributed tracing, and…

Projects sharing features with Keep

These projects share indexed features with Keep. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • victoriametrics/victoriametricsVictoriaMetrics avatar

    VictoriaMetrics/VictoriaMetrics

    16,343View on GitHub↗

    VictoriaMetrics is a high-performance, scalable time series database and observability platform designed for long-term storage and analysis of metric, log, and trace data. It functions as a unified backend for monitoring ecosystems, offering full compatibility with industry-standard protocols and query languages. The system is built to handle massive data volumes through a distributed architecture that supports horizontal scaling and efficient data lifecycle management. The platform distinguishes itself through a storage engine that utilizes consistent hashing for data sharding and log-struct

    Godatabasegrafanagraphite
    View on GitHub↗16,343
  • prometheus/alertmanagerprometheus avatar

    prometheus/alertmanager

    8,356View on GitHub↗

    Alertmanager is a monitoring notification gateway and routing service that deduplicates, groups, and directs alerts to the correct receivers. It functions as a central manager for Prometheus alerts, using a hierarchical routing tree and label-based matchers to dispatch notifications to external services. The system employs a peer-to-peer mesh network to coordinate multiple instances in a high availability cluster, ensuring continuous alert processing. It features a dedicated inhibition engine and grouping mechanisms to reduce notification noise by suppressing redundant alerts when related iss

    Goalertmanagerdeduplicationemail
    View on GitHub↗8,356
  • ccfos/nightingaleccfos avatar

    ccfos/nightingale

    13,108View on GitHub↗

    Nightingale is a Prometheus-compatible monitoring and alerting platform designed to centralize telemetry management across multiple time-series databases. It functions as a multi-source alerting engine and metric data pipeline that ingests telemetry via remote write protocols and triggers alarms based on data from sources such as Prometheus, Elasticsearch, Loki, and ClickHouse. The system is distinguished by its automated alert healing system, which executes predefined scripts and RPC-based corrective actions when monitoring thresholds are breached. It supports distributed alert processing, a

    Goalertingccfmetrics
    View on GitHub↗13,108
  • stefanprodan/dockpromstefanprodan avatar

    stefanprodan/dockprom

    6,560View on GitHub↗

    dockprom is a monitoring stack based on Prometheus and Grafana designed to track the performance of Docker containers and their underlying hosts. It functions as a complete solution for gathering real-time metrics and displaying them through a self-hosted dashboard. The project includes a suite of tools for collecting container and host metrics, as well as a discovery tool specifically for automatically identifying and adding tagged EC2 instances to the monitoring configuration. The system covers several observability areas, including time-series data storage and the creation of performance

    View on GitHub↗6,560
Compare all 30 related projects→