In July 2025, Replit s AI agent deleted a production database containing data on 1,200+ executives and 1,190+ companies despite an explicit code freeze. Replit later acknowledged the incident and shipped additional safeguards.
It s a good example of why we think observing an agent after something goes wrong isn t enough.
With Traccia, you can define runtime policies around agent execution for example, which tools an agent is allowed to use, how many retries/tool calls it can make, or how long it can run.
We ve been thinking about this a lot while building Traccia.
One behavior we ve seen with MCP workflows is an agent getting into repeated tool calls without making meaningful progress. The workflow hasn t necessarily failed it can just keep going.
That got us thinking about a different kind of agent monitoring: not just detecting errors, but defining boundaries on execution.
A handful of people. A lot of late nights. More doubts than we d like to admit.
And today, Traccia is live on Product Hunt.
What started as conversations and rough ideas slowly became something real through broken builds, discarded ideas, tiny wins, and a small team that just kept showing up.
We re not a big company. There s no huge team behind this.
Traccia is a vendor-neutral AI Agent Control Plane built for teams running autonomous agents in production. Observe agent behavior, evaluate performance, govern actions with policies and runtime controls, and maintain an auditable trail of what happened. Built with an open, developer-first SDK and OpenTelemetry, Traccia works across models, frameworks, and existing observability stacks—so teams can control their agents without being locked into a single AI vendor.