Your

Yes, Arize AX supports deployment on GCP, Azure, AWS, Oracle Cloud, OpenShift, K3s, Rancher, Tanzu, and other Kubernetes environments.

• Connected: The installation workstation and cluster nodes have direct outbound access to Arize distribution services and container image registries, allowing software and images to be pulled directly without additional network configuration.
• Semi-restricted: The installation workstation and/or cluster nodes have limited outbound connectivity and must access Arize distribution services and/or image registries through a corporate proxy, firewall allowlist, or other controlled network path.
• Air-gapped: The workstation and/or cluster have no outbound connectivity to Arize distribution services or image registries. All required software artifacts and container images must be transferred into the environment through an approved offline process, typically using a private container registry and internal artifact repository.

Arize AX self-hosted runs the same core platform as the SaaS offering—full agent and LLM observability, tracing, online and offline evaluations, prompt optimization, datasets/experiments, and the Alyx AI assistant. The primary difference is operational rather than functional: in self-hosted, you own the infrastructure, scaling, and upgrades, and your data stays entirely within your environment.

In self-hosted Arize AX, all observability data lives entirely within your own environment—your Kubernetes cluster and your own persistent/object storage under your security controls. Arize does not store your data.

No. In a self-hosted deployment your data stays within your environment. Optional outbound features—such as Arize Call Home telemetry, hosted LLM evaluations, or external notification integrations (Slack, PagerDuty, SMTP)—only transmit data if you explicitly enable and configure them. 

A Kubernetes cluster (GKE, AKS, EKS, OpenShift, K3s, Rancher, Tanzu, etc.), persistent block storage for stateful components, and an object store like a cloud bucket or private storage solution (GCS, S3-compatible, Azure Blob, etc.).

Yes, Arize AX provides reference Terraform templates and modules for GCP, Azure, and AWS.

Yes. Arize AX self-hosted supports any SAML 2.0 IdP, including Okta, Entra, OneLogin, Ping. Arize AX also supports RBAC role mapping with your IdP provider.

Arize Database (adb) is an AI-native OLAP database designed by Arize AI for massive-scale ML and LLM observability. For benchmark information visit https://arize.com/blog/adb-benchmarks/.

Release notes and product changelogs are published in the Arize AX documentation, and platform announcements appear on the Arize blog. Self-hosted customers should consult the version-specific release notes for the chart/image version they’re deploying.