50 posts tagged with "Platform"

The MCP server that shipped in v0.12 accepted exactly one credential: a personal API token, in a header. That works for a client you run yourself — Claude Code, the CLI — and it cannot work for a hosted one, which has no way to be handed a token you minted. Which is to say it could not serve the client the module's whole warning was written for.

The hub can now act as an OAuth 2.1 authorization server.

Reading what your models cost is not the same as being able to act on it. This release closes that gap — and it opens by fixing a way of reading those spans that turned out to be wrong.

avuru obs has known a great deal about agents since v0.11 — the model calls your applications make, what they cost, when they cross a budget. Nothing let an agent know anything about your estate. The new MCP module fixes that direction of travel.

v0.12.0 turns AI spend from a number on a screen into something that reaches you — and opens the estate, read-only and on your switch, to an agent that can investigate it.

v0.10.0 answers a question that comes from outside the platform team: what is this cluster costing, and how much of it is buying nothing? A Kubernetes cluster is sized by what its workloads reserve, not by what they use — and until now avuru obs only knew the second half of that sentence.

v0.9.0 is for clusters where the network is not a straight line. A service mesh intercepts every call, so a dependency graph either draws hops that are not dependencies or draws nothing at all — and the kernel underneath has been seeing faults nobody was asking it for.

v0.8.0 is about the screen people actually look at. The service map has been the product's front page since v0.1 and a graph of circles for just as long. This release taught it to say more — and it needed no new collection: everything below is drawn from telemetry that was already arriving.

v0.7.0 is about the words your data is filed under and the surfaces that read it. v0.6 opened both ends of the pipe; what arrived was only as useful as the vocabulary available to slice it — and, it turned out, as truthful as the map drawing it.

Observing a second cluster used to mean running a second instance — its own store, its own UI, its own login. Projects now stretch across clusters instead: one screen, one store, and an install that can be just the ingest half.

v0.6.0 is about the two ends of the pipe. Getting data in no longer means re-pointing every sender you own, and getting a second cluster on the screen no longer means a second instance. Adopting avuru obs became a reversible decision instead of a migration.