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.
Quick decision
- No infrastructure to run? Use Asymptote Cloud.
- Telemetry must land in your account first, but a hosted dashboard is fine? Use BYOC storage.
- No third party may hold or read your agent telemetry? Self-host, on Kubernetes, with one of the two setup paths below.
Self-hosted: Kubernetes
Asymptote runs on Kubernetes only, installed from one Helm chart. The chart is the same on every cloud.Two setup paths
Requirements
Sizing
Size depends on how many endpoints you have, how much agent activity they record, and how long you keep it. Event volume drives ClickHouse’s CPU, memory and disk; the other services are small and scale horizontally.
Asymptote sizes your deployment during the engagement from your fleet size, a sample of your endpoints’ event volume and your retention period, and sets the chart’s resource values to match.
External dependencies
By cloud
The services each release is tested with, and what the reference Terraform creates:LLM providers
Container registry
Images are in Asymptote’s private registry. Pull them with the credentials Asymptote gives you, or mirror them into your own registry (Amazon ECR, Artifact Registry or Azure Container Registry) and point the chart at it.Migration
- From Asymptote Cloud. Stand up the self-hosted deployment, re-enroll endpoints against it (see Connecting Endpoints), and disconnect them from Asymptote Cloud. Ask Asymptote about carrying over policies and history.
- From BYOC storage. Point the self-hosted loader at your existing bucket, and it loads the history already there.
Next steps
- System Architecture: what runs where.
- Terraform: create the cluster and services.
- Kubernetes Deployment: install the chart.