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)
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
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?
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.
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.
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.
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)
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
We will check the Cloudwatch integration, thanks!
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
providers are usually driven by the community! happy to collaborate on that provider if you’d like.
Congrats on launching.
$1/alert/month???
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?
Small typo on your "Mapping" page "Enirch alerts with more data from Topology, CSV, JSON and YAMLs"
thank you for that! fixed in https://github.com/keephq/keep/issues/2681
Damn, answering feedback with a pr link is fireeee
trying to keep that high pace!
I love me some worfklows. Please keep this typo…pretty please? :)
haha! gotta fix those for my ocd: https://github.com/keephq/keep/pull/2684 ^^'
At least it will be preserved in the PR title.
Looks great! What about some Zapier support?
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/
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
Interesting! What type of integration do you imagine?
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.
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.
Ok, I've taken "open source" out of the title now. The definitional argument here isn't really on topic.
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.