1. Choose your path
Start with the deployment model that matches your review and operating needs.| Hosting Option | Best for | Where to go |
|---|---|---|
| Asymptote Open Source | Small pilots across supported local, CI, and cloud-agent surfaces, with local JSONL and customer-managed forwarding where applicable. | Continue below. |
| Asymptote Managed | Centralized visibility, policy controls, investigations, SSO/RBAC, and rollout support. | See Asymptote Managed. |
| Asymptote Private Deployment | Managed capabilities with stricter data isolation, residency, or infrastructure ownership requirements. | Contact us. |
2. Run a small open-source pilot
If you are starting local-first, pilot Beacon on a small macOS group before broad MDM deployment. Decide three things up front:- which agent harnesses are in scope
- whether events should stay local at first or forward into a security workflow
- which MDM group will receive the first system-mode package rollout
3. Deploy and validate
4. Expand or centralize
If the pilot is healthy, expand through MDM and add forwarding only where it matches your security workflow. Beacon preserves local JSONL even when you forward events downstream. Use Log Forwarding for Wazuh, Splunk HEC, Falcon LogScale HEC, Elastic, Datadog, Sumo Logic, Rapid7 InsightIDR, Microsoft Sentinel, object storage, local JSONL, and customer-managed pipelines. Move to Asymptote Managed when you need centralized retention, search, detections, fleet-wide visibility, governance, investigations, SSO/RBAC, audit trails, or rollout support. Contact us if you want Managed or Private Deployment guidance.Related
MDM Deployment
Plan managed macOS rollout with the packaged system agent.
Log Forwarding
Forward Beacon events into security and observability platforms.
Security Review
Review local collection, data inventory, content handling, endpoint behavior, and disclosure policy.
Asymptote Managed
Review managed visibility, policy controls, investigations, and rollout support.

