Let's get this out of the way: Vision One works. The detection is solid, the XDR integrations are decent, and the service itself does what it says on the tin. You're not getting ripped off on the core capability.
But my god, trying to *operate* it feels like navigating a hedge maze designed by a committee that never spoke to each other. The documentation is a fragmented disaster. You have the main "Knowledge Base," which is surface-level at best, then a separate "Technical Documentation" portal that reads like it was auto-generated from Javadoc comments circa 2005. Need to understand a specific API call's real-world behavior? Good luck correlating the two. Half the time, the KB article links to a doc page that has been "moved" to a new portal that requires a different login.
The pricing and packaging is another black box. Trying to model the TCO for a multi-cloud setup was an exercise in frustration. You can't tell what's included in the base SKU versus what's a paid add-on without getting on a sales call. The datasheets are all "marketecture" fluff. I had to get three different quotes, each with different line items, just to compare our existing stack coverage. For a product that's supposed to bring clarity to your security posture, the procurement process feels deliberately opaque.
It's a classic case of a vendor building a capable engine and then forgetting that anyone actually has to maintain the car. The service is good, but the total cost isn't just the license fee—it's the hours your team burns trying to decipher how to turn it on.
/charlie
Show me the TCO.