Codenotary announced AgentMon Start, a purpose-built release of its AI agent monitoring platform for small and mid-sized businesses that provides visibility into how autonomous AI agents operate in their software development organization, without requiring a dedicated security team or cloud-based deployment.
The agentic monitor system provides the ability to see, investigate and govern what autonomous AI agents are actually doing in software development, and understand where the token spend goes.
The platform enables existing IT, development, and security teams to understand AI agent behavior, investigate anomalies, enforce governance policies, and maintain compliance as AI adoption accelerates. Also, AgentMon Start reports on token spend providing organizations with insight into their AI budget.
“While corporations have the ability to set up AI governance teams, security operations centers and specialized observability infrastructure, non-enterprise organizations often cannot,” said Moshe Bar, CEO and co-founder, Codenotary. “That leaves a visibility gap, yet AI agents used by smaller organizations have access to many of the same sensitive systems, credentials, customer records and source code, and generate substantial cost.”
AgentMon Start closes that gap by providing continuous monitoring, investigation capabilities, governance controls, and cost visibility for AI agents operating throughout the organization.
AgentMon Start is for organizations that want comprehensive AI oversight without deploying complex SaaS infrastructure or building dedicated AI security teams. No cloud account is required. AI activity remains within the organization's network.
AgentMon provides unified monitoring across more than 16 AI agent and large language models (LLMs), including Claude, Codex, Cursor, Gemini CLI, GitHub Copilot, Goose, Groq, KiloCode, Kiro, Ollama, and Roo Code.
AgentMon Start provides visibility across four areas.
- Cost management - Token consumption tracking, model usage, developer activity, session history, and AI spending across teams that enable organizations to identify unusually expensive usage, compare AI tools, establish budgets, and optimize AI operating costs.
- Security and agent behavior - The platform identifies secrets appearing in prompts, monitors files accessed or modified by AI agents, detects potential prompt injection attempts, identifies unauthorized AI tools, and maintains an audit trail of agent activity.
- Incident Investigation - When AI agents behave unexpectedly, organizations can review reasoning replay, execution traces, and search activity logs to understand exactly what occurred, eliminating the need to reconstruct incidents from fragmented application logs.
- Governance and shadow AI detection - Organizations gain visibility into which AI tools employees are actually using while applying consistent governance policies and guardrails across approved and unauthorized AI applications.
The Latest
When discussing AI Observability, one of the first questions that arises: Is this just an extension of traditional observability or is this a whole new type of tool? Part 2 compares traditional observability with AI observability ...
In this extensive 14-part series that will post over the next three weeks, experts across observability and AI will provide insight and opinions on the need for AI Observability, the challenges, the benefits, the current state, and predictions for the future ...
Amid rising complexity, organizations are moving quickly toward agent-driven operations: AgenticOps, according to The Impact of Agentic AI on Network Operations, a new report from Cisco ...
AI, automation, and enterprise software give organizations an extraordinary amount of leverage. Work that once required hours can happen in minutes. Information buried across systems can be analyzed almost instantly. Complex workflows can be coordinated across teams with far less manual intervention. That leverage creates a temptation to start with the technology ...
Everyone wants to talk about models. Compute clusters. Benchmark scores that climb a fraction of a point and make headlines anyway. It's an easy conversation to have because it's measurable. But it's also increasingly beside the point ...
For more than a decade, the default infrastructure play has been simple. Move more workloads to the cloud, retire on-premises gear and treat the data center as a cost to shrink. That logic held while public cloud offered near-limitless capacity at predictable prices, and AI demand is now testing both halves of that assumption ...
Most enterprise IT leaders can tell you exactly how many applications are running across their organization. They can surface a dashboard showing telecom spend by region, pull a report on SaaS license utilization, or call up a real-time view of mobile device inventory. The data is there, and IT leaders have largely delivered on the promise of visibility. Yet, in most organizations, that visibility has not translated into business value ...
Government agencies are largely misjudging their level of AI governance as the technology permeates their organization, according to Racing to Deploy: How Public Sector AI Adoption is Moving Faster Than the Foundations Needed to Support It, a new report from SolarWinds ...
When an application team reports that a service is slow, and a platform team confirms that the cluster is healthy, both statements can be true at the same time. The application team is describing response times observed in the code. The platform team is describing node, pod, and resource level conditions. Neither statement is incorrect. They are simply describing different layers of the same system, using different data. This is not primarily a matter of tooling. It is a difference in vocabulary, and it is one of the more common patterns in organizations running Kubernetes at scale ...
Traditional observability practices were not designed for systems that reason probabilistically, interact autonomously, and continuously evolve. With the rise of agentic AI, observability needs to evolve beyond just an operational monitoring discipline into a more strategic layer for governance and accountability across infrastructure, applications, workflows, and autonomous action ...