> ## 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.

# Preparing your infrastructure

> The infrastructure, access, and capacity decisions to prepare with Vidoc before a self-hosted deployment.

Use this page to involve the right teams before deployment. Vidoc reviews these items with you and supplies the configuration and detailed procedures in the release runbook.

## Information to bring to the review

| Area                 | What your team prepares or confirms                                                                                                     |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Kubernetes           | Platform and version, node architecture, namespace ownership, and the team that can approve required controllers and permissions.       |
| Capacity             | Expected repository sizes, scan frequency, concurrent scans, and capacity available for application and sandbox workloads.              |
| Persistent storage   | Storage service and storage classes, capacity, performance, backup facilities, and recovery requirements.                               |
| Container registry   | Whether you will pull supplied images from Docker Hub or copy them into your registry, and who manages registry credentials.            |
| DNS and ingress      | Your web app and API hostnames, private or public ingress, HTTPS endpoints, and the users and systems that must reach them.             |
| Network boundary     | Whether public-internet access is permitted, which services must run internally, and which privately connected services are acceptable. |
| Source code platform | GitHub, GitLab, or Bitbucket type and location, repository owners, and the account that can prepare the integration.                    |
| Identity provider    | OIDC provider and the identity team that can register the application and supply its connection details.                                |
| LLM service          | Provider account, region, model access, quotas, and the team that manages credentials and service costs.                                |
| Secrets              | Your process for supplying application and integration credentials, retaining required encryption keys, and rotating them.              |
| Operations           | Owners for monitoring, backups, recovery, maintenance windows, and support coordination.                                                |

For the connection requirements, refer to [Networking and access](/deployment/networking).

## Capacity planning

Vidoc helps define resource and storage requirements for your workload. The estimate accounts for:

* The size and number of repositories, including the initial indexing and scan work.
* The number of scans that can run at the same time.
* Web, API, worker, and supporting-service capacity.
* Sandbox workloads and temporary or retained workspace storage.
* Data growth, backup storage, and the agreed retention requirements.
* Model-service quotas that can limit scan throughput.

A proof of concept and a production deployment can need different capacity and availability arrangements. Use the sizing agreed for your environment and release.

## Kubernetes workload requirements

The application includes long-running services and jobs. The sandbox runtime also creates workloads during scans. Your platform team reviews permissions, resource quotas, scheduling, and network policies for both kinds of work.

Plan persistent storage for the stateful services and the scan workspaces. Storage behavior during node replacement and service recovery is part of the deployment review.

## Existing services and availability

If your team wants to use existing database, object storage, or other supporting services, share their versions and access model with Vidoc. We confirm compatibility before including them in the deployment design.

Agree on availability and recovery requirements before choosing the number of replicas and placement of stateful services. Record which services your team operates and which are supplied as part of the deployment package.

## Ready for deployment

Before installation, your team and Vidoc confirm the deployment design, service owners, required access, and release package. The supplied runbook contains the checks used to verify the environment.

Refer to [Deployment process](/deployment/process) for image delivery, technical guidance, and validation with Vidoc.