The primary area of difference is in the supported platforms. Most light orchestration software we've encountered works on the Microsoft* Windows* platform only. Lumos was designed with the goal of running on as many different platforms as possible. It's being developed on FreeBSD*, and tested on Linux*, FreeBSD, Windows, and Mac OS X*. In theory, it should run on just about anything.
Secondly, the way it goes about updating the light controller hardware is different. Vixen, for example, handles events as individual snapshots capturing the state of every output channel at each instant in time. A typical device plug-in would just take that data and update every channel on each controller, regardless of whether they all changed state or just a single channel did. While several SSR controllers expect to be updated that way, not all do, and individually addressing the specific channels which change can be more efficient (depending on how much is being updated at one time). Lumos handles channel events separately so the choice of whether to send complete device updates or individual channel changes can be made by each device driver as appropriate for the hardware it's driving.
Thirdly, Lumos is completely open source and full source code is provided. We fully respect the decision of other developers to keep their code proprietary, but for those users who would like a system they can open up and customize at any level, we wanted to provide a system which made that possible.
Finally, Lumos is a very new system, and is still somewhat spartan in “chrome plating” and user interface design. Lumos may be a wonderful choice for an experienced hobbyist who wants extra flexibility to experiment, but for a more casual user who only wants a way to get patterns of lights to blink from their Windows PC, a more mature program such as Vixen may still meet their needs better.
While Lumos theoretically ought to run on just about anything, we have verified and tested it so far on the following configurations without problems: