nkozmoyan

Plans on Proberix include features like full-page rendering and change detection alongside HTTP checks.

Full-page rendering, which basically mimics an actual browser to also help test websites that are client-side rendered, is computationally expensive, unlike simple HTTP checks that are good for server-side rendered pages.

The Change Detection feature, which diffs large HTTP responses between two checks, uses a lot of computing power.

You are definitely talking to a person and I have worked as a UX specialist at a monitoring company (about 100 people) my whole career. The majority of the time, I was battling why we should invest long term to create lovable products rather than do "growth hacking" and draw immediate metrics for investors. This was the reason I decided to start a new company, knowing well how saturated the market is in this area. Trust me, I have repeatedly found myself asking the above question. It may sound poetic or like ChatGPT because I didn't want to bring a comparison of features. Rather, I wanted to give a high-level motivation.

That’s a very valid question.

Having been part of the product team at an established monitoring company, I witnessed firsthand how services can spiral into complexity following investments or acquisitions, with a new focus on appealing to investors or shareholders rather than meeting user needs. This shift often leads to bloated features, unnecessary upsells, and an overarching emphasis on business metrics at the expense of user experience. With Proberix, my goal is to cut through that noise, offering human-centric approach that prioritizes simplicity.