What our customers are saying
How Brex drove reliability standards with Scorecards and reports
"Prior to Cortex, we had a lot of best practices and standards scattered across our knowledge bases as documentation, but it was impossible to track what services were following the standards that we had defined. It was often the case that incidents would be caused by assumptions that these standards are being followed throughout our software, when in actuality this was not always true, especially for legacy services."
How LetsGetChecked doubled deployment frequency and slashed MTTR with Cortex
“Cortex makes action obvious for devs, helping them stay focused on priorities, and saving me 4-5 hours a week following up. In the case of our Kubernetes migration, the ability to drive timely action cut our projected timeline from 24 months down to 16—enabling us to capture savings 8 months earlier.”
How the cloud team at 8x8 gained visibility into service maturity with Cortex
“Cortex is one of those things where it’s like, you’d never know you needed it until you had it. And as soon as you have the service catalog, you’re like, ‘How did we live without this thing?'"
How Cortex helps SolarWinds ensure the security and reliability of their latest product
"Cortex helps unite our organization in defining cross-cutting standards of excellence. Using Cortex to provide standards to developers has minimized performance and quality issues, increasing the overall reliability of our products."
How Pismo built a road to visibility in a complex microservices ecosystem
“Combining Scorecards with dependency graphs allows us to identify where we should prioritise our efforts to improve our services and, consequently, the whole Pismo banking and payments platform. So our squads have a tool that helps them in the decision-making process, providing a basis for choosing backlog activities for the next sprints.”
How ShareChat improved visibility into its services
“Cortex has tremendously helped with the visibility and discoverability of service info. It’s very easy for a new engineer to learn more about the services they own and their downstream dependencies. We can understand what a service is calling, who it’s owners are, and where the documentation lives in one single dashboard.”