On prem deployments

Your

Deploy Arize AX in your own environment.

True self-hosted

Advantages of Arize

Data, authentication, APIs, and the UI stay inside your infrastructure. The full capabilities of the AX platform stay intact.

Data stays in your environment

Data never leaves your perimeter. One security boundary to audit; air-gapped deployment available for regulated and classified environments.

SOC 2 Type II, ISO 27001, HIPAA-ready
SAML 2.0 SSO with your IdP (Okta, Azure AD) no third-party authentication

No dependency on Arize after deploy

Everything runs in your infrastructure. No operational dependency on Arize: business continuity and uptime are yours to own.

Platform keeps running regardless of vendor status or outages
No vendor lock-in on access or data

Predictable infrastructure costs

You control spend.
Use reserved instances and enterprise agreements; no surprise usage-based platform pricing as teams or usage grow.

Your cadence, your identity, your updates

You decide when to update and who has access. Pin versions, run staging, fit ITIL and change management. Terraform fits your naming and GitOps.

FAQ

Everything you need to know about self-hosting.

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.

What you get

Data on your network

Keep your data on your company's network.

Your auth system

Use your existing IdP (Okta, Azure AD, etc.).

Premier support

Dedicated support from the Arize engineering team.

Self or fully managed

Run it yourself or have Arize manage the deployment.

Deployment Comparison

In the SaaS model, data is logged or periodically sent to Arize AX's managed cloud infrastructure. The SaaS offering is also available with a Private Connect option that keeps the transmission of data within the cloud provider's private network backbone. With the Self-Hosted Deployment (VPC/On-Prem), Arize is installed in the customer's cloud of choice and data remains within their private VPC.

Ready to get started?

Get a personalized walkthrough of Arize AX - tailored to your stack and use case.

Get started Book a demo

Docs

Start here

Build your playbook