Verana lets programmers build reusable touchpoints from blocks, then maps each control to the correct space, scene, role, device, and room-combine state. Operators get simple controls. Integrators get flexible deployment. The system stays capable without turning every room into a custom one-off.
The building runs locally. Cloud-assisted tools make support, updates, and diagnostics easier when connected.
Deploy the same touchpoint layout across rooms. Each touchpoint resolves its own space, scenes, roles, defaults, and room-combine state, so operators see the right controls without custom panel logic for every location.
A single ON button can load the correct scene for Ballroom A, Ballroom B, or the combined room because Verana maps the action through touchpoint context.
See context-aware touchpoints →In legacy systems, giving eight ballrooms individual scene control means eight duplicated configurations. Change a color and you change it eight times.
A look in Verana is a reusable definition — not a copied scene tied to one room. Define it once. Apply it to every space that needs it. When something changes, it changes once, everywhere.
See how looks work →Verana treats supported endpoints as Managed Fixtures: anything the system controls or tracks through the fixture model. DMX fixtures, Lutron-compatible zones, relay outputs, shades, sensors, and HTTP devices can all participate in the same looks, triggers, shared feedback, and support workflows.
Where a device or integration supports feedback, its state reports into one shared layer — giving integrators a consistent view of what the system is actually doing, not just what it was told to do.
See the fixture model →The local controller operates the installation. Cloud services provide remote visibility, diagnostics, updates, and AI-assisted workflows when connected. Because local and cloud tools share the same system model, support understands spaces, looks, touchpoints, and fixture state — not just open ports.
RDM discovery, auto-suggested matches, verified write where supported, and a structured report exportable as PDF for the field team.
Build one interface, deploy it across rooms. Each touchpoint resolves its own space, scenes, roles, and room-combine state — no duplicate panel logic.
Ask the system anything in plain English. AI drafts proposed changes for review. It accelerates your work without taking decisions away.
Tell us what you are trying to control, who needs to operate it, and where support gets painful. We'll show how Verana would model the installation.