|
By Ganesh Datta
This is the fourth post in our DRIVE Deep Dive series. Over the coming weeks we're examining each pillar of the DRIVE framework in turn. For the complete model, download the full DRIVE framework. Our last post covered Initiatives. Up next: Efficiency. The bottleneck on writing code is gone, and the industry is responding the way it always does when a constraint disappears: by producing more.
|
By Ganesh Datta
This is the third post in our DRIVE Deep Dive series. We've covered Delivery and Reliability so far; this post takes on Initiatives. For the complete model, download the full DRIVE framework.
|
By Cortex
You can hit every DORA target and still be losing ground. Deploy frequency up, lead time down, change failure rate and MTTR both healthy, but underneath it could be hiding an organization slowly getting worse at turning work into reliable software. New services shipping without clear owners, an attack surface widening faster than anyone is tracking, on-call rotations quietly filling up, a migration that was supposed to close last quarter still limping along.
|
By Ganesh Datta
This is the second post in our DRIVE Deep Dive series. Over the coming weeks we're examining each pillar of the DRIVE framework in turn, and mapping DRIVE against the frameworks engineering leaders already run on, including DORA and SPACE. For the complete model, download the full DRIVE framework. Our last post covered Delivery. Up next: Initiatives. --- AI has removed the last real constraint on producing code, and organizations are shipping more of it than ever.
|
By Ganesh Datta
This is the first post in our DRIVE Deep Dive series. Over the coming month we'll examine each pillar of the DRIVE framework in turn, and map DRIVE against the frameworks engineering leaders already run on, including DORA and SPACE. For the complete model, download the full DRIVE framework.
|
By Skyler Wuolle
Incident response is a context problem. The first minutes of any incident are spent reconstructing what the affected service is, what it depends on, and who owns it. That reconstruction happens during the worst possible window. The Cortex catalog already holds this data: services, teams, domains, and the relationships between them, maintained by the engineers who run those systems.
|
By Ganesh Datta
Ask a software engineer what they do and the answer, for years, has been some version of "I write code." That assumption is unwinding fast. AI agents can now write code, review pull requests, run tests, and ship to production, and they're taking on a fast-growing share of that work. As agents absorb more of the execution, the human role shifts.
|
By Ganesh Datta
Most engineering organizations already run something they call an operational review. It usually looks like a cousin of the quarterly business review: a deck assembled every few months, walked through team by team, anchored on whatever incidents happened to land in the previous quarter. By the time leadership sees the data, the systems it describes have moved on and the next set of risks is already accumulating in the gap.
|
By Ganesh Datta
Engineering leadership is in the middle of a real transition, and most of the leaders I talk to know it. AI has reshaped how software gets built quickly enough that the operating models many of us spent a decade refining no longer fit cleanly, and there is a great deal of serious work happening across the industry to figure out how these models should evolve. The teams I find most impressive right now are the ones treating their operating model as an open question rather than a settled one.
|
By Cortex
AI changed how code gets written before it changed how code gets operated. Generation accelerated; the downstream controls that turn that output into reliable, secure software at a reasonable cost did not keep pace. The result is elevated risk, distributed unevenly across engineering organizations. A recent survey explains why the distribution is so uneven.
In this video, Becka gives a guided tour of Cortex, the Engineering Operations Platform that runs mission control for your AI software factory. Learn how to centralize visibility, clarify ownership, and automate standards across your entire software ecosystem. What we cover: Why Cortex: Cortex is where engineering leaders run mission control for the AI software factory: the visibility, intelligence, and controls to keep teams shipping fast without letting accelerated output turn into accumulated risk to reliability, security, and cost.
The World Cup is down to the final two, and so is Cortex's Coming Home Dashboard. In this Feature Friday, VP of Strategic Initiatives & Marketing Cristina Buenahora walks through an update on the Coming Home Dashboard she and Edward Spencer built a month ago, and the product update behind it. What she covers: Whether you're tracking brackets or tracking engineering maturity, the view's the same. Reach out to your CSM to try it.
Cortex co-founder and CTO Ganesh Datta sits down with Dr. Martin Nettling, Senior Director of Engineering and Head of QA at Tealium, to explore the distinction between trusting people and having confidence in tools, and why that difference matters as AI becomes part of every engineering workflow.
In this video, Becka gives a guided tour of Cortex, the Engineering Operations Platform that runs mission control for your AI software factory. Learn how to centralize visibility, clarify ownership, and automate standards across your entire software ecosystem.
Most engineering metrics track individual output. DRIVE measures the health of the system as a whole. In this Feature Friday, Director of Customer Education and Delivery Taylor Schmidt walks through Cortex's DRIVE scorecard and dashboard, a framework covering five pillars: delivery, reliability, initiatives, vigilance, and efficiency.
Stop guessing whether your repos meet your branch policies. Start knowing. In this Feature Friday, Senior Engineering Manager Gabriel walks through Cortex's new native support for GitHub branch rule sets and how to use them in scorecards to enforce consistent policies across all your repos. What you'll see: Questions? Reach out to your CSM or drop a comment below.
Cortex co-founder and CTO Ganesh Datta sits down with Shawn Burke, Distinguished Engineer at Cortex, to explore what separates an operational excellence review that drives real engineering behavior from one that produces great conversation and nothing else. Shawn draws on experience from SoFi, Uber, and Microsoft to explain why these reviews so often fail—and how to build a process that actually sticks.
Cortex co-founder and CTO Ganesh Datta sits down with Dinesh Sukhija, Director of Engineering at Okta, to discuss how AI is reshaping the relationship between platform engineering, SRE, and security.
Cortex Workflows can now be triggered externally via the Workflows Run API (beta). In this video, Solutions Architect Jeff Schnitter walks through how to trigger a workflow from the Cortex CLI, pass context via a JSON file, and run synchronously or asynchronously. Requires CLI v1.15.0+ and the "runnable via API" toggle enabled on the workflow. To enable the Workflows Run API in your workspace, contact your CSM.
- July 2026 (10)
- June 2026 (11)
- May 2026 (8)
- April 2026 (16)
- March 2026 (17)
- February 2026 (7)
- January 2026 (9)
- December 2025 (13)
- November 2025 (16)
- October 2025 (19)
- September 2025 (11)
- August 2025 (4)
- July 2025 (6)
- June 2025 (4)
- May 2025 (6)
- April 2025 (6)
- March 2025 (10)
- February 2025 (3)
- January 2025 (14)
- December 2024 (5)
- November 2024 (4)
- October 2024 (5)
- September 2024 (9)
- August 2024 (6)
- July 2024 (6)
- June 2024 (6)
- May 2024 (7)
- April 2024 (6)
- March 2024 (8)
- February 2024 (4)
- January 2024 (8)
- December 2023 (6)
- November 2023 (7)
- October 2023 (10)
- September 2023 (8)
- August 2023 (6)
- July 2023 (3)
- June 2023 (3)
- May 2023 (5)
- April 2023 (3)
- March 2023 (5)
- February 2023 (4)
- January 2023 (5)
- December 2022 (6)
- November 2022 (8)
- October 2022 (8)
- September 2022 (4)
- August 2022 (1)
- May 2022 (2)
- January 2022 (1)
Cortex makes it easy for engineering organizations to gain visibility into their services and deliver high quality software.
Cortex helps engineering teams build better software at scale:
- Align your team and drive accountability: Scorecards enable teams to drive what matters most to them – including service quality, production readiness standards, and migrations.
- A single source of truth for your services: Cortex’s service catalog integrates with the most popular engineering tools, giving teams an easy way to understand everything about their architecture.
- Build a culture of reliability and high performance: Teams enable organizations to drive a sense of ownership and pride as they improve service quality.
- Ensure new services follow best practices from day one: Scaffolder lets developers scaffold a new service in less than five minutes using custom templates crafted by your team.
Cortex gives organizations visibility into the status and quality of their microservices and helps teams drive adoption of best practices so they can deliver higher quality software.