Skip to main content
Asymptote helps security and IT teams understand what AI agents are doing at runtime and add controls as adoption grows. You can start with local endpoint telemetry, then move into centralized visibility, policy controls, and investigations when a small pilot turns into a broader rollout.

Why Teams Need This

AI agents create a visibility gap that most security tools do not cover well. Traditional endpoint and application logs can usually tell you that something happened, but not enough about the agent session that caused it. In practice, teams usually run into a few problems:

Unknown Agents, Unknown Risk

  • Teams often do not have a reliable inventory of which agent tools are in use.
  • Ownership is unclear once agents spread across individual laptops and teams.
  • It becomes hard to answer basic questions such as which harness is running, what it can access, and where activity should be monitored.

Runtime Moves Faster Than Review

  • Agents can read files, call tools, write code, and trigger actions very quickly.
  • Manual review works for a small pilot, but it does not scale once many users or teams depend on agents.
  • Security teams need a way to observe and govern activity while it is happening, not only after the fact.

Logs Without Runtime Context

  • Standard logs may show a process, file write, or network connection.
  • They usually do not show the prompt, tool call, file context, or session flow behind that action.
  • That makes investigations harder and weakens policy decisions.

How Asymptote Fits Together

Asymptote is built as a progression rather than a single all-or-nothing product.
  • Asymptote Open Source is the open-source foundation. It captures local agent activity such as prompts, tool calls, file edits, commands, and related session events. Teams can inspect that record locally or forward it into their own security tools.
  • Asymptote Managed builds on that foundation with centralized ingest, retention, detections, fleet-wide visibility, policy controls, identity mapping, approvals, and investigation workflows.
  • Private Deployment is for teams that need dedicated infrastructure, tighter data boundaries, or residency controls.
That gives teams a practical path:
  • start with endpoint visibility
  • validate what agents are doing
  • centralize and govern that activity as usage expands
  • move into private deployment when compliance or infrastructure requirements demand it

Choosing a Deployment Path

Use these rules of thumb:
  • Choose Asymptote Open Source if you want local visibility, a normalized record you control, and customer-managed forwarding into your SIEM or observability stack.
  • Choose Asymptote Managed if you need centralized operations across endpoints, users, and teams.
  • Choose Private Deployment if managed capabilities are right, but you need stronger infrastructure ownership or data-isolation requirements.
CapabilityAsymptote Open SourceAsymptote ManagedPrivate Deployment
Open-source runtime telemetry
Capture from supported local agent harnesses
Customer-managed SIEM forwarding
MDM-friendly endpoint rollout
Managed ingest, retention, search, and detections-
Fleet-wide inventory and centralized visibility-
Policy controls, identity mapping, and approvals-
Investigation timelines and case workflows-
SSO, RBAC, and audit trails-
Dedicated deployment and data isolation options--

Asymptote Open Source

Asymptote Open Source is built on the agent-beacon repository. Agent Beacon GitHub star growth If you are starting with Asymptote Open Source, these pages are the most useful next steps:

Quickstart

Choose the right setup path for a managed rollout or local developer evaluation.

Open Source Architecture

Learn how local agent harness telemetry flows through collection, normalization, and local outputs.

Local testing

Validate endpoint health, events, dashboard access, MCP access, and logs.

Agent harness integrations

See supported agent harnesses, deployment modes, destinations, and boundaries.

Endpoint event schema

Review Asymptote Open Source JSONL fields, normalization behavior, and example events.

Security & IT Rollout Guide

Plan endpoint inventory, MDM rollout, retention policy, validation, and log forwarding.
Additional references: Core Concepts, Command reference, and MCP server.

Asymptote Open Source

Install the open-source CLI and configure endpoint telemetry.

Asymptote Managed

Review managed visibility, policy controls, investigations, and rollout support.

Hosting Options

Compare the open-source local path with managed and enterprise deployment options.

Pricing

See plan positioning for open-source, managed enterprise, and private deployment.