Skip to main content
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 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

Open app.vidoc.dev or your custom deployment URL to use the web app. The API has a separate address; refer to API addresses.

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

​
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 to understand the stages from environment review to operational handover. The following pages help each team prepare:

Deployment process

Image access, the runbook, technical guidance, validation, and handover.

Architecture and data flow

Application workloads, supporting services, and connections to your systems.

Preparing your infrastructure

Capacity, storage, platform access, integrations, and service ownership.

Networking and access

Web and API addresses, webhooks, registry access, and runtime connections.

Operations and upgrades

Monitoring, backups, maintenance, release delivery, and support.
To discuss your environment, contact support@vidocsecurity.com.

​
Comparison

The table below describes product and account differences between deployments.

​
Data handling and security review

Before you connect production repositories, request the security and data-processing information for your deployment from 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 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.
  • 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.
  • Self-hosted installations include all Enterprise features.
To change your plan, contact Vidoc through vidocsecurity.com.