# Self-hosted deployment

> An overview of running AI CodeOps on your own Kubernetes cluster, an Enterprise option on request: what it involves, what it needs, and how to get started.

Source: https://aicodeops.dev/docs/self-hosted · Last updated: 2026-10-18

Most teams use AI CodeOps as a hosted service in the browser. Some organizations need their code and run history to stay on their own infrastructure. For them, self-hosted deployment is available as an Enterprise option, on request. It is not a separate product and has no public install steps: it is planned with you, and the installation guide is shared privately with Enterprise customers.

This page gives an overview so you can judge whether it fits. To start, [contact sales on the Enterprise page](https://aicodeops.dev/enterprise).

## What you get

A self-hosted Enterprise install runs the same browser-based product your team would use on the hosted service, in your own Kubernetes cluster:

- your code, sessions, changes and audit history stay in your database;
- you choose the AI model provider your sessions use;
- secrets can come from your own secrets store;
- people sign in through your identity provider with [SSO](https://aicodeops.dev/docs/sso).

## What it involves

AI CodeOps is deployed with a Helm chart. At a high level, an Enterprise install involves:

| Part                 | What it is                                                                                     |
| -------------------- | ---------------------------------------------------------------------------------------------- |
| Kubernetes           | A cluster running Kubernetes 1.27 or later.                                                    |
| Application services | The web console, the sign-in service, an operations service, and workers that run AI sessions. |
| Scheduled jobs       | Jobs for schedules, approvals, monitoring, notification retries and data retention.            |
| PostgreSQL           | The main database. Schema migrations run as a job before each upgrade.                         |
| Redis                | Used alongside the database by the application services.                                       |
| Ingress and TLS      | An ingress controller and certificates for the console's address.                              |
| Sandboxes            | Optional isolated containers for test runs and terminals, with restricted network access.      |
| Secrets              | Kubernetes secrets, or your secrets store.                                                     |

Your team also connects the services AI CodeOps talks to: your Git host, your model provider and your email delivery.

The exact sizing, storage, backup and network design depend on your environment, and are agreed during planning.

## How to start

1. Open the [Enterprise page](https://aicodeops.dev/enterprise) and fill in the contact form.
2. Tell us about your environment: your Kubernetes platform, Git host, model provider and identity provider.
3. We plan the deployment with you and share the installation guide.

## Next steps

- [Enterprise](https://aicodeops.dev/enterprise)
- [Enterprise overview](https://aicodeops.dev/docs/enterprise)
- [Data retention and deletion](https://aicodeops.dev/docs/data-retention)

## Frequently asked questions

### Can I self-host AI CodeOps on the free plan?

No. Self-hosted deployment is available to Enterprise customers only, on request. The open beta runs on the hosted service.

### Is there a public installation guide?

No. For Enterprise customers, the installation guide is shared privately and the deployment is planned with you.

### Does a self-hosted install need a desktop app or CLI?

No. A self-hosted Enterprise install is the same browser-based product, running on your infrastructure.