HAPIO Software and Distribution Terms

CR8TEK (UEN 53531114A) is a sole proprietorship registered in Singapore at 60 Paya Lebar Road, #06-28 Paya Lebar Square, Singapore 409051. CR8TEK operates HAPIO. "CR8TEK" means CR8TEK. Contact: admin@cr8tek.com

1. Purpose

This document states what a Pilot participant receives, how Hapio may be copied, deployed, inspected and modified, and the mechanism, an offline signed licence file, by which a licence is verified. It exists to make the boundary between what is technically possible and what is contractually permitted explicit, since Hapio deliberately ships with readable source and no technical lock. It also states how this will extend once Hapio is available for purchase.

2. Scope

This document applies to every Pilot deployment of Hapio and, once available, to every purchased licence. It forms part of the Terms of Use and uses its definitions.

3. Definitions

4. Policy Statement

CR8TEK delivers a bundle the Customer runs on its own infrastructure, not a hosted service and not an installer that reports home. Licensing is enforced by agreement and by an offline signed Licence File, not by a technical lock on the code. The bundle contains readable application source and configuration, and CR8TEK treats that as a feature, not a risk to be obscured. What is and is not permitted with that source is stated in this document.

5. Roles and Responsibilities

6. Requirements

6.1 What the Customer Receives

The deliverable is a bundle the Customer runs on its own infrastructure, not a hosted service and not an installer that reports home. It contains:

1. container images for Hapio, delivered as a portable archive;
2. the compose and configuration files needed to run it;
3. an example environment file documenting every setting;
4. the documentation;
5. a script and instructions for obtaining the local model weights from their publishers. Hapio runs both its embedding model and its language model locally, so both sets of weights must be staged. CR8TEK does not ship large model weights inside the bundle; the Customer stages them through its own controlled channel.

Where a Licence File is issued for a Deployment, it is delivered with the Bundle.

Hapio is not currently available for purchase through any storefront. Delivery, today, is arranged directly with CR8TEK for each Pilot. The bundle is never published to a public container registry or a public bucket, and this will remain true once a general distribution mechanism exists.

6.2 Scope of a Deployment

One Pilot, or once available, one licence, covers one production Deployment: one running installation of Hapio, operated by the Customer, for one organisation, in one production environment.

Included at no extra cost, on the same Pilot or licence:

1. development, staging and test copies used by the Customer's own team;
2. one standby copy for disaster recovery, provided only one copy serves live users at a time;
3. backup copies of the bundle and images;
4. moving the Deployment between the Customer's own servers, data centres or cloud accounts. The Pilot or licence follows the organisation, not a machine.

A second production Deployment, or a Deployment operated for or on behalf of anyone other than the Customer, needs a separate written agreement with CR8TEK. CR8TEK does not count seats, users, questions, documents or servers, and nothing in the software meters them.

6.3 Redistribution

The Customer must not, without CR8TEK's written agreement:

1. sell, resell, rent, lease, lend, sublicense or give away Hapio, the bundle, the images, or its Licence File;
2. publish it to any public or shared registry, package index, file host, torrent or repository;
3. include it in another product, appliance, image or distribution;
4. run it as a service for third parties, or host Deployments on behalf of clients.

The distinction is between who the Customer serves and who it gives the software to. Serving the Customer's own end users through its own Deployment is exactly what Hapio is for, and is fully permitted. Without a separate written agreement, the Customer must not give the software itself to another organisation, or operate deployments as a service for other organisations. A redistribution or white label agreement can be requested by emailing admin@cr8tek.com. Its terms will be published here once CR8TEK offers one on a standard basis.

6.4 Inspection, Modification and Reverse Engineering

CR8TEK does not represent the code as hidden. The bundle contains readable application source and configuration. Anyone who runs it can open a shell in the container and read what they are running. CR8TEK considers that a feature: a regulated buyer running software inside its own perimeter should be able to audit it, and an obfuscation layer would only be theatre that made the Customer's own security review harder.

So the restriction sits where it belongs, in the agreement, not in a technical measure.

The Customer may:

1. read, audit, scan and security test Hapio in its own Deployment;
2. debug it, instrument it and inspect its behaviour;
3. modify or extend it for its own Deployment, at its own risk. A modified Deployment is unsupported;
4. do anything the law expressly permits regardless of contract, including any act permitted under the Copyright Act 2021 of Singapore for interoperability or security testing. Nothing here limits those rights.

The Customer may not, without CR8TEK's written agreement:

1. use the Software, or anything learned from reading it, to build or help someone else build a competing or substantially derivative product;
2. extract components, prompts, retrieval logic, schemas or configuration to reuse outside its own Deployment;
3. distribute a modified version to anyone.

The Customer may not, in any case:

1. remove, disable, alter or work around any licence verification;
2. remove or alter the copyright, attribution or licence notices of the open source components or the model publishers. Those notices are not CR8TEK's to waive.

Ownership of the Software and of any modification's underlying rights stays with CR8TEK. The Customer owns the changes it writes, and may not distribute them in a form that includes CR8TEK's code without CR8TEK's written agreement.

6.5 The Licence File

Where CR8TEK issues a Licence File for a Deployment, licensing is enforced by an offline signed file. There is no licence server and no activation call.

1. The file records the Deployment: the buyer, the issue date, and, where applicable, the date a maintenance or support period ends.
2. It is signed with an Ed25519 key. The corresponding public key ships in the artefact; the private key never leaves CR8TEK's control and never ships.
3. The software verifies the signature locally, at startup, with no network access. Verification works in an environment with no network connection at all.

Behaviour. The check warns; it does not lock the Customer out. If the file is missing, malformed, or past any stated maintenance date, the software says so in the logs and keeps running. This is a deliberate support decision: a Deployment with no automatic contact to CR8TEK has no way for CR8TEK to correct an incorrect verification result outside business hours. None of this is permission to run without an agreement in place. Running Hapio without one is a breach of the Terms of Use, whether or not the software stops the Customer.

Confidentiality. The Customer must keep its Licence File confidential. It identifies the Deployment it was issued for. Sharing it is a material breach.

6.6 Transfer and Change of Control

A Pilot or licence is not transferable. The Customer may not sell, assign or pass it to another organisation.

One exception. If the Customer's business, or the business unit that operates the Deployment, is sold, merged or reorganised, the Pilot or licence may transfer once to the successor, provided:

1. CR8TEK is notified in writing at admin@cr8tek.com within 30 days of the transfer;
2. the successor accepts these terms and the Terms of Use in full;
3. the successor does not use the transfer to increase the number of Deployments.

A change of ownership or control of the Customer's own organisation, with the Deployment staying in the same entity, is not a transfer and needs no notice.

6.7 Components From Other Companies

The Software includes open source components licensed by their authors under their own terms, included in the bundle and prevailing for those components. Nothing in these terms restricts a right the Customer has under an open source licence.

Model weights are licensed by their publishers, not by CR8TEK. This applies to both the local embedding model and the local language model Hapio runs. CR8TEK selects permissively licensed models and records the licence for each in the documentation, but the Customer obtains them from their publisher and uses them under that publisher's terms.

7. Procedures

7.1 Security Reporting

Report a vulnerability to admin@cr8tek.com. CR8TEK asks for a reasonable period to issue a fix before publishing. CR8TEK does not offer a paid vulnerability disclosure reward, but will credit the reporter on request.

7.2 Requesting Redelivery

If the Customer's copy of the bundle or its Licence File is lost, it should email admin@cr8tek.com.

8. Exceptions

The single change of control exception to the rule against transfer is stated in Requirements 6.6. No other exception to this document applies without CR8TEK's written agreement.

9. Compliance and Enforcement

A breach of the redistribution, inspection or licence file conditions in this document is a material breach of the Terms of Use.

9.1 On Termination

If a Pilot or licence ends, the Customer must stop running the Software, delete the images, containers and bundle from its systems, and confirm this in writing if CR8TEK asks. Data the Customer created, its documents and its database, is its own and is not affected.

10. Review and Maintenance

CR8TEK reviews this document at least once every 12 months, and sooner on any material change to the licence file mechanism or to how Hapio is sold. This document will be extended with purchase specific redistribution and transfer terms before Hapio is offered for sale.

11. References

• Terms of Use: the agreement this document forms part of.
• Acceptable Use Policy: conditions on use.
• Copyright Act 2021 (Singapore).

12. Governing Law

These terms are governed by the laws of Singapore.