Systems | Development | Analytics | API | Testing

The era of the “copilot” is ending. We are moving rapidly toward the era of the autonomous software factory, where autonomous agents don’t just autocomplete our code—they investigate, plan, test, and merge entire features while we sleep. But this shift has exposed a critical flaw in how we consume AI. For the past decade, the default motion for enterprise software has been SaaS. It’s easy, frictionless, and managed by someone else.

Healthcare still runs on generalized treatment protocols, even though every patient is biologically and clinically different. Clinicians often make decisions under time pressure using fragmented data from EHRs, labs, and patient history. That leads to gaps such as delayed diagnoses, trial-and-error treatments, and inconsistent outcomes. At the same time, expectations have changed. Patients now expect healthcare to be as personalized as the rest of their digital experiences.

Enterprise AI teams are laboring under two key pressures: 1) squeeze maximum value out of expensive GPUs and 2) deliver new GenAI experiences faster than competitors. Too often, their ability to deliver is blocked by: The new ClearML running on the Nutanix Kubernetes Platform (NKP) solution is designed to tackle every one of these headaches. Below, we unpack each layer of the stack and explain what it is, why it matters, and how it helps you ship AI both quickly and with cost efficiency.

By combining Fivetran, DuckDB, Claude, and an MCP server with an open data infrastructure, you can enable conversational analytics and talk to your data.

Data analytics and science professions have undergone a dramatic transformation in the last decade. Demand for data talent has risen steadily, but the skills required to succeed in the field have evolved right alongside it. And now AI is a defining variable shaping what the next decade of analytics work will look like. It speeds up routine tasks, gives data access to more business users, and raises new questions about what skills will matter most in the not-so-distant future.

The Model Context Protocol (MCP) is quickly becoming the standard for how large language models connect to enterprise data. As adoption accelerates, engineering teams face a foundational decision: build a custom MCP server from scratch, or adopt an AI data gateway that ships with MCP support, security, and governance out of the box. Both paths have real tradeoffs. This post breaks them down so you can make the right call for your stack, your team, and your risk profile.

Every enterprise moving AI into production is about to face a familiar problem in an unfamiliar form: the cost explosion, but for LLMs. This is *very *similar to what happened with cloud. In the early days of cloud, teams spun up infrastructure with no visibility into who was consuming what. Finance got the bill. Engineering got the blame. No one had the data to make good decisions. It took years of hard-won FinOps discipline to fix that. LLM spend is on the same trajectory *and moving faster*.