HYPER LIGHT
Get a licence

HYPER LIGHT End-User Licence Agreement

Version
1.1
Updated
2026-09-28
SHA-256
e5e3ff3c00502df6…

Draft, pending legal review. This text describes how HYPER LIGHT works today; the Owner's legal details and governing law are still to be confirmed, and it is not yet in force as a contract.

This End-User Licence Agreement (the "Agreement") is between HYPER LIGHT (the "Owner") and you, the person or organisation installing or using the HYPER LIGHT console software (the "Licensee"). The console shows this Agreement the first time it starts on a machine and does not start its DMX engine or check its licence until you accept it. By selecting Accept you agree to these terms. If you do not agree, select Decline and the software closes without having done anything.

1. Definitions

  • Software: the HYPER LIGHT lighting console, projection mapper and media server, its documentation, file formats and updates the Owner provides.
  • Licence File: a file the Owner issues for one machine, signed with the Owner's private key, that the Software checks offline.
  • Machine Code: a 25-character code the Software derives on the machine from hardware identifiers, used to bind a Licence File to that machine.
  • Evaluation: the period of full use a machine receives before it is activated.
  • Show File: a file the Software writes that describes a lighting show you create.

2. Grant of licence

  • The Owner grants the Licensee a non-exclusive, non-transferable licence to install and use the Software on the machine named by a Licence File, for the term that Licence File states (30 days, 90 days, 365 days or perpetual), subject to this Agreement.
  • Every machine receives an Evaluation of 14 days with every feature. After the Evaluation, until the machine is activated with a Licence File, the Software does not save show files and, from its next start, sends DMX on one universe only. Output that is running is never cut by a licence decision.
  • Show Files you create are yours. This Agreement gives the Owner no rights in them.

3. Licence protection

The Software protects its licence in several places at once, and the Licensee agrees not to interfere with any of them:

  • Licence Files are verified offline against the Owner's public key and must name the machine they run on.
  • The Evaluation's start, the last licence decision and the acceptance of this Agreement are each recorded in more than one place on the machine, sealed with the operating system's per-user data protection. A record that has been edited reads as restricted, not as a first start.
  • The Software detects a system clock set back behind the time it last saw.
  • An optional online check may renew a Licence File. It accepts only a newer Licence File signed by the Owner, and every failure leaves the machine as it was.

4. Restrictions

Except as expressly permitted in writing by the Owner, or where applicable law expressly permits it notwithstanding this limitation, the Licensee may not:

  • copy the Software other than for installation and backup on licensed machines;
  • reverse engineer, decompile, disassemble or otherwise attempt to derive the source code of the Software;
  • remove, alter, bypass or circumvent any licence check, Machine Code binding, Evaluation record, clock check, copyright notice or other protection in the Software, or help anyone else do so;
  • reset, extend or restart an Evaluation by any means, including deleting records, reinstalling, cloning a machine or changing its clock;
  • sell, rent, lease, lend, sublicense, distribute or otherwise transfer the Software or a Licence File;
  • use the Software to build a competing product.

5. Offline evaluation rules

  • The Evaluation belongs to the machine, not to an installation: reinstalling the Software does not start a new one.
  • A Licence File is checked at every start, without a network. A start whose check has not finished in time uses the last decision recorded on the machine.
  • A licence decision is made once, when the Software starts. A change during a session — an Evaluation ending, a Licence File expiring — takes effect at the next start.

6. Data

  • The Software computes the Machine Code on the machine. It leaves the machine only when the Licensee sends it: to the Owner's portal to request a Licence File, or to the Owner's licence service when activating or renewing.
  • The Software sends no usage data, analytics or telemetry. Its network traffic is the lighting and video protocols the Licensee configures (Art-Net, sACN and the like) and, only when configured, the licence service.
  • Diagnostic files the Software writes (logs, telemetry, crash reports) stay on the machine unless the Licensee chooses to send them.

7. Safety

  • The Software controls lighting, laser and video equipment. The Licensee is responsible for the safe installation and operation of all connected equipment and for compliance with the laws and standards that apply to it, including laser safety regulations.
  • BLACKOUT, the laser kill (F12) and every other control in the Software are operating controls, not safety devices. They do not replace an emergency stop, a laser interlock, a key switch, a qualified operator or any safety system the law or the equipment's manufacturer requires.

8. Third-party components

The Software includes components licensed by third parties, listed in THIRD_PARTY_NOTICES.md, which ships with the Software. Their licences govern those components, and nothing in this Agreement restricts rights they grant.

8.1 Third-party formats and interoperability

HYPER LIGHT provides import capabilities for third-party fixture personality formats (including Avolites .d4/.r20) strictly for software interoperability. All third-party trademarks, logos, and file specifications remain the property of their respective owners. HYPER LIGHT does not redistribute or sell third-party fixture libraries.

  • The Software reads such files from the Licensee's own installation of the third party's software, or from files the Licensee loads. The Licensee is responsible for holding the right to use them, and should obtain them from their manufacturer or publisher.
  • GDTF, an open standard, is the Software's primary fixture format. Import of the Avolites .r20 format is experimental: a file the Software cannot read is refused, never guessed at.

9. Updates and support

The Owner may provide updates, which this Agreement covers unless they come with their own terms. The Owner is not obliged to provide updates or support unless a separate written agreement says so.

10. Warranty disclaimer

To the extent permitted by law, the Software is provided "as is", without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose and non-infringement. Nothing in this Agreement excludes or limits a right a consumer has under the law of the country where they live that cannot be excluded or limited by agreement.

11. Limitation of liability

To the maximum extent permitted by law, the Owner is not liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of profits, revenue, data, use or goodwill, arising from the use of or inability to use the Software, including any interruption of a performance or event. The Owner's total liability under this Agreement is limited to the amount the Licensee paid for the Licence File concerned. Nothing in this Agreement limits liability for death or personal injury caused by negligence, or for fraud, where the law does not allow it to be limited.

12. Termination

This Agreement ends automatically if the Licensee breaches it. On termination the Licensee must stop using the Software and delete all copies. Sections 4, 6, 10, 11 and 13 survive termination.

13. Export

The Licensee will comply with the export control and sanctions laws that apply to the Software and its use.

14. Governing law

The governing law and courts of this Agreement are to be confirmed by the Owner before it comes into force.

15. The accepted text

The Software records which text of this Agreement was accepted — a SHA-256 digest of it — with the time, sealed on the machine. A later version of this Agreement is shown again and must be accepted before the Software starts.

16. Contact

Questions about this Agreement: through the Owner's portal, where Licence Files are requested.