Thanks! Hard to make a comparison to Cleric since their site doesn't really have any features or a demo. Onegrep is a fellow YC company, and we love what they're building! They seem to be more focused on workflows and pulling together context (also a very important problem in the space), we we've put more of a focus on root causing infra issues specifically. Resolve seems to come from the same category as Temporal, which are more traditional automation platforms. These end up being somewhat rigid tools in that you have to very explicitly define each step and they require a certain level of CI/CD or monitoring sophistication to be useful. Using LLMs allows us to relax these requirements and follow workflows like an actual engineer would.
I haven't heard of Beeps and can't find it, could you share the URL?
> They seem to be more focused on workflows and pulling together context (also a very important problem in the space), we we've put more of a focus on root causing infra issues specifically.
So just to clarify, are you saying that Parity is focused on infrastructure issues, while something like Onegrep addresses the broader problem by providing context?
> I haven't heard of Beeps and can't find it, could you share the URL?
Yes, my understanding is that Onegrep is meant to provide context from your documentation and past incidents, which can be helpful when trying to solve an alert. We're focused on root-causing underlying infrastructure issues by actually looking into the logs/configurations/metrics.
Ah I actually did see beeps a while back. I haven't tried their product, but they seem to be similar to rootly/Onegrep in that they're working on on-call management/post-mortems
I haven't heard of Beeps and can't find it, could you share the URL?