OSS Tanbou

centralize monitoring alerts and connect correlation, enrichment, and response workflows

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
12,373
Primary language
Python
License
Not determined
Repository last updated
Sep 28, 2026
On this page

Overview

Keep is an AIOps and alert-management platform that aggregates alerts from observability systems and applies deduplication, filtering, correlation, enrichment, and incident workflows. Provider integrations and declarative YAML workflows can automate tickets, notifications, and operational actions.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Aggregate alerts from multiple sources into one pane

Monitoring and observability providers feed a common UI for searching, filtering, and building incident context.

Sources: [2]

Reduce noise through deduplication, correlation, and AI enrichment

Related alerts can be grouped and enriched, with AI backends such as OpenAI, Anthropic, and Ollama available for context gathering and summarization.

Sources: [2]

Automate responses with declarative YAML workflows

Triggers, steps, actions, conditions, and provider integrations can create Jira tickets, send Slack notifications, or run other operational actions.

Sources: [2]

Best fit

Fits SRE and operations teams with fragmented alert triage

It is relevant when alerts from many monitoring systems need a common model and automated routing or first-response workflows.

Sources: [2]

Before adoption

Do not expose the default Docker Compose stack publicly

The repository's default Compose config sets AUTH_TYPE=NO_AUTH on frontend and backend and includes local fixed secrets. Production deployments need real authentication, secret management, and database configuration.

Sources: [3][4]

Treat MIT core and ee/ Enterprise licensing separately

The root license places non-ee code under MIT, while ee/ requires a valid Enterprise Edition subscription and compliance with Enterprise terms for production use. Do not treat the whole repository as MIT.

Sources: [6][7]

Regression-test integrations when upgrading v0.54.3-era deployments

The v0.54.3 release includes changes across database and Redis settings, Grafana queries, and multiple LLM provider defaults and response handlers, so provider-specific upgrade tests are warranted.

Sources: [5]

Official sources

  1. [1]keephq/keep repository(2026-10-01)
  2. [2]Keep README(2026-10-01)
  3. [3]Keep Docker Compose(2026-10-01)
  4. [4]Keep common Docker Compose settings(2026-10-01)
  5. [5]Keep v0.54.3 release(2026-10-01)
  6. [6]Keep root MIT license(2026-10-01)
  7. [7]Keep Enterprise Edition license(2026-10-01)
Supplemental curator note

Keep centralizes alerts from multiple monitoring systems and connects deduplication, correlation, enrichment, ticketing, notifications, and actions through workflows. Core code is MIT, while ee/ requires a valid Enterprise subscription for production use.

Try it in 3 steps

  1. 1

    Clone Keep

    Fetch the official repository. The default Compose stack is for local evaluation and uses AUTH_TYPE=NO_AUTH.

    git clone https://github.com/keephq/keep.git && cd keep
  2. 2

    Start with Docker Compose

    Start the frontend, backend, and websocket server. Do not expose this default stack publicly; configure production authentication, secrets, and database settings first.

    docker compose up -d
  3. 3

    Open the UI and connect a provider

    Open Keep and connect a monitoring provider to test alert aggregation and workflows.

    Open http://localhost:3000
Check the official README

Growth

Growth trends · Last 30 days

12,373 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
10
Open PRs
199

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • alarm
  • alarms
  • alerting
  • alerts
  • monitoring
  • monitoring-tool
  • python
  • python3
  • aiops
  • workflow-automation
Stars
12,373
Forks
1,524
Watchers
49
Open issues
450
Contributors
196
Owner type
Organization
Primary language
Python
License
Not determined
Repository last updated
Sep 28, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?