Skip to content

Licensing

This page describes licensing in LyftData 3.0. Community Edition runs without a license; it is ideal for evaluation and small deployments. Licensed editions carry signed entitlement claims for volume, Workers, and feature grants.

Volume entitlements on this page use decimal units: 1 GB is 109 bytes and 1 TB is 1012 bytes.

Use this guide when you are ready to activate a license. Community+ removes the Community rate limiter and job maximum but remains built-in-worker-only; Standard and Enterprise are the editions that support external Workers.

Edition License Volume entitlement Worker entitlement Product features
Community Edition No license required 250 GB/day, applied by the local rate limiter One built-in Worker Community feature set, at most 15 jobs, MCP included
Community+ Licensed; no charge; renewed annually Current offer: 1 TB/day, observed with no product rate limiter One built-in Worker; external Workers are not supported All generally available self-managed features, plus the embedded AI runtime, the Operator agent (Preview), and Data Awareness (Preview); admission-only connector ceiling from the signed license (current offer: 7 active sources / 5 active destinations)
Standard Edition Paid — contact the LyftData team Committed daily volume allowance set in the signed license; the current Standard offer starts at 1 TB/day Built-in and external Workers supported; no licensed Worker or connector ceiling All generally available self-managed features, plus the embedded AI runtime, the Operator agent (Preview), and Data Awareness (Preview)
Enterprise Edition Paid and negotiated — contact the LyftData team No licensed throughput limit Built-in and external Workers supported; no licensed Worker, connector, or throughput ceiling All generally available self-managed features, plus the embedded AI runtime, the Operator agent (Preview), and Data Awareness (Preview)

“No licensed limit” and “all generally available self-managed features” describe the commercial software entitlement. They do not promise unlimited technical capacity or unsupported topologies — capacity remains bounded by the infrastructure you deploy and the architecture LyftData supports. The embedded AI runtime, Operator agent, and Data Awareness are Preview features; they need an AI provider account and separate per-feature consent. Hosted or managed services, professional services, and support packages are contracted separately and are not product-feature gates.

Community+ is the registration and activation step between anonymous Community use and paid Standard use. Activating Community+ removes the Community rate limiter and the 15-job maximum, and neither is re-enabled afterwards. Standard conversion is the next step when a deployment needs external Workers, more than 1 TB/day, or a commercial procurement relationship. Enterprise is not a further feature-unlock step; it is the negotiated edition with no commercial ceiling.

On licensed editions — Community+, Standard, and Enterprise — LyftData observes usage to produce evidence, rather than stopping already-running work.

  • Commercial non-compliance never stops, throttles, disables, undeploys, or otherwise interrupts already-running operations.
  • Exception (Community+ only): adding a source or destination connector beyond the signed connector-scope limit is refused at admission (connector_scope_limit_exceeded). Under the current Community+ offer of 7 sources and 5 destinations, that is an 8th source or a 6th destination. Equal-count replacements and reducing repairs remain allowed. Standard and Enterprise have no licensed connector ceiling.
  • Usage above your volume entitlement is recorded as evidence and, where it meets the applicable review conditions, leads to an assistive true-up conversation handled contractually.
  • Community Edition’s rate limiter, 15-job maximum, and connector-type denylist are boundaries of the unlicensed edition. Activating Community+ removes those, and keeps the admission-only connector ceiling from the signed license (7 sources / 5 destinations in the current offer).
  • Missing or stale usage evidence is shown as missing or stale; it is not converted into an assumed compliance result.

Security trust and resource safety are separate and unchanged. A forged or cryptographically invalid license, an explicit security revocation, bounded backpressure, and resource-exhaustion protection are not commercial metering actions.

Commercial offers are sales-assisted. Contact the LyftData team for license or evaluation assistance and the applicable signed terms. Portal access does not imply that a self-service offer is available.

For production or higher-throughput deployments, contact us to review the Standard and Enterprise editions.

To configure a license on a LyftData server, follow these steps:

  1. Download your signed license JWT from the LyftData Portal.
  2. Sign in to the Product UI with your existing administrator account.
  3. Open Settings → License → Activate.
  4. Expand Advanced: Full License Key, choose Load from file, and select the downloaded JWT file.
  5. Select Activate License, then check Settings → License for the verified entitlement and activation result.

Loading the file only fills the license input; it does not activate the license. Product verification determines the authority granted by the signed JWT.

Alternative: provide license via environment variable

Section titled “Alternative: provide license via environment variable”

You can provide a license non-interactively on server startup using the LYFTDATA_LICENSE environment variable. This is useful for automation:

Terminal window
# example: systemd EnvironmentFile or shell export before starting
export LYFTDATA_LICENSE="<paste-your-license-jwt>"
  • When set, the server uses this value as a bootstrap license at startup.
  • If no license exists yet, it is applied automatically.
  • If an existing stored license is invalid, the bootstrap license is used to replace it.
  • If a valid stored license already exists, release builds keep the existing license.
  • For first-run automation, you can also accept the EULA via LYFTDATA_LICENSE_EULA_ACCEPT=yes.

See also: Configuration for details on these environment variables.

Worker authorization leases are capped at the entitlement expiry. When authority expires, unsafe Jobs lose authorization; the Worker management and recovery loop remains reachable to renew, replace, or recover authority. The product warns you ahead of time:

  • The server logs a warning 14 days before license expiry and again 3 days before.
  • The license health badge in the header and Settings → License apply warning styling at the same thresholds.
  • Workers log a local warning when their authorization lease approaches those thresholds.
  • Community Edition never warns — it does not expire.

Renew and activate the new license before expiry; workers pick up new leases automatically and jobs continue without interruption. If an external-Worker-capable entitlement expires, activating a valid signed entitlement that authorizes external Workers recovers those Workers automatically within a few minutes — no worker restart is needed.

Replacing or clearing a configured license

Section titled “Replacing or clearing a configured license”

Use the authenticated license-management surface to replace or clear a configured entitlement. Clearing or losing a configured entitlement does not automatically reopen the no-JWT Community profile: ordinary licensed authority closes safely while renewal, replacement, revocation discovery, license administration, and status/recovery remain reachable.

Do not use license clearing as a topology conversion. A valid signed entitlement that authorizes external Workers restores their authority automatically after activation; Community+ remains built-in-worker-only even though it is licensed.