Skip to main content
On the hosted acusight.io service, there’s nothing to configure at this level — domains, database, object storage, identity, and TLS are all managed for you, and platform updates arrive automatically (see the changelog). You work entirely in the app. Configuration via environment variables applies only to self-managed and on-prem deployments, where you run the AcuSight stack in your own environment.

​
Self-managed configuration

Self-managed deployments are configured through a per-environment file (for example, an .env for your deployment mode) covering domain and hosting, database, object storage, identity and single sign-on, TLS, and the edge agent version. Values are environment-specific and include secrets, so the full schema isn’t published here.
The complete environment-variable reference, with required values and secret-generation steps, ships with the on-prem package. Contact your AcuSight representative to scope a self-managed or air-gapped deployment.

Air-gapped / on-prem

How self-managed and disconnected deployments are delivered.

Sign in & SSO

Authentication for the hosted service.