Installation
Welcome to the DataQI installation guide. This section is specifically designed for platform engineers and Kubernetes administrators who are deploying the DataQI data intelligence platform.
The DataQI application is designed exclusively for deployment to Kubernetes and is distributed as a series of Helm charts. The core DataQI agentic platform is deployed using the dataqi chart. Additional functionality may be enabled by other charts such as the dataqi-aiops chart, which contains additional resources that allow agents to query operational systems.
dataqi chart
Section titled “dataqi chart”The dataqi chart deploys a collection of interconnected microservices, including:
- The core AI-powered application programming interface (API).
- A stateless authenticated telemetry ingress for browser logs, traces, and metrics.
- A responsive single-page application (SPA) front-end.
- Asynchronous data extraction and processing workers.
- Foundational infrastructure components such as PostgreSQL, Valkey, and NATS.
For a detailed breakdown of these components, their responsibilities, and how they interact, refer to the System overview page.
Installed documentation
Section titled “Installed documentation”Every DataQI SPA image contains the public documentation built for that image’s version. After deployment, it is available without sign-in at:
https://<DataQI host>/docs/Rolling the SPA image forwards or backwards changes the installed documentation at the same time. The public site at docs.dataqi.ai describes the latest stable release and may differ from an older installation.
DataQI-authored pages, search, styles and fonts are included in the SPA image. Links marked with the external-link indicator retain their original destination and may require network connectivity.
Deployment architecture
Section titled “Deployment architecture”The deployment is designed to be highly available and scalable. The Helm chart encapsulates the entire infrastructure required to run DataQI, with the exception of the pre-requisite secrets.
Our deployment model assumes a “Day 2” approach to secrets management, meaning that all sensitive configuration must be provisioned securely into the cluster before the Helm installation begins.
Please start with the Prerequisites section to ensure your environment is ready for installation.