Hacker News new | past | comments | ask | show | jobs | submit login
Launch HN: Keep (YC W23) – AIOps and alert management (github.com/keephq)
77 points by talboren 13 hours ago | hide | past | favorite | 30 comments
Hey HN, Matvey, Shahar, and Tal from Keep (keephq.dev) here. Keep lets you easily centralize alerts from any monitoring tool and correlate (manually or AI-based), enrich, deduplicate, filter, and then run automation (such as auto-recovering or ticketing sync). For example, if you have Sentry for your exceptions, Prometheus for metrics, and your cloud provider for logs, you can easily send all the alerts to Keep and get a great interface to run workflows.

Simply check it out yourself at https://playground.keephq.dev or just have a look at our repo https://github.com/keephq/keep

We always had trouble with anything monitoring, observability and alerting, with and without OpenTelemtry. While trying almost every tool out there, we always lacked something and eventually found ourselves building complementary tools that fit our needs.

Keep is like a swiss army knife for alerts - anything from collecting, enriching, correlating, and automating. We have over 90 integrations: anything from alerts, topology (CMDB), ticketing, databases, etc., a GitHub-Action-like interface for your monitoring stack (we did a Show HN for it here: https:///item?id=37381268) triggers manually, cron, alert or incident-based, a smart correlation layer, where we use LLMs or pre-configured rules to correlate alerts into incidents (imagine “DB is down” and plenty of 5XX from other services), opinionated or customized deduplication rules to view only the alerts that matter, extraction and mapping capabilities to extract/add missing bits of information to alerts, a single pane of glass to see and manage everything in one place and batteries-included LLM: chat with your observability data

Tools like BigPanda, Moogsoft, Splunk ITSI, or Datadog Event Management treat AIOps as a side quest – trying to vendor-lock or deploy AIOps for huge enterprises only while we build a tool that can serve organizations of any size.

We are completely open-source (MIT license), and we monetize on a SaaS-managed version and enterprise features: SSO, RBAC, Auditing, 24/7 support, longer retention, and private deployments.

We are excited to share what we’ve been working on for the last year and would love to hear your feedback and opinions!

Hosted Demo: https://playground.keephq.dev

Open Source: https://github.com/keephq/keep

Landing Page: https://keephq.dev






Congratz on the launch! is it relevant for early-stage products with small teams or is it an overkill? we're just kicking our observability tools (Vercel, AWS - ECS infra)

reply


it's definitely relevant for early-stage products who deeply care about realiability. are you already handling some amount of alerts today? there's a bunch of stuff you can do with workflows to automate processes and help your users.

we do integrate with AWS Cloudwatch but not yet with Vercel's observability, but can add that if you want to give it try

reply


We will check the Cloudwatch integration, thanks!

reply


What's an actual use case for this?

reply


for small teams we mostly see workflow automation on their alerts, for bigger teams it’s also unified API for alerts from many tools and single pane of glass for alerts

reply


ok but what problem does this solve that I can't solve with Slack notifs

reply


With slack you lose history and context. Also collaboration is harder. Also if you have some processes/workflows you want to maintain in some GitHub repo and manage as code/gitops, you can’t do it with Slack. Deduplicating alerts is also a thing. Basically it’s a different use case

reply


Thanks for the clarification. Would you be able to provide a concrete example for this product’s differentiated use case

reply


Np! Company A have 4 monitoring tools and 2 IRM’s. Few dozens of alerts per day. They use Keep to streamline their ticketing routing, enriching the ticket from a prod db, some if/else logic. Every month they do some research on the alerts they had last month with slice and dice per team/app/etc.

Company B, with big operations group, use Keep as single pane of glass where NOC dispatch incidents and sync context from every system.

reply


Thanks. The first example painted a better picture

reply


Congrats on the launch!

TIL that BigPanda and Moogsoft solve the same problems which you are trying to solve :)

Would have loved to see SigNoz also in the list of supported integrations

reply


providers are usually driven by the community! happy to collaborate on that provider if you’d like.

reply


Congrats on launching.

reply


Small typo on your "Mapping" page "Enirch alerts with more data from Topology, CSV, JSON and YAMLs"

reply


thank you for that! fixed in https://github.com/keephq/keep/issues/2681

reply


Damn, answering feedback with a pr link is fireeee

reply


trying to keep that high pace!

reply


I love me some worfklows. Please keep this typo…pretty please? :)

reply


haha! gotta fix those for my ocd: https://github.com/keephq/keep/pull/2684 ^^'

reply


At least it will be preserved in the PR title.

reply


Looks great! What about some Zapier support?

reply


$1/alert/month???

reply


actually, it’s 100 workflows, 20 providers and 10 users. important to note that it’s per deduplicated alert and not every event ingested by keep. what got you surprised about this pricing model?

reply


Contrats on the launch, this looks pretty good, interesting, useful, and especially for such a stage, integrated with a ton of things!

If you're taking feature requests, it would be pretty cool if you added support for Nomad[1] as an orchestrator too.

1 - https://nomadproject.io/

reply


Deployment with Nomad should be pretty straightforward following https://github.com/keephq/keep/blob/main/docker-compose.yml or https://github.com/keephq/helm-charts

reply


Interesting! What type of integration do you imagine?

reply


It looks quite interesting, that's said, I wish people would stop calling projects open source when they aren't and most if not all projects here in Show/Launch are open core - same with Keep. You have a proprietary license in the project, with parts of the code with an open source license.

reply


Companies adopt different strategies when building Open Core products. Some aim to keep the Open Source portion minimal, reserving the most valuable features for their paid versions. At Keep, we chose the opposite path—moving nearly everything into Open Source. Our philosophy is that most users should be able to fully benefit from the Open Source version.

While I understand (and share) the caution around licenses, I don’t think this concern applies to Keep. With 99% of our codebase under the MIT license, it’s a far cry from just having "parts of the code with an open source license."

I recommend running Keep locally and comparing the Open Source version to the playground where full version is running. You might find it challenging to spot the differences.

I also reccomend comparing Keep Open Source to BigPanda and Moogsoft. It may be surprising how much of it Keep OSS, real MIT-licensed Keep has.

reply


Ok, I've taken "open source" out of the title now. The definitional argument here isn't really on topic.

reply


Yo! I can say that most of our users are open source users. We are community-driven, and like 95% of the features are open source. It’s true that we need something to monetize on but I really feel that we are an open source company.

reply




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: