Roadmap

Last updated

We publish a rolling view of what's coming because the people backing this work — Stripe subscribers, customers, and the wider theatre community — should know what their support is funding. None of the items below come with hard dates: estimates we'd commit to in writing rarely survive contact with the soldering iron.

Recently shipped

The v7 firmware family has been the largest single overhaul since the product launched.

  • v7.2.1 — Status LEDs mirrored live in the web UI's status page.
  • v7.2 — Per-direction status-LED state machine. Dedicated colours for DMX vs pixel mode so you can read each port's role from across the room.
  • v7.1 — Ground-up rewrite of the web UI as a single-page application backed by a REST API. Per-device unique MAC. Live diagnostics dashboard. WiFi removed entirely (the dualETH hardware never used it; removing it freed memory and dropped power draw).

Coming next

The next short cluster of releases focuses on features the product has half-supported for a while but never quite finished.

  • Scenes — record a DMX snapshot to the device, recall it later from a console or trigger it standalone. Useful for installations that need a fallback when the network goes quiet.
  • More pixel effects — colour wipe, fire, meteor, plasma. All driven from FX12 mode so they're console-controllable.
  • sACN priority handling — multi-source priority per the E1.31 spec. Important for redundant-console setups.
  • Backup / restore configuration — export and import a device's full settings as a JSON file. Reconfigure 30 nodes from one template instead of one at a time.
  • .local device discovery — find the node by hostname instead of by hunting for an IP address.

Exploring

Further out, less certain, no commitment. We mention these because we'd rather you knew what we're thinking about than be surprised later.

  • Next-generation hardware platform with more memory and headroom. Same firmware feature set, more capacity for pixels and effects per port.
  • Signed firmware updates so the updater can refuse anything not built and signed by us.
  • Console-driven firmware push (Art-Net 4 OTA). Eos and similar consoles can already push firmware to compatible nodes; we'd like to support that.

How we prioritise

Bug reports beat feature requests, every time. Within features, we weigh how often a thing comes up in support, how many existing customers are affected, and what subscribers via Stripe tell us they want. If something on this list matters to you specifically — or you don't see something that should be there — drop us an email. We read every one.