Skip to main content

Documentation Index

Fetch the complete documentation index at: https://arize-ax.mintlify.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Self-hosted Arize AX installs on Kubernetes using the distribution archive (Helm operator chart, arize.sh, Terraform, and offline docs/), your values.yaml, and your platform’s networking and storage.

Before you install

  1. Installation flow — Operator, Helm, and how the pieces connect.
  2. Prerequisites — sizing, pools, storage, and tools.
  3. Download and unpack the distribution — obtain and extract the release tarball.

Install by platform

Overview

The diagram below depicts the target topology for GCP.Throughout this section, distribution archive means the Arize AX release tarball you download with your JWT (Helm chart, arize.sh, Terraform, examples, and offline HTML docs).Read the ordered steps below once so you know the sequence (download → cluster → install → ingress → validate). Complete Prerequisites, including deployment types for your network model, before you start. Then open each linked page below; you can return here anytime as the hub.For the full Helm reference, use Advanced → Helm in the HTML documentation under docs/ inside your extracted distribution archive.
1

Download the distribution

Obtain the distribution archive with your JWT, extract it, and review the Helm chart, scripts, Terraform, and example manifests included in the bundle.

Download and extract

JWT, get_latest.sh, folder layout, and what to open next.
2

GKE cluster and infrastructure

Bring an existing GKE cluster and supporting GCP resources in line with Arize AX, or use the Terraform modules shipped in the distribution archive to provision them.

Existing cluster

Node pools, labels, GCS buckets, IAM, and Workload Identity.

Terraform

Use bundled modules and README; align static IPs and outputs with ingress.
3

Install Arize AX

Configure values.yaml for GCP and install the operator chart.

Quick start

Use when: you want a complete example values.yaml and a single Helm command to get running fast.

Detailed walkthrough

Use when: you need every field explained, base64 secrets, optional mirroring, and ./arize.sh versus Helm called out step by step.
4

Create ingress

Expose the UI and APIs with a Google Cloud HTTP(S) load balancer and the GCP examples, or use NGINX, Istio, Kong, or another controller with the bundled example manifests.

GCP load balancer

Static IPs, examples/endpoints/gcp, and appBaseUrl / expBaseUrl.

NGINX, Istio, Kong, …

Example paths under examples/endpoints and ingressMode guidance.
5

Validate the deployment

Confirm pods are healthy, ingress and DNS resolve, and the UI is reachable before sending data.

Validation checklist

kubectl health checks, ingress inspection, login, and SDK testing.
6

Use Arize AX

Open the public Arize AX documentation for product guides and configure your application with the on-prem SDK documentation.

Arize AX documentation

Product documentation, quickstarts, and observability guides on docs.arize.com.

SDK usage (self-hosted)

Python SDK versions and endpoint configuration for self-hosted deployments.

Integrations

Framework and provider integrations for tracing and monitoring.

Shared configuration

For release versions and artifacts, see On-premise releases.