I may be biased as a co-founder of Spike.sh, but I think we have one of the best designed incident management products out there. We've focused on making it easy to create on-call schedule and overrides, and added templates for escalation, on-call and alert rules.
SRE is one of the hottest roles in startups and enterprises right now. But the job responsibilities and scope can change from company to company. We wanted to see what were the top expectations in the SRE role, so we analyzed 30 job postings from Google, Airbnb, Coinbase etc. to find out.
"It looks like this service does require password for sign-up and login right now unless you use google auth?"
We have implemented magic link in our new product, also as a way to trying out the tech and understanding user feedback. Appreciate your comments and a lot of great feedback from the discussion on this post in general.
I agree to some extent. Unless you can filter the feedback based on the level of the user (plan, MRR from account, user engagement), it can result in some lower importance features being built. Also, making the roadmap public reduces the product team's flexibility to an extent.
I may be biased as a co-founder of Spike.sh, but I think we have one of the best designed incident management products out there. We've focused on making it easy to create on-call schedule and overrides, and added templates for escalation, on-call and alert rules.