Voke Documentation
Integrator reference for Voke — multi-tenant IoT platform with ESM (AMQP) and PLC (MQTT) integration surfaces.
Voke is a multi-tenant IoT platform that connects plants and devices to energy-system-management (ESM) partners. This site is an integrator reference. It documents two things:
- How ESM partners (Obzor, CPI Energo, custom) connect to Voke over AMQP using their own adapter, which translates partner-specific commands into the Voke Communication Protocol (VCP).
- How PLC / device programmers connect plants and sub-devices to Voke over MQTT, publishing telemetry snapshots and receiving commands.
Operators using the admin dashboard do not need this site. Internal architecture deep-dives live elsewhere.
Pick your track
ESM Partners
AMQP, VCP, adapter pattern. Start here if you are integrating a partner ESM.
PLC / Devices
MQTT, auth, snapshot envelope. Start here if you are shipping plant-side firmware or controller software.
Shared concepts
Both tracks assume familiarity with Voke's domain model — organizations, plants, sub-devices, device templates, signals. See Concepts.
Try the sandbox
Every integration path can be exercised end-to-end without any external partner infrastructure. The Voke ESM sandbox ships inside the Voke API container and implements the real ESM HTTP contract. See the Voke ESM sandbox and quick-start pages under ESM Partners.
Architecture at a glance
Tech stack
| Layer | Technology |
|---|---|
| API | NestJS 11, TypeORM 0.3, PostgreSQL 16 + TimescaleDB |
| Broker | Mosquitto 2 (MQTT 5), RabbitMQ (AMQP 0.9.1) |
| Real-time | Socket.IO 4 |
| Protocol | VCP (AMQP), Voke PLC protocol (MQTT) |
Public endpoints
See the Endpoints page under Reference for the full domains + ports table.