Skip to main content
This guide provides an overview of how to install Qodo on-premises. The installation consists of four phases: preparation, deployment, configuration, and validation. Use this guide to understand the overall process, then follow the detailed documentation for each part of your installation.

​
Phase 1: Preparation

Before deploying Qodo, prepare your Kubernetes environment, credentials, and external dependencies.
1

Review the prerequisites

Make sure your environment meets the requirements for a Qodo on-premises deployment.
2

Obtain registry credentials

Contact Qodo to receive your Replicated registry credentials and verify access to the required registries.
3

Prepare persistent storage

Select your StorageClasses and initial claim sizes for Gitway and the bundled datastores. Choose whether Helm or your storage team owns the Gitway claim. See Configure persistent storage.
4

Prepare external dependencies

Provision the cluster entry point, DNS, TLS, storage, and external PostgreSQL server, unless you explicitly choose the bundled database. Prepare AI model access, your identity-provider application, and Git provider credentials. The default chart supplies Redis, RabbitMQ, and Zitadel. See Infrastructure requirements.If enabling ServiceMonitors during installation, prepare Prometheus Operator, its CRDs, and your Prometheus and Grafana deployment first. See Monitor Qodo with Prometheus and Grafana.
5

Prepare optional Kubernetes integrations

Select your ingress controller’s values and prepare DNS and TLS. See Configure ingress.If using ESO, reconcile the required Secrets and wait for Ready before installing Qodo. If enabling autoscaling, verify KEDA and its metrics APIs first. See Configure Kubernetes add-ons with values files.
6

Gather configuration values

Have the information required for your deployment available, including:
  • Registry credentials
  • AI model credentials
  • Git provider credentials
  • Domain names and TLS certificates
  • Organization or team configuration

​
Phase 2: Deployment

Deploy Qodo using Helm. The deployment process includes:
  1. Obtaining the required Helm chart.
  2. Configuring deployment values and secrets.
  3. Deploying Qodo to your Kubernetes cluster.
  4. Verifying that the Qodo services are running successfully.
Follow the detailed Helm procedure and keep your selected overlays in the same order for rendering, readiness checks, and deployment. For more information, see Deploy Qodo using Helm and Configure Kubernetes add-ons with values files.

​
Phase 3: Configuration

After deploying Qodo, connect it to your Git provider and configure the required settings. Connect your Git provider Select your Git provider and follow the corresponding installation guide: Each guide covers the provider-specific authentication, permissions, webhooks, and configuration required to connect Qodo.

​
Phase 4: Validation

After deployment and configuration, verify that Qodo is running correctly and can communicate with the required services.
1

Verify the deployment

Confirm that the Qodo services are running successfully in your Kubernetes cluster.
2

Verify connectivity

Confirm that Qodo can connect to your Git provider and other required external services.
3

Verify ingress and optional scaling

Check the certificate, OIDC discovery, backend health, portal, and SDK access through your selected ingress. See Configure ingress.If KEDA is enabled, exercise scale-out and scale-in with representative work. See Autoscale Qodo with KEDA.
4

Run a functional test

Trigger a test code review through your Git provider to verify that the integration is working correctly.
5

Verify monitoring

Confirm that expected Prometheus targets report UP and that Grafana shows metrics after test traffic. See Monitor Qodo with Prometheus and Grafana.
If validation is successful, your Qodo on-premises deployment is ready for use.