> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vidocsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment process

> What your team receives from Vidoc and how we work together to deploy it in your infrastructure.

Vidoc works with your DevOps team to prepare, deploy, and validate a self-hosted installation. Your team operates the infrastructure. Vidoc provides the release images, deployment package, technical runbook, and guidance.

This page explains what to expect at each stage. The runbook supplied with your release contains the installation commands and configuration details.

## From planning to the first scan

<Steps>
  <Step title="Review your environment with Vidoc">
    We review your Kubernetes platform, container registry, storage, network access, source code platform, identity provider, and LLM service. Tell us whether your deployment must operate without public ingress or public-internet access, and whether all processing must stay within your infrastructure. We also discuss the number and size of repositories, scan concurrency, and availability requirements.

    Your platform, identity, and source control owners help confirm the required access. Together, we agree on the deployment design and the work each team will do. Refer to [Preparing your infrastructure](/deployment/infrastructure).
  </Step>

  <Step title="Receive access to the release images">
    Vidoc provides access to its private Docker Hub images with an access token. You can copy the release images into your own container registry and deploy from there.

    The deployment package identifies the required image versions. It covers the Vidoc application, migration jobs, scan sandbox, and supporting components. Plan registry access for the complete set, including third-party images.

    Keep the supplied release versions together when you mirror them. Your team controls credentials for your own registry.
  </Step>

  <Step title="Receive the deployment package and runbook">
    You receive the Helm chart, configuration guidance, and technical runbook for the agreed release and environment. The runbook describes installation, credentials, service connections, and verification.

    The package identifies which supporting services will run with Vidoc and which will use services in your existing infrastructure. It also records the web app and API addresses for your installation.
  </Step>

  <Step title="Prepare your infrastructure with our guidance">
    Your team prepares the agreed cluster capacity, persistent storage, image registry, DNS, ingress, and credentials. The relevant owners prepare source control, SSO, and LLM access.

    Vidoc helps review the configuration and resolve deployment questions. Use [Networking and access](/deployment/networking) to coordinate the required connections with your network team.
  </Step>

  <Step title="Deploy and validate together">
    Your team deploys Vidoc with the supplied runbook. Vidoc provides guidance and helps diagnose installation problems.

    Together, we verify service health, sign-in, repository access, webhook delivery, LLM connectivity, and a complete scan with the agreed network restrictions in place. We confirm that results appear in the web app and in a test pull request when PR reviews are part of the deployment.
  </Step>

  <Step title="Complete the operational handover">
    We review monitoring, backup and recovery responsibilities, credential rotation, and the process for receiving releases and requesting support.

    Your team keeps the configuration and runbook for the installed release. Confirm the support contacts, access arrangements, and maintenance process at handover. Refer to [Operations and upgrades](/deployment/operations).
  </Step>
</Steps>

## What your team receives

| Deliverable                                  | Purpose                                                                                    |
| -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Private image access                         | Retrieve the Vidoc release images and copy them into your registry if required.            |
| Release image list and Helm chart            | Identify the application and supporting components that make up the deployment.            |
| Technical runbook and configuration guidance | Install and verify the agreed release in your environment.                                 |
| Deployment guidance                          | Review the configuration, resolve setup questions, and validate the first scan with Vidoc. |
| Operational handover                         | Agree on ownership, maintenance, and the support process.                                  |

To start a deployment review, contact [support@vidocsecurity.com](mailto:support@vidocsecurity.com) with a summary of your environment and requirements.