Skip to content
LumenFlow

Licensing & Access

LumenFlow is proprietary software licensed by Hellmai Ltd, a company registered in England and Wales (company number 16412231). The licence terms are included with every package and apply from first use. LumenFlow is not distributed under an open-source license.

Access

Section titled “Access”

Access to LumenFlow distributions, packages, and infrastructure is granted by arrangement. To request access or discuss a licensing arrangement, contact licensing@lumenflow.dev.

First-run acceptance

Section titled “First-run acceptance”

First-party npm packages reference their included full proprietary terms through "license": "SEE LICENSE IN LICENSE" or "SEE LICENSE IN LICENSE.md" in package.json. Both filenames are supported; the delivered terms must match the approved canonical licence byte for byte. Before the first governed CLI command runs on a machine, the CLI prints a short acceptance notice referencing that file and asks you to accept:

LumenFlow is licensed, not sold: SEE LICENSE IN LICENSE (the LICENSE file
included with this install). By accepting, you agree to those terms.
Type "accept" and press Enter to accept these terms (or set
LUMENFLOW_EULA_ACCEPTED=1 and re-run):

Type accept (or y/yes) and press Enter. A small acceptance record is then written under your per-OS user config directory (next to the cached licence file), and every later command on that machine runs without prompting again. Declining, or running with no input available and no acceptance recorded, refuses with the same remedy.

On a non-interactive host (CI runner, container build, scripted install) where no one can answer the prompt, set the environment variable before running any command:

LUMENFLOW_EULA_ACCEPTED=1

pnpm lumenflow:doctor reports the current acceptance state (accepted, with the timestamp, or not accepted, with the same remedy) alongside the licence status.

Third-Party Software

Section titled “Third-Party Software”

LumenFlow depends on third-party libraries that remain under their own licenses. Dependency manifests in each package are the authoritative source for third-party attribution.

Section titled “Related Legal Pages”