Skip to main content
Arize Private Connect keeps the traffic between your cloud and Arize AX off the public internet. Telemetry, API calls, and UI traffic travel over your cloud provider’s private network through AWS PrivateLink, Azure Private Link, or Google Cloud Private Service Connect, while Arize continues to run the stack as a managed SaaS deployment. Arize recommends it when you need private connectivity, since you get the network isolation of a VPC deployment and Arize runs the infrastructure. Contact support@arize.com to set it up.

How it works

Your cloud account creates a VPC endpoint that connects to Arize AX’s environment. Data from your AI agents travels from your VPC through that private endpoint into Arize’s compute, and the same endpoint serves API and UI requests.
Architecture diagram of Arize Private Connect using AWS PrivateLink

Example architecture with AWS PrivateLink.

Why choose Private Connect

Compared with a VPC deployment, Private Connect is faster to set up and costs less to run. Managed network connections replace dedicated infrastructure, so there is nothing to install or maintain in your network, and Arize AX updates arrive without maintenance windows or downtime on your side. Traffic stays on the cloud provider’s network backbone. Any of your virtual networks in the region can connect, and networks in other regions can connect through network peering. Access control uses AWS IAM, Azure AD, or Google Cloud IAM alongside SSO.