Skip to main content
Start here if you are deciding how to introduce Asymptote across a team. Asymptote can begin as open-source Agent Beacon telemetry across supported local, CI, and cloud surfaces, move into managed visibility and governance, or run in a private deployment for stricter infrastructure requirements.

​
Choose a Deployment Path

Hosting OptionUse it whenNext step
Asymptote Open SourceYou want open-source telemetry across supported agent surfaces, local JSONL where applicable, and customer-managed forwarding into your SIEM or observability stack.Start with the Security & IT quickstart or developer quickstart.
Asymptote ManagedYou need centralized ingest, fleet-wide visibility, policy controls, investigations, SSO/RBAC, audit trails, and rollout support.Review Asymptote Managed or contact us.
Asymptote Private DeploymentYou want managed capabilities with dedicated infrastructure, stricter data boundaries, or residency requirements.Contact us to discuss deployment requirements.
See Hosting Options for the full comparison.

​
Open Source Rollout Strategy

For most Security and IT teams, the safest open-source path is staged. Local endpoint collection is usually the first evaluation path, then teams can add CI and cloud-agent surfaces where those agents run:
  1. Evaluate locally with a small pilot group using supported agent harnesses.
  2. Validate health and visibility with endpoint status, runtime log freshness, and expected event coverage.
  3. Add CI or cloud surfaces with the relevant Beacon setup paths when agent activity also runs in build jobs or hosted sandboxes.
  4. Decide where events should live: local JSONL only, Wazuh localfile, a supported SIEM/log destination, object storage, or a customer-managed pipeline.
  5. Expand through MDM once install coverage, collector health, and forwarding checks are stable.
The open-source path is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection.

​
Managed or Private Path

Move to Managed when a small pilot becomes an operating program: multiple teams, centralized search, governance, investigations, access control, and rollout support. Private Deployment is the path for regulated teams that need managed capabilities with dedicated infrastructure, stronger isolation, custom retention, or residency requirements. Contact us to discuss Managed or Private Deployment.

​
Pick Your Quickstart

For Security & IT Teams

Plan an open-source pilot, validate endpoint telemetry, and decide when to centralize or move to Managed.

For Individual Developers

Install Beacon locally, confirm collection health, and inspect agent activity on your machine.

​
Deeper Guides

Asymptote Open Source

Install Beacon and configure the open-source telemetry path.

Security & IT Rollout Guide

Expand from pilot to managed endpoint rollout, validation, and forwarding.

Asymptote Managed

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

Agent harness integrations

See supported runtimes, deployment modes, destinations, and boundaries.