Thanks for sharing this perspective, stressing the relative value of predictability.
Of course, when things go pear-shaped the last thing you want to discover is that your monitoring pipeline doesn't work as expected. We feel you.
Your skepticism is justified and I'm super happy to see that here. We know that our future users are (and should be) quite demanding with respect to robustness of the platform.
We're not naively assuming that it's easy to build a platform that is highly available, auto-scaling, and generally worry-free.
In fact, based on our experience, we really know that we'll have to invest an incredible amount of engineering effort in order to make things super reliable and predictable. On the other hand, by making some smart decisions we can get far with little effort. We have super strong building blocks that we can rely on (such as using a cloud-provided database for storing critical configuration state).
> If you folks believe I can achieve this functionality on a per-seat basis I'd be interested in saving those six figures.
The bet is on, but of course we need a bit of time :)