Planned release. Self-hosted Asymptote is in development and offered to design partners through a Private Deployment engagement; the Helm chart and Terraform modules described in this section are not generally available yet. This section describes the planned release: chart names, values keys and paths may change before it ships. Today’s Asymptote Cloud dashboard uses hosted services for sign-in and product analytics; the self-hosted release replaces them, as described in System Architecture. Contact us to take part.
Enroll a device
The CLI’s default service is beacon.sh, so always name your deployment.- System mode (fleets)
- User mode
System mode is the usual mode for a managed fleet. As root, run:A browser opens on your dashboard, and a member of your organization approves the device. Use
--no-browser to print the approval URL instead.BEACON_DASHBOARD_URL=https://<domain> in the environment does the same as --dashboard-url, which helps in MDM scripts.
Roll out with your MDM
Install the Beacon package with your MDM, then run the connect step on each machine. The MDM guides cover packaging and rollout; use your deployment’s URL wherever they connect to Asymptote.Policy enforcement
With policy enforcement on, the hooks on a connected device send their live checks to thepolicy service in your cluster. Turn it on per device with sudo beacon endpoint enforcement enable; the device must be an Apple Silicon Mac connected in system mode. enable downloads the enterprise Beacon package through your deployment, which fetches it from GitHub; to keep the cluster off GitHub, deploy the enterprise package with your MDM and then run enable.
Check it
managed_ingest block reports the device as connected to your domain, and the credential check passes. Run an agent session, and it appears on the dashboard within a minute.