Terms of Use

Last Updated: 30 August 2026

1. Introduction

These Terms of Use and License Agreement (“Terms”) govern the use of RelayQ software (“RelayQ”, “Software”, “Runtime”) provided by Precocity Research Limited (“we”, “us”, “our”).

RelayQ is provided as a licensed software runtime designed for deployment within edge systems, embedded devices, and customer-controlled environments.

RelayQ software is licensed to you under the Elastic License 2.0 (ELv2). A copy is published at /legal/license/ and is included with every distribution.

Scope and order of precedence. The ELv2 licence governs your rights in the software. These Terms govern your use of this website and any services offered through it. If a provision of these Terms conflicts with the licence in respect of the software, the licence prevails to the extent of the conflict. Nothing in these Terms is intended to restrict, condition, or extend the rights granted by the licence.

By installing, accessing, or using RelayQ, you agree to be bound by these Terms.

2. License Grant

RelayQ is licensed, not sold.

Subject to these Terms, ELv2, and any applicable commercial agreement, we grant you a limited, non-exclusive, non-transferable license to:

• Install and execute RelayQ in approved environments or deployment contexts
• Use RelayQ for internal business purposes or agreed deployments
• Integrate RelayQ with external systems using documented interfaces

The permitted scope of use may be defined based on:

• device
• deployment
• environment
• or other agreed licensing units

3. Deployment Model

RelayQ is delivered as a self-contained software runtime designed for deployment on edge systems or customer-controlled infrastructure.

• RelayQ operates independently of hosted services unless expressly agreed
• Configuration, operation, and integration are managed by the deploying party
• RelayQ operates as a data ingestion, processing, and messaging layer within a single execution boundary and does not replace primary control or protection systems

4. Evaluation and Pilot Use

RelayQ may be provided for evaluation, testing, or pilot use:

• Evaluation is provided as a full-featured runtime limited to 24 hours per start, 72 hours of cumulative runtime, and 30 days from the first run. The runtime shuts down gracefully at the end of each 24-hour period and may be restarted until either further limit is reached, after which it will not start without a licence file. Production use requires a licence file. These terms apply unless otherwise agreed in writing
• Scope, performance, or functionality may be restricted
• Evaluation use is provided “as is”, without warranty
• The evaluation edition is not suitable for production use. It is provided solely for assessment, testing, and proof-of-concept purposes. We accept no responsibility or liability for any loss, damage, or disruption arising from the use of the evaluation edition in production or operational environments.

Pilot integration effort and resource allocation will be mutually scoped and agreed prior to commencement.

5. Commercial Use and Payment

Commercial use of RelayQ is subject to a separate agreement defining:

• pricing
• licensing scope
• payment terms
• deployment scale

Unless otherwise agreed:

• Fees are payable according to issued invoices
• Failure to pay may result in suspension of license rights after reasonable notice
• Refunds, if applicable, are governed by the relevant commercial agreement

6. Support and Maintenance

RelayQ is a maintained, version-controlled software runtime.

Support, response times, and service levels are defined under applicable support agreements or service plans.

• Commercial deployments may include defined response times and update access
• Evaluation use does not include guaranteed support unless expressly agreed

7. Permitted Use

You may:

• Deploy RelayQ within the licensed scope
• Use RelayQ to process, route, and transform data
• Integrate RelayQ with internal or external systems
• Operate RelayQ on approved hardware or infrastructure

8. Restrictions on the Software

Your rights in the software, and the limits on them, are set out in the Elastic License 2.0: see /legal/license/. We do not restate or add to them here, so that there is one authoritative statement rather than two.

For reference, the licence already provides that you may not:

• provide the software to third parties as a hosted or managed service where the service gives users access to a substantial set of its features;
• move, change, disable, or circumvent the licence key functionality, or remove or obscure functionality protected by the licence key; or
• alter, remove, or obscure any licensing, copyright, or other notices.

The licence is also non-sublicensable and non-transferable, and grants no rights in our trademarks.

9. OEM, White-Label, and Redistribution

Some arrangements need rights the Elastic License 2.0 does not grant, in particular the ability to sublicense RelayQ to your own customers, to distribute it under your own brand, to provision licence keys on devices you ship, or to use our trademarks. Because we hold the copyright in RelayQ, we can grant those rights separately.

Those rights are available under a separate written commercial agreement. If you intend to embed RelayQ in a product you sell, to white-label it, or to offer it to your customers under your own terms, contact us at info@precocity.nz.

Note that production use of RelayQ requires a valid licence file in every case. Evaluation mode is limited to 24 hours per start, 72 hours of cumulative runtime, and 30 days from the first run, after which the runtime will not start without a licence.

10. Partner Responsibilities (Deployment and Integration)

The deploying party is responsible for:

• System configuration and integration
• Providing suitable hardware or runtime environments
• Connectivity to external systems (e.g. Modbus-enabled devices)
• Providing relevant protocol documentation (e.g. register maps)
• Operational monitoring and deployment management

This includes ensuring safe operation within industrial or regulated environments.

RelayQ operates as a software runtime within a broader system and does not assume responsibility for full system behaviour. RelayQ enforces bounded behavior within its runtime but does not guarantee correctness of external systems or integrations.

Message flows (including MQTT messaging) may be used to control actuators, trigger actions, or influence physical systems. We accept no responsibility for any damage, injury, or loss resulting from faulty system design, misconfiguration, or inadequate testing. All deployments should be thoroughly assessed in a test environment before being deployed in production or safety-relevant contexts.

11. Data Ownership

All data processed through RelayQ remains the property of the customer or originating party.

• RelayQ does not claim ownership of user data
• Data control, retention, and usage remain with the deploying party

12. Intellectual Property

All intellectual property rights in and to RelayQ, including:

• software
• architecture
• designs
• protocols
• documentation

remain the exclusive property of Precocity Research Limited and its licensors.

No ownership rights are transferred under these Terms.

13. Source Code

RelayQ is distributed as compiled software (binary runtime) only.

• Source code is not provided under these Terms
• Any access to source code requires a separate written agreement

14. Confidentiality

Any non-public or proprietary information exchanged between the parties shall be treated as confidential and used solely for:

• evaluation
• integration
• deployment
• agreed collaboration

15. Website and Portal Use

Use of the RelayQ website, documentation, and associated services must remain lawful and appropriate.

You agree not to:

• misuse forms or services
• attempt unauthorized access
• interfere with the operation of services

We reserve the right to suspend or restrict access in cases of misuse.

16. Trademarks

“RelayQ” and associated marks are trademarks of Precocity Research Limited.

All third-party names, protocols, and technologies (e.g., Modbus) are used solely for identification and interoperability purposes.

17. Limitation of Liability

To the maximum extent permitted by law:

• Evaluation use is provided “as is”, without warranty
• Commercial use is subject to applicable support and service agreements
• We are not liable for indirect, incidental, or consequential damages

The deploying party is responsible for system design, integration, and operational outcomes.

18. Termination

This license terminates if:

• you breach these Terms
• you exceed the licensed scope
• applicable commercial agreements expire or are terminated

Upon termination:

• You must cease use of RelayQ
• Deployed instances must be removed unless otherwise agreed

Running instances will not be remotely disabled after license expiry. However, any restart (power cycle, watchdog, or manual restart) will fail license validation and the runtime will not resume. In such cases, continued operation does not grant rights to:

• updates
• support
• new deployments
• expanded licensing scope

19. Non-Exclusivity

These Terms do not grant exclusivity.

Any exclusivity arrangement must be agreed separately in writing.

20. Governing Law

These Terms are governed by the laws of New Zealand, unless otherwise agreed in writing.

21. Contact

For licensing, support, or commercial inquiries, use the contact form.