Helm.sh
Kubernetes
Rancher
Docker Compose
Google App Engine
Amazon S3
Kustomize
AWS Elastic Beanstalk
Rootly
incident.io
Scoutflo
FireHydrant.io
Better Stack
Pulsetic
Pagerly.io
Sonarly
RootlyNo Rootly videos yet. You could help us improve this page by suggesting one.
Based on our record, Helm.sh seems to be a lot more popular than Rootly. While we know about 181 links to Helm.sh, we've tracked only 17 mentions of Rootly. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I know there's no such thing as a unique name anymore, but https://helm.sh/ is rather popular. - Source: Hacker News / 3 months ago
Self-managed BYOC is the highest-control option. The vendor distributes their software as binaries, container images, Helm charts, or Terraform modules, and the customer's platform engineering team handles the full operational lifecycle. This model is common among organisations with strict air-gap or no-internet requirements, teams that need deep customisation of configuration and network topology, and regulated... - Source: dev.to / 4 months ago
Helm 4 is the most significant release since Tiller was removed. New templating engine, dependency resolution changes, and the question everyone's asking: what breaks? The maintainers themselves walk through the migration path. - Source: dev.to / 4 months ago
Ready to try it out? Getting started with the operator is straightforward. You can use a local Kubernetes cluster such as minikube or kind and use Helm for installation. - Source: dev.to / 8 months ago
To get to a working deployment of the proposed app, though, you would probably need to learn at least a dozen different k8s concepts. Hereโs a short list of what you might need: a Deployment to describe Pods in a ReplicaSet along with a Service, Ingress and Ingress Controller to hook up your domain. Helm to install Cert Manager so you can get SSL working. Youโll likely need to learn about plenty more along the way. - Source: dev.to / 8 months ago
A copilot inside Rootly, incident.io, FireHydrant, or Datadog Bits AI drafts Slack updates, suggests on-call swaps, and writes a postmortem from artefacts the team has already produced. An AI SRE generates the evidence those artefacts describe. The two categories cooperate; they do not substitute. See our AI SRE vs traditional incident management comparison for the long form. - Source: dev.to / about 2 months ago
Rootly is an incident management platform designed to reduce manual work and streamline collaboration by meeting engineers where they work: in Slack. It focuses heavily on automating the entire incident response process, from creation to postmortem. - Source: dev.to / 12 months ago
- Opsgenie comparison (features): https://rootly.com/comparisons/opsgenie-vs-rootly-on-call. - Source: Hacker News / over 1 year ago
This looks great and cool to see more innovation in the space. We've been using Rootly https://rootly.com and love it. - Source: Hacker News / almost 4 years ago
This ultimately led me to build https://rootly.com/ to make managing incidents and outages easier :). Source: almost 4 years ago
Kubernetes - Kubernetes is an open source orchestration system for Docker containers
incident.io - Create, manage and resolve incidents directly in Slack. Leave the rest to us.
Rancher - Open Source Platform for Running a Private Container Service
Scoutflo - The first-ever commercial open-source marketplace.
Docker Compose - Define and run multi-container applications with Docker
FireHydrant.io - FireHydrant helps teams organize and remedy incidents quickly when their system experience disruptions.