> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command-connector/installation/prepare-for-a-command-connector-deployment.md).

# Prepare for a Command Connector Deployment

Gather key information before installing the Command Connector to integrate third-party IP cameras with Verkada Command

## Prerequisites and planning

* **Are the cameras IP-based?**
  * Analog cameras require an encoder to function (not recommended).
* **Are cameras on the** [Hardware Compatibility List](https://www.verkada.com/security-cameras/command-connector/hcl)?
  * If not, verify they support ONVIF Profile S or RTSP.
  * Use the [ONVIF Conformant Products](https://www.onvif.org/conformant-products/) tool to verify compatibility.
* **Do you have complete camera specifications?**
  * Camera type and model
  * Megapixel resolution
  * Encoding format
  * Number of video feeds
  * IP address and login credentials
* **Where are the cameras connected?**
  * Ideally, they should connect to the same network switch as the Command Connector.

***

## Device requirements

### Camera capabilities

* **Encoding format**: H.264 and H.265 streams are supported. H.265 requires Command Connector firmware that reports codec support, and the camera must support H.265. See [Configure H.265 for non-Verkada channels](/command-connector/configuration/configure-h.265-for-non-verkada-channels.md).
* **Resolution**:
  * **≤ 5MP**: Recommended for optimal performance.
  * **8MP** = Supported, but reduces the number of cameras that can be connected per Command Connector.
  * **> 8MP** = May not be supported. Contact your Verkada Solutions Engineer for more information.
* **Multisensor cameras**: Require one license per video stream.
* **Login access**: Each camera must have a known IP address and admin credentials.

### Network setup

* Cameras must be on the same LAN as the Command Connector.
* Avoid configurations where cameras are only accessible through an NVR’s internal switch.
* IT resources:
  * [Network Requirements](/command-connector/getting-started/command-connector-network-settings.md)
  * [Local Streaming](/verkada-cameras/video-streaming-and-sharing/live-streaming/local-streaming-on-verkada-cameras.md)

***

## Sizing and licensing

Collaborate with your Verkada Partner or Sales Rep to determine:

* The number of Command Connectors required.
* Whether camera retention settings align with expected video usage and storage needs.

{% hint style="warning" %}
One **LIC-CAM** license is required per video stream.
{% endhint %}

***

## Physical installation

Each Command Connector is a 1RU rack-mount server and requires:

* AC power
* One network connection to the site switch
* (Optional) Alternative mounting solutions are available from third-party suppliers.

Reference: [Command Connector Install Guide (PDF)](https://docs.verkada.com/docs/Verkada-CC300-500-700-Command-Connector-Install-Guide.pdf).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/command-connector/installation/prepare-for-a-command-connector-deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.