Skip to content

InvokeFlow Documentation

InvokeFlow is a platform of programmable runtimes that turn every screen, desktop, and speaker into a remotely orchestrated surface — all driven over MQTT, on your own network. Publish a command; windows, widgets, and apps flow into place.

The platform has three products that share one command contract:

  • InvokeFlow Aria — the programmable display runtime (any screen → a multi-window surface).
  • InvokeFlow Composer — the programmable desktop runtime (drive real native app windows in place).
  • InvokeFlow Conductor — the control plane (one console for the whole fleet, plus KingDSP audio).

Documentation

Aria User Guide

Your complete guide to InvokeFlow Aria. Covers installation, setup, MQTT architecture, the windowing system, screen states, system commands, widgets, media playback, intercom, Home Assistant integration, and more.

Conductor Admin Guide

Administration and operations guide for InvokeFlow Conductor. Covers device provisioning, fleet management, user roles, security policies, remote troubleshooting, and day-to-day operational workflows across your InvokeFlow surfaces.

MQTT Widget Reference

Comprehensive technical reference for every MQTT command, widget type, and configuration option. Covers 25+ widget types including gauges, charts, carousels, animated text, clocks, weather, maps, canvas, calendars, games, and more.

Custom Widget SDK

Build your own widgets for InvokeFlow Aria. The Custom Widget SDK provides a JavaScript bridge API for creating interactive third-party widgets that communicate bidirectionally with the runtime via MQTT.

On naming — InvokeFlow was formerly the King Suite

These products were previously KingKiosk (now Aria), King Admin (now Conductor), and KingComposer (now Composer), from Kall Innovations — now InvokeFlow Inc. Some technical identifiers in these docs — MQTT topic roots such as kingkiosk/{device_id}/…, command names, and settings keys — still use the original names to match the current shipping apps. They will transition to the InvokeFlow namespace in a future release; the protocol contract is unchanged in the meantime.