> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/introduction-to-zoom-node.md).

# Introduction to Zoom Node

Learn more about Zoom Node and how it works with your Zoom Workplace app features

Zoom Node is a hybrid platform that integrates your data center servers with Zoom’s cloud. With the Zoom Node platform, you deploy Zoom Service Modules (workloads) on your premises, and control them through the Zoom admin web portal.

Featuring a cloud-driven deployment model, Zoom Node allows administrators to quickly deploy Zoom workloads to their data centers using the Zoom admin web portal. This portal also includes tools for service management, upgrades, log management, performance reporting, and troubleshooting.

Zoom Node is an appliance packaged with a hardened OS, which can run as a virtual machine (VM) on a [supported Hypervisor](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/zoom-node-infrastructure-prerequisites.md#supported-hypervisors). Zoom Node is deployed to a customer data center to operate Zoom Hybrid Services, also called modules, such as Meetings Hybrid, Recording Hybrid, Chat Hybrid, and Phone Local Survivability.

This guide covers the deployment, configuration, and registration process for a Zoom Node virtual machine. Instructions for supported hypervisors are provided in this guide.

Refer to the Zoom support site for [deployment guides on individual hybrid services](https://support.zoom.com/hc/en/category?id=kb_category\&kb_category=2cd976da8720391089a37408dabb35f9).

You can learn about general Zoom Node concepts and architecture by reading the [Zoom Node Explainer](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer).

### <mark style="color:blue;">Zoom Node is a modular design where you only deploy the Service Modules you need</mark>

Instead of requiring separate software for each hybrid service, Zoom Node is an “all-in-one” modular platform that allows companies to manage and deploy multiple hybrid services using one common framework.

Zoom Node achieves this modular design by installing the Zoom Node OS (a Linux-based operating system) onto enterprise data center servers, transforming them into Nodes. Once the software is installed, the Node registers with the Zoom Node Platform in the cloud and awaits installation of various Service Modules that provide Zoom service functionality.

Service Modules are service-specific software that run on the Zoom Node platform, allowing hybrid services like Zoom Phone Local Survivability to function. Each Zoom Node endpoint can support up to four (4) Service Modules.

Zoom administrators assign services to Nodes ‌using the web-based Zoom Node dashboard. After selecting the service for a Node, the Zoom Node Platform pushes the chosen Service Module configuration from Zoom’s cloud to the device and installs it automatically. Once installation is complete and the service has been started, the Node endpoint is ready for use with its designated hybrid service.

The following Service Modules are currently available:

* [Zoom Meetings Hybrid](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-meetings-hybrid)
* [Zoom Recording Hybrid](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-recording-hybrid)
* [Zoom Chat Hybrid](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-chat-hybrid)
* [Zoom Conference Room Connector Hybrid](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-conference-room-connector-hybrid)
* [Zoom Phone Local Survivability](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-phone-local-survivability)
* [Zoom Meetings & Recording Connectors (On-Premises)](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-explainer/zoom-meetings-and-recording-connectors-on-premises)

For more information on each Service Module, see the [Zoom Node Explainer](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-overview.md).

### <mark style="color:blue;">Zoom Node supports several hypervisor deployments with varying system requirements</mark>

For details on Zoom Node-supported hypervisors and the associated requirements and prerequisites, see [Supported Hypervisors](https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/zoom-node-infrastructure-prerequisites.md#supported-hypervisors).


---

# 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://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/introduction-to-zoom-node.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.
