← Directory

Keep

Keep is an open-source AIOps (AI for IT operations) platform that gives SREs, operators, and engineering teams a single pane of glass for all their alerts and…

  • AI
  • Automation
  • Monitoring & Logging
Keep is an open-source AIOps (AI for IT operations) platform that gives SREs, operators, and engineering teams a single pane of glass for all their alerts and incidents. It provides alert deduplication, enrichment, filtering, and correlation, along with bi-directional integrations to 90+ monitoring tools and automated workflows that bring GitHub Actions to your monitoring stack. Use Keep to cut alert noise, accelerate incident response, and leverage AI-powered summarization in complex, multi-tool environments.

Platform availability

Available on 0 of 9 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

74/100 Good

Maintained
100last commit 14 days ago
Popular
8212,393 GitHub stars
Easy to install
150 install platforms, install notes
Light to run
No data
Security check
70no serious findings, 10 minor, CI, tests

Based on 4 of 5 factors.

GitHub stars
12,393
Open issues
654
Last commit
2026-09-28
Latest release
v0.54.3
Activity
declining

Checked today - source: GitHub (keephq/keep)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Add a UI secret before starting Copy keep-ui/.env.local.example to keep-ui/.env.local and add NEXTAUTH_SECRET with a random string that helps Keep secure logins. Without it, the web UI may have login problems or weak session security. source
  • Test Keep with a sample workflow After the UI is running, apply a sample workflow file, such as keep workflow apply -f examples/workflows/query_clickhouse.yml. This checks that your Keep installation can receive and display workflows from files. source
  • Start local Llama.cpp if using AI If you want local AI answers, start the Llama.cpp server with the correct model path and make it reachable on port 8080. A wrong path or blocked port will stop the AI feature from connecting to Keep. source

Fetched today - each note links to its source

Alternatives (4)

Checked today - source: AlternativeTo

Common questions

What UI secret is required before starting Keep?

Copy the example UI environment file and set NEXTAUTH_SECRET to a random string. Without it, the web UI may have login problems or weak session security.

What configuration is needed for local Llama.cpp AI answers?

Start the Llama.cpp server with the correct model path and make it reachable on port 8080. An incorrect path or blocked port prevents Keep from connecting to the AI feature.

How can I verify that Keep accepts file-based workflows?

After the UI is running, apply a sample workflow file with the Keep CLI. This checks that the installation can receive and display workflows from files.

How do I request a missing monitoring integration?

Submit a new provider request using the provider request template in the Keep GitHub repository.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected today - public community threads