Systems | Development | Analytics | API | Testing

There’s a tension building inside most engineering organizations right now, and not many people are talking about it openly. AI has given development teams an extraordinary gift: the ability to build faster than ever before. Features that once took days can be prototyped in hours. Applications that required large teams can now be scaffolded by a handful of engineers with the right tools. By almost every measure of development velocity, we are living through a remarkable moment.

AI solves the velocity problem, but confidence is still holding testing teams back.

Observability is the key to understanding and improving MCP servers. These servers connect AI agents to tools, but without visibility, issues like slow responses, errors, or security risks can go undetected. Observability helps track how agents interact with tools, pinpoint failures, and optimize performance.

Over 1,000 people around the world tuned in as Tricentis CEO Kevin Thompson and VP of AI David Colwell unveiled our new integrated platform, followed by a live demo from Enterprise Solution Architect Matt Serpone. From our headquarters in Austin, Texas, we unveiled a unified solution designed to help enterprises treat quality as a coordinated system rather than a collection of disconnected tools.

Your AI coding agent just made every test pass. Ship it, right? Not so fast. A growing class of AI-generated bugs doesn’t come from writing bad code. It comes from the AI changing working code to accommodate its own mistakes. This isn’t a theoretical risk. It’s happening now, in production codebases, and it’s harder to catch than any bug the AI might introduce from scratch.

You can build Data Apps inside Keboola with Kai. But what if you prefer working with Keboola via MCP, in Claude Code, Cursor, or another AI-powered editor? Want to build a JavaScript Data App that Kai doesn't support yet? That's what the Keboola AI Kit is for. It's a set of skills you install into your agent so it knows how to work with Keboola - how to query your data, how to structure a Data App, how to deploy it. Here's how to set it up.

Most teams building AI agents start with HTTP streaming. It's the right starting point. Every major agent framework defaults to it, it gets tokens on screen fast, and for a single-user prompt-response interaction it works well. The question is when it stops being enough - and how to recognise that before it turns into user experience problems, engineering waste, and technical debt that constrains what your product can do.

HTTP streaming – the default transport underneath every major agent framework – was never designed for sessions that survive a tab close or hand off cleanly between participants. Two failures surface consistently in production CX products because of this. Both generate support tickets about conversation state and prompt quality. Both trace to the transport layer. The scenario that illustrates them: a customer contacts support about an order that's partially shipped and partially stuck.

Every major layer of the AI stack now has a name. Model providers - OpenAI, Anthropic, Google - handle inference. Agent frameworks - Vercel AI SDK, LangGraph, CrewAI - handle orchestration. Durable execution platforms like Temporal make backend workflows crash-proof.