> ## 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 options
> Choose where Vidoc runs and understand the delivery process and responsibilities for your deployment.
Vidoc is available as a cloud service and as a self-hosted installation in your Kubernetes infrastructure. Self-hosted deployments can run on premises or in your cloud environment. Vidoc reviews the platform and service configuration with your team before installation.
This section helps DevOps teams plan a deployment. The [deployment process](/deployment/process) explains what you receive and how Vidoc works with your team. Detailed installation procedures come in the technical runbook supplied for your release.
## Choose where Vidoc runs
| | Vidoc Cloud | Self-hosted |
| ---------------- | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Infrastructure | Vidoc operates the service. | Your team operates the Kubernetes infrastructure and agreed supporting services. |
| Deployment | Start in the hosted web app. | Your team deploys with the supplied Helm chart and runbook, with guidance from Vidoc. |
| Release delivery | Vidoc manages application updates. | Vidoc supplies private image access and release guidance. You can copy the images into your own registry. |
| Connections | Use the integrations available on Vidoc Cloud. | Plan connections to your source code platform, identity provider, and configured LLM service. |
| Operations | Vidoc operates the application infrastructure. | Your team owns monitoring, backups, recovery, and maintenance under the agreed deployment plan. |
Open [app.vidoc.dev](https://app.vidoc.dev) or your custom deployment URL to use the web app. The API has a separate address; refer to [API addresses](/api/authentication#base-url).
## Private network access
Your web app and API can be available only within your internal network. With an internal self-managed GitLab or Bitbucket Data Center instance, webhook delivery and repository access do not require public ingress.
A deployment with no public-internet runtime access also needs private connectivity to every required service, including the LLM and embedding services. Vidoc reviews the full network boundary and verifies the agreed configuration with your team. Refer to [Private network access](/deployment/networking#private-network-access).
## Self-hosted installations
Vidoc provides access to private Docker Hub images, a deployment package, a technical runbook, and guidance through setup and validation. Your team can mirror the images into its own registry and deploy them in the agreed environment.
Start with [Deployment process](/deployment/process) to understand the stages from environment review to operational handover. The following pages help each team prepare:
Image access, the runbook, technical guidance, validation, and handover.
Application workloads, supporting services, and connections to your systems.
Capacity, storage, platform access, integrations, and service ownership.
Web and API addresses, webhooks, registry access, and runtime connections.
Monitoring, backups, maintenance, release delivery, and support.
To discuss your environment, contact [support@vidocsecurity.com](mailto:support@vidocsecurity.com).
## Comparison
The table below describes product and account differences between deployments.
| Item | Vidoc Cloud | Self-hosted |
| ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hosting | Vidoc operates the service. | Your Kubernetes cluster. Your team operates the installation. |
| Web app and API addresses | `https://app.vidoc.dev` and `https://api.vidoc.dev` | Your own hosts, for example `https://app.` and `https://api.` |
| Sign-in | Passwordless email sign-in or Google. Your email address must be verified. | Your company identity provider (SSO, OIDC). |
| Organizations | You create an organization. The creator becomes the admin. You can be a member of more than one organization. Use **Change organization** in the user menu to switch. | One organization for the installation. |
| Members | An admin invites members by email and sets their role and project access. An admin can change roles and project access, and remove members. | Users join when they sign in through SSO. There are no invites. A new user gets the Developer role. Your operators set the first admin. |
| Source code platforms | GitHub (github.com) and GitLab.com. Refer to [Supported platforms](/supported-platforms#availability-by-deployment). | GitHub (github.com), GitLab.com or self-managed GitLab, Bitbucket Cloud or Bitbucket Data Center. |
| Plans | Pro or Enterprise. Refer to [Plans](#plans). | All Enterprise features are included. |
| Slack | Available. Refer to [Slack](/web-app/slack). | Not available. |
| **Scans** panel (all scans of the installation, support bundles) | Not available. | Available to admins. Refer to [Settings](/web-app/settings). |
| Delete organization | An admin can delete the organization in **Organization danger zone**. | Not applicable. |
| Where data is stored and processed | Vidoc stores your data in infrastructure that Vidoc operates. Vidoc sends code and prompts to the LLM providers that Vidoc uses. | Vidoc stores your data in your Kubernetes cluster. Vidoc sends code and prompts to your own LLM account (AWS Bedrock in your AWS account in the reference configuration). |
## Data handling and security review
Before you connect production repositories, request the security and data-processing information for your deployment from [support@vidocsecurity.com](mailto:support@vidocsecurity.com). Include your hosting choice and any data-residency requirements.
Ask for the agreed details on:
* Where source code, findings, prompts, logs, and backups are stored and processed.
* Retention periods and deletion procedures, including backups.
* LLM providers and subprocessors, what data they receive, and their retention and model-training terms.
* Operator and support access to your data.
For self-hosted installations, review the release's installation and security guides with your operators, including outbound connections and your LLM account settings. Self-hosting alone does not establish the retention or training terms of an external provider. Use your deployment configuration and agreements for those terms.
The [website privacy policy](https://www.vidocsecurity.com/terms) covers the public website's privacy information. Request the product-specific documents above for repository and scan data.
## Plans
Vidoc Cloud has two plans: **Pro** and **Enterprise**. For prices and limits, refer to [vidocsecurity.com](https://www.vidocsecurity.com).
| Feature | Pro | Enterprise |
| ------------------------------------------------------------ | :-: | :--------: |
| Pull request reviews (PR scans, summary and inline comments) | ✓ | ✓ |
| Repositories and **Pull requests** pages | ✓ | ✓ |
| Manual full repository scans (**Run scan** in the web app) | ✗ | ✓ |
| Repository detail page | ✗ | ✓ |
| **Findings** | ✗ | ✓ |
| **Insights** | ✗ | ✓ |
| **AI Chat** | ✗ | ✓ |
| **Memory** | ✗ | ✓ |
* If your organization has no subscription, Vidoc does not run scans.
* On the Pro plan, the sidebar shows the Enterprise features in the **Enterprise only** group. These items are disabled.
* On the Pro plan, Vidoc does not run a first full scan when you turn on **PR reviews** for a repository. Refer to [How Vidoc works](/how-it-works#scan-types).
* Self-hosted installations include all Enterprise features.
To change your plan, contact Vidoc through [vidocsecurity.com](https://www.vidocsecurity.com).