We’ve been using Cortex Cloud for a few months now, and it’s honestly been a game changer for how we manage service ownership and operational maturity across teams. The service catalog gives us a clear, centralized view of our microservices, including who owns what and how each service stacks up against our internal standards.
One thing I really like is the scorecard system — it helps us track things like SLO compliance, runbook links, and security checks in a way that’s visible and actionable without adding process bloat. It’s made some of our security and compliance reporting way easier.
Setup took a bit of effort, especially getting all the integrations in place, but once it’s up and running, it’s low-maintenance and easy to keep updated. We’ve tied it into GitHub, PagerDuty, and some of our CI tools, and the visibility it gives us is solid.
If you’re trying to get more structure around service ownership, or just reduce the back-and-forth between engineering and ops, Cortex is definitely worth looking into. Review collected by and hosted on G2.com.
Cortex Cloud offers a lot of value, but getting started can be challenging. The setup process, especially around configuring integrations and defining scorecards, isn’t exactly plug-and-play—it requires a good amount of upfront effort and familiarity with your internal systems.
In terms of flexibility, some areas like scorecard customization or UI tweaks feel a bit limited unless you reach out to their support team. For organizations with unique workflows, this can slow down full adoption.
Also, the pricing structure isn’t very clear upfront, which makes it harder to evaluate the platform without going through a sales cycle.
That said, once it’s properly configured, it becomes a really effective tool for driving service maturity and visibility across teams. Review collected by and hosted on G2.com.
