Technical Requirements & Prerequisites

Infrastructure Requirements

Before deploying Project Green in any model -- cloud-connected agents, partner-hosted backend, or full on-premises -- it is important to understand the infrastructure requirements at both the agent level and the server level. Proper sizing and preparation upfront prevent performance issues and simplify ongoing operations.

For agent deployments, the Project Green agent is a lightweight process designed to run on a dedicated virtual machine or as a container. The minimum specification for an agent host is 2 CPU cores, 4 GB of RAM, and 20 GB of available disk space. A single agent instance can monitor up to 500 devices, depending on the polling frequency and the number of active plugins. For larger sites, multiple agents can be deployed and load-balanced across the device inventory.

For partner-hosted or on-premises backend deployments, the infrastructure requirements are more substantial. The recommended baseline for a production environment is a Kubernetes cluster with at least 3 worker nodes, each with 4 CPU cores and 16 GB of RAM. The platform also requires a PostgreSQL 15+ database instance (managed or self-hosted) with at least 100 GB of storage, scaled based on the expected data retention period and device count. A Redis 7+ instance is used for caching and real-time messaging, requiring at least 2 GB of RAM.

Storage requirements grow with the number of monitored devices and the configured telemetry retention period. As a general guideline, plan for approximately 500 MB of database storage per 100 monitored devices per month of retention. Cyviz provides a sizing calculator in the partner portal that generates specific recommendations based on your deployment parameters.

All infrastructure should be provisioned with appropriate redundancy for production workloads. This includes database replication, persistent volume backups, and node-level fault tolerance in the Kubernetes cluster. Cyviz's deployment guide includes reference architectures for AWS, Azure, and GCP that follow cloud-provider best practices for high availability.

Network Requirements

Network configuration is a critical aspect of any Project Green deployment. The agents must be able to communicate with both the monitored devices on the local network and the backend services, whether those are cloud-hosted or on-premises.

Agents communicate with the backend over HTTPS (port 443) using TLS 1.2 or higher. If the backend is cloud-hosted, the agent requires outbound internet access to the Cyviz cloud endpoints. A full list of domains and IP ranges that must be allowlisted is provided in the partner portal. If the customer's network uses a web proxy, the agent supports proxy configuration via environment variables, including support for proxy authentication.

For device communication, the agent needs network reachability to the devices it monitors. The specific ports and protocols depend on the device types and plugins in use. Common requirements include SNMP (UDP 161), HTTP/HTTPS (TCP 80/443), SSH (TCP 22), and Telnet (TCP 23) for legacy devices. Some specialized plugins may require additional ports, which are documented in each plugin's configuration guide.

In environments with network segmentation or VLANs, the agent must be placed on a network segment that has routed access to the device VLANs. Alternatively, multiple agents can be deployed across network segments, each monitoring the devices reachable from its segment. The backend aggregates data from all agents into a unified view regardless of network topology.

For real-time dashboard features, the web application uses WebSocket connections (WSS on port 443) between the browser and the backend. If the customer's network employs a web application firewall or reverse proxy, ensure that WebSocket upgrades are permitted. Latency between the agent and backend should be kept below 200ms for optimal real-time alerting performance, though the system is resilient to higher latencies and intermittent connectivity.

Partners should perform a network assessment as part of the pre-deployment scoping process. Cyviz provides a network readiness checklist and a connectivity test utility that the agent can run to validate reachability to both the backend and the target devices before full deployment begins.

Supported Devices and Protocols

Project Green is designed to be vendor-agnostic and supports a broad range of AV, collaboration, and IT infrastructure devices. The platform's plugin architecture means that new device support can be added without modifying the core agent, and the library of supported devices grows with each release.

The current device support library includes major collaboration platforms such as Microsoft Teams Rooms (Windows and Android), Zoom Rooms, Cisco Webex Devices (Room Series, Board, Desk), and Poly (Studio, G7500, Trio). Display and projection devices from manufacturers including Samsung, LG, Sony, Epson, NEC, and Christie are supported via their respective control protocols. Audio systems from Shure, Biamp, QSC, Sennheiser, and Bose are also covered, along with control systems from Crestron, Extron, and AMX.

At the protocol level, the platform supports device discovery and monitoring via SNMP v1/v2c/v3, HTTP/HTTPS REST APIs, native vendor APIs (such as the Cisco xAPI and Crestron CIP), serial over IP, and SSH/Telnet for command-line accessible devices. Each plugin abstracts the protocol details and exposes a normalized set of device properties and health indicators, so the dashboard and alerting experience is consistent regardless of the underlying communication method.

If a customer's environment includes devices that are not currently supported, partners have two options. First, check the upcoming release roadmap in the partner portal -- the device may already be scheduled for support. Second, consider the custom plugin development path described in the Integration Models topic. Partners with technical certification can develop plugins for unsupported devices and submit them for review and inclusion in the shared library.

Partners should compile a complete device inventory during the scoping phase, including manufacturer, model, firmware version, and network connectivity method. This inventory is used to validate plugin compatibility and identify any devices that may require additional development or configuration.

Agent Deployment Prerequisites

Deploying the Project Green agent at a customer site requires preparation on both the technical and organizational sides. A well-prepared deployment goes smoothly and avoids the most common delays and issues.

On the technical side, ensure that the agent host meets the infrastructure requirements described above and has been provisioned with a supported operating system. The agent supports Linux (Ubuntu 20.04+, Debian 11+, RHEL 8+), Windows Server 2019+, and containerized deployment via Docker or Kubernetes. The host must have network connectivity to both the backend services and the target devices, as outlined in the Network Requirements section.

Before the deployment begins, the partner should have received an agent registration token from the Cyviz cloud portal or the on-premises backend administrator. This token authenticates the agent during its initial connection and assigns it to the correct tenant. Tokens are generated in the backend management interface and are scoped to a specific tenant and site.

Organizationally, ensure that the customer's IT team is aware of and has approved the deployment. This includes firewall rule changes, SNMP community strings or credentials for managed devices, and any change management processes that the customer requires. In enterprise environments, it is common for firewall and credential provisioning to take one to two weeks, so this should be initiated well in advance of the planned deployment date.

The agent installation itself is straightforward. On Linux, it is delivered as a .deb or .rpm package and can be installed via the standard package manager. On Windows, an MSI installer is provided. For containerized environments, a Docker image is available from the Cyviz container registry. Post-installation, the agent is configured via a YAML configuration file that specifies the backend endpoint, registration token, and any site-specific settings such as proxy configuration or custom plugin paths.

After installation, run the built-in connectivity check to verify that the agent can reach the backend and at least one target device. The agent will appear in the backend management interface within minutes of a successful registration, at which point device discovery and monitoring can begin.

Security and Compliance Considerations

Security is a top priority for Cyviz and should be a key part of every partner's deployment conversation with customers. Project Green has been designed with enterprise security requirements in mind, and understanding the platform's security posture will help you address customer concerns confidently.

All data in transit between agents, the backend, and the web dashboard is encrypted using TLS 1.2 or higher. Data at rest in the database is encrypted using AES-256 encryption. The platform supports integration with enterprise identity providers via SAML 2.0 and OpenID Connect for single sign-on, and role-based access control (RBAC) allows granular permission management at the tenant, site, and device group level.

The multi-tenant architecture ensures strict data isolation between customers. Each tenant's data is logically separated at the database level, and API authentication ensures that credentials scoped to one tenant cannot access another tenant's data. For partner-hosted and on-premises deployments, the data is physically isolated within the partner's or customer's own infrastructure.

Cyviz maintains compliance with SOC 2 Type II and ISO 27001 standards for its cloud-hosted infrastructure. The platform undergoes regular third-party penetration testing, and vulnerability disclosures are handled through a responsible disclosure program. Audit logs capture all administrative actions, user logins, and configuration changes, and these logs can be exported to SIEM platforms for centralized security monitoring.

For customers in regulated industries, partners should be prepared to discuss data residency, retention policies, and the customer's ability to control where their data is stored and how long it is retained. The platform's configurable retention policies and the availability of multiple deployment models (including on-premises) provide the flexibility needed to meet most regulatory frameworks, including GDPR, HIPAA (when combined with appropriate administrative controls), and government-specific standards.

Partners should familiarize themselves with the security whitepaper available in the partner portal, which provides a comprehensive overview of the platform's security architecture, certifications, and compliance posture. This document can be shared directly with customer security teams during the evaluation process.