My main use case for Cortex.io is that it provides the centralization of data from all the tools like CI/CD, monitoring, or incident management, making it a single source of truth and giving us a centralized command center for managing the health and reliability of the software services and the teams.

I use Cortex.io as a centralized command center to manage many microservices and engineering squads in a centralized way, which provides a centralized service catalog that centralizes data from all the microservices, allowing us to know who owns each service, its current health, and any documentation gaps.

The best feature Cortex.io offers is visibility, which is most relevant to the teams or services struggling with consistency and operational toil. This visibility gives us complete insight across our entire services and organization, which stands out the most for me.

The visibility feature has helped our teams by resulting in a 75% reduction in mean time to restore, allowing us to get alerts and incident history instead of relying on scattered spreadsheets and unreliable tools, thus saving around 15 to 20 hours per newly created service.

Cortex.io positively impacts our organization not only with visibility but also through its scorecards that grade each service against engineering standards, helping us check for on-call owners, passing tests, and production readiness.

The scorecards feature has changed how our teams work by providing me, as a manager, with a bird's eye view of operational maturity across teams and insight into pending incidents and responsible personnel.

I wish Cortex.io could cater to smaller teams struggling with visibility and operational toil, as a lighter version would be really great.

I believe AI adoption tracking can be enhanced and made more useful, as it currently lags behind market trends, especially in the area of security tracking for AI adoption. I think the interface and support could improve in that field.

I have been using Cortex.io for the last six months.

Cortex.io is very stable.

The scalability of Cortex.io is high.

Customer support is very professional, and I receive complete answers within a fraction of time.

I haven't used any other solution previously.

I deploy Cortex.io using both public cloud and on-premise solutions.

For my public cloud deployment, I use AWS, and for my self-hosted deployment, I utilize Kubernetes plus Helm.

I don't have complete visibility on how Cortex.io was purchased, but I believe it is through AWS Marketplace.

I have been seeing a 70 to 75% reduction in MTTR after using Cortex.io, which is the only metric I can share.

Regarding pricing, it is fair, and the setup cost for the self-hosted version is really simple. I am on a starter deal with five product tiers that include engineering intelligence and DORA matrices. Although I have faced budget restrictions regarding engineering intelligence for renewal, initial setup costs are justified and licensing fees are broadly acceptable in the industry.

Before choosing Cortex.io, I evaluated Spotify Backstage, which I believe is open source, and also looked at Port.io, as these are the two options I discussed or analyzed.

My advice to others looking into using Cortex.io is to start with a service catalog first, as scorecards are the real power feature, and it is beneficial to invest in Cortex Academy early for teams to learn how to use it effectively.

If Cortex.io gets better AI adoption tracking improvements and they provide solutions for smaller setups, that would also enhance its value.

I would rate this product an 8 out of 10 overall. I feel completely satisfied, as I do not have any other improvements needed, and have no additional thoughts about Cortex.io.