Docs / dflux TinyCore
ContactGet started

Licensing

Community builds run without a license file. One optional tinycore grant from dflux covers every NF process. This page explains where the file lives when you have one, and how grace and renewal work.

Unsigned community builds are fail-open: no license file is required, and each NF starts without one.

A signed license from dflux for the tinycore product is optional. When you have one, every NF binary — d3x-core-nrf, d3x-core-dmf, d3x-core-dpf, d3x-core-upf, and the optional d3x-core-nssf / d3x-core-smsf — reads the same grant. There is no separate license per NF: point every binary at the same file. The license is yours to keep; only the download link for the binaries is time-limited.

Default path

When a signed file is present, resolution is:

  1. D3X_LICENSE_FILE when set (explicit override).
  2. /etc/dflux/d3x.lic when that compound file exists.
  3. /etc/dflux/tinycore.lic — per-product fallback.
Bash

Overriding the path

Point every NF at a custom path with the environment variable:

Bash

There is no -license-path flag and no license_path config key — path selection is solely via D3X_LICENSE_FILE or the default files under /etc/dflux/.

Startup output

With no file, each NF starts with no licensed-to line. With a signed file, each NF logs who it's licensed to, the edition, and the expiry:

Code

Grace and expiry

When a signed file is present, the gate enforces product scope and expiry (with a grace window). Once running, each NF re-checks daily and escalates warnings as expiry approaches or passes — it does not self-terminate the data plane.

Offline and air-gapped

License verification is fully offline. No NF phones home, contacts a license server, or needs any network access to validate the license — verification happens locally from the file alone. dflux TinyCore runs unchanged in air-gapped environments.

Renewal

To renew, request a fresh license file from dflux and replace the file in place — overwrite /etc/dflux/tinycore.lic (or whatever path D3X_LICENSE_FILE points at) and restart each NF. The new licensed-to / expires line in the startup log confirms the renewal took effect. Because the file is shared, you only update it once per host.

Where to go next

Ready to bring the core up? Follow the Quickstart, or install the binaries first with the Installation guide.