Verana's local controller runs the installation. Cloud services share the same model of spaces, looks, touchpoints, Managed Fixtures, and state so integrators can monitor, support, update, and diagnose the system without tunneling into a black box.
The on-site Verana controller executes looks, schedules, triggers, fixture output, and local state. Cloud services synchronize authorized system data over a secure outbound connection for remote visibility, diagnostics, updates, and AI-assisted workflows. Local operation does not depend on cloud availability.
A UI config describes what controls exist. A touchpoint record describes where and how those controls are used: assigned space, role, orientation, allowed actions, default behavior, and controller failover targets.
That separation lets the same interface adapt across rooms without duplicating the layout for each space.
A Managed Fixture is any endpoint Verana controls or tracks through the fixture model. It may be a DMX fixture, a Lutron-compatible zone, a relay, a shade, a sensor, an HTTP endpoint, or another supported control point.
The programmer works with spaces, looks, scenes, and intended behavior instead of rebuilding logic around every protocol.
In legacy workflows, feedback often has to be custom-built for each integration. Verana treats feedback as part of the fixture model.
Where a device or integration supports feedback, its state reports into one shared layer so operators and integrators can understand what the system is actually doing — not just what it was told to do.
Verana is designed for installations that mix device types. Each supported endpoint participates in the same Managed Fixture model.
No inbound firewall rules required at the site. Application sync and diagnostic access are separate trust levels.
DIN-rail and rack-mount controller options run the same Verana software model, with hardware selected based on fixture count, redundancy needs, and project scale.
Supported installations can run primary and secondary controllers with shared configuration and heartbeat monitoring. If the primary drops, the secondary takes over without requiring operators to reprogram the system.
Encrypted transport, scoped access, versioned configuration, rollback, and separate authorization levels for application sync and diagnostic access. If cloud access is unavailable, the local controller continues running the last valid configuration.
See how Verana models spaces, Managed Fixtures, touchpoints, feedback, and support workflows in a real installation.