Skip to main content
Wiacom Agent is a managed infrastructure appliance, delivered as a VM, cloud VM or bare-metal image, that securely bridges the Wiacom cloud platform with customer-controlled WiFi infrastructure. It is not delivered as an application. It is provided as a full lightweight system image with the required operating system, services, security configuration, and Wiacom connectivity pre-included — ready to import and run without manual setup.

Deployment Options

Wiacom Agent can be deployed as:
  • VM image on customer virtualisation platforms — VMware, Hyper-V, Proxmox, KVM, or VirtualBox
  • Cloud VM image inside the customer’s own cloud infrastructure — Azure, Google Cloud, AWS, or private cloud
  • Bare-metal image on a mini PC, Intel NUC, Raspberry Pi, or industrial gateway

What It Does

The agent runs inside the customer-controlled environment and acts as the secure execution layer between Wiacom and the local WiFi infrastructure. It can:
  • Receive provisioning tasks from Wiacom
  • Create, update, or delete SSIDs
  • Configure WiFi Pass / unique PSK credentials
  • Update VLAN, password, band, or access settings
  • Communicate with APs, controllers, or gateways over local API, REST, CLI, or vendor-specific interfaces
  • Report task status and errors back to Wiacom

Why It Is Needed

Some WiFi vendors or deployments expose management only locally — for example through a local REST API, SSH/CLI, controller LAN access, or a vendor-specific local interface. In these cases, Wiacom cannot safely connect directly from the cloud to the equipment. The agent solves this by running inside the same network as the AP or controller.

How It Works

1

Import or install the appliance

The VM or bare-metal image is deployed in the customer environment using the appropriate method for the target platform.
2

Boot with services included

The appliance boots with Wiacom agent services already configured — no post-installation setup required.
3

Outbound connection to Wiacom

The agent establishes an outbound HTTPS connection to the Wiacom cloud. No inbound ports are required.
4

Receive provisioning tasks

Wiacom sends configuration and provisioning tasks to the agent over the established channel.
5

Local execution

The agent executes tasks against the local AP, controller, or gateway using the appropriate interface.
6

Report results

Task status, confirmation, and any errors are reported back to Wiacom.

Security Model

No public inbound access is required. The appliance requires only:
  • Outbound HTTPS access to the Wiacom cloud
  • Local network access to the managed AP, controller, or gateway management interfaces
  • Customer-approved credentials or API tokens for the managed WiFi equipment
All communication between the agent and Wiacom is outbound-initiated and encrypted. The appliance does not expose any public-facing service.

Minimum Requirements

For most deployments:
ResourceMinimum
CPU1 vCPU
RAM512 MB – 1 GB
Disk2 – 10 GB
OSLinux
Network (outbound)HTTPS to Wiacom cloud
Network (local)Access to AP / controller management IPs
No public inbound port is required. The agent initiates all external communication outbound.