Asymptote Labs raises $5.5 million to monitor and control enterprise AI agents – Unite.AI

AI agents are going beyond generating suggestions to edit files, execute commands, and work through connected business tools. For security teams, the resulting question is increasingly operational: What did an agent actually do, under whose authority, and is it possible to stop the next risky action? Asymptote Labs is building infrastructure around this problem and has announced an oversubscribed $5.5 million seed round.

The financing is led by Tower Research Ventures, the venture capital arm of Tower Research Capital, with participation from Lytical Ventures, 1984 Ventures and South Park Commons. Asymptote says the capital will support engineering, product development, hiring and go-to-market expansion.

Its approach combines Beacon, an open source layer for logging agent activity, with an enterprise platform for detection, response and governance. The distinction is important: collecting documentation of an action and applying a decision before the action proceeds are separate capabilities. A credible security architecture must make it clear which component does each job.

A common record across different agent tools

According to the company, Beacon captures activity on Claude Code, Codex, Cursor and more than 20 other agent systems. A harness is the software environment that connects a model to tools, instructions, and a work session. Different wiring exposes different information, making it difficult to investigate activity consistently across a company’s chosen tools.

Asymptote describes Beacon as an MIT-licensed telemetry layer that normalizes such records into a common runtime data model that extends OpenTelemetry. This gives security and engineering teams a shared framework to review activity instead of interpreting each tool’s history separately.

The Beacon repository adds useful implementation context. Describes session playback covering requests, responses, tool usage, commands, changes, approvals, and token information, along with local JSONL records and explicit targets. It also describes the transfer of revised knowledge via MCP or Agent Skills.

The practical value of normalization is correlation. An investigation may need to link a user request to a command, a file change, and an approval. A final answer alone cannot explain that sequence. A shared event structure can make the sequence easier to inspect, although the completeness of the record still depends on what a particular integration captures.

Where corporate control comes into play

Asymptote’s enterprise platform is based on Beacon with runtime detection and response. The company says it can intercept agent activity in real time and apply policy-based protections at the timeliness and tooling level, identifying risks such as data loss, insider threats, and AI supply chain issues.

The company website makes the division of the product more explicit. Open source beacons provide portable telemetry that customers can route into their existing security systems. Managed Asymptote adds acquisition, retention, search, discovery, identity mapping, policy controls, approvals, and governance workflows. Private implementations are also part of the stated offering.

This separation is important when evaluating an implementation. Recording a call to the tool after execution helps in investigations; preventing it requires a checkpoint in the execution path. Buyers need to determine which actions can be intercepted, which are observed later, and what enforcement looks like when a service is unavailable. The funding announcement does not publish a coverage matrix or benchmark for block accuracy.

These are central questions in the governance of enterprise AI agents. A policy written in the instructions of a model is different from a policy applied by an infrastructure external to the model. The useful test is whether an agent can proceed with an unauthorized action despite the intended restriction.

Telemetry can also preserve useful engineering knowledge

Beacon placement goes beyond security. The public project description explains how to use session history to identify useful workflows, fixes, debug patterns, and repository conventions to reuse in subsequent sessions. Instead of discarding a solved problem at the end of a conversation, the goal is to make the revised knowledge available to a future agent.

This creates a second reason to collect activity consistently across tools. A workflow discovered in one harness can be valuable to a team using another. However, preserving a successful sequence does not mean that it is safe to repeat it unchanged. Credentials, dependencies, permissions, and business requirements may change between sessions.

The same records that help diagnose errors can contain sensitive prompts, source code, or tool output. The distribution then raises familiar questions about information management: where records go, how long they stay, who can retrieve them, and how sensitive content is handled. Telemetry ownership is valuable, but it does not eliminate the need to regulate access to it.

Founders with experience in sensing infrastructure

Asymptote was co-founded by Justin D’Souza, CEO, and Shukan Shah, CTO. Both previously worked at social engineering firm Doppel. The company’s About page describes D’Souza’s work on scaling machine learning infrastructure and Shah’s work on automating security operations and agent-based threat hunting.

The announcement states that Beacon’s GitHub stars grew more than 460% in September and that the project reached third place in GitHub’s global trending repositories. These are company-reported signs of adoption, rather than evidence of tracking effectiveness or recurring revenue. Asymptote also says security teams are using Beacon and its enterprise platform in production, without disclosing customer counts or contract values.

Tower Research Ventures says its interest began with Beacon’s open source traction, and that Tower’s security organization is evaluating the technology on its own endpoints. Evaluation by an investor’s organization should be distinguished from publicly disclosed implementation by a commercial customer.

The next test is coverage and useful intervention

The seed round supports a broader thesis: As organizations deploy more agents, runtime records become necessary for security, design reliability, platform oversight, and cost analysis. A common data layer could allow these teams to examine the same task for different purposes.

The test for Asymptote will be whether the shared vision is comprehensive and timely enough to support action. Security teams will need useful detections with manageable false positives, while engineers will need records that explain errors without creating excessive collection costs. Financing provides the company with the resources to pursue these objectives; its long-term value will depend on what businesses can reliably observe, investigate and control.