Docs / Getting Started / Network and Environment Prerequisites

Network and Environment Prerequisites

Published · Last updated: May 2026 · 2 min read

Architectural Context

CloudAIPilot acts as an active, persistent control plane between your local machine and your globally distributed infrastructure. To support real-time orchestration telemetry and enterprise-grade security protocols, your local network and browser environment must meet strict baseline requirements.

Browser Compatibility Matrix

The dashboard leverages advanced Web API features for secure rendering and encrypted state management. We natively support the latest iterations of major evergreen browsers:

  • Google Chrome / Chromium-based (Primary Recommendation)
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge

*Warning: Legacy browsers (e.g., Internet Explorer) and browsers with strict JavaScript execution bans are inherently incompatible with the dashboard's cryptographic requirements.*

Local Network Configurations

If you operate within a restricted corporate network, defense contractor environment, or university network, your perimeter firewall must accommodate the following:

  1. Uninterrupted WebSocket Telemetry: CloudAIPilot utilizes secure WebSockets (wss://) to stream granular, real-time telemetry to the Activity Center. If your network deeply inspects or drops WebSocket connections, the interface will gracefully fall back, but you will lose real-time visibility into background operations.
  2. Secure Session Persistence: As noted in our security architecture, browser cookie limits prevent full Post-Quantum Cryptography (PQC) at the browser layer. We rely on highly secure, HttpOnly dual-token cookies. Browsers configured to aggressively block all cross-site data may experience session volatility.
  3. Aggressive Telemetry Blockers: Certain ultra-strict browser extensions (ad-blockers) may erroneously identify our internal telemetry API calls as tracking scripts. If the AI Pilot interface fails to respond, whitelist the dashboard domain.

Infrastructure Firewall Requirements (Port 22)

To execute autonomous commands, the CloudAIPilot orchestration engine must establish a secure SSH tunnel to your compute nodes.

  • Autonomous Provisioning: When CloudAIPilot provisions a server directly, the engine automatically configures the cloud provider's firewall (e.g., AWS Security Groups) to exclusively allow Port 22 (SSH) traffic from CloudAIPilot's static, trusted IP addresses.
  • BYOC (Bring Your Own Compute): If you are importing an existing, legacy server into the control plane, you *must* manually adjust your external firewall to permit inbound SSH connections from our published IP ranges. Without this, the AI Pilot cannot command the server.

Related Articles