Licensing

Community Edition runs without a license; it is ideal for evaluation and small deployments.

Community Edition limits

• One built-in worker (external workers require a license)
• Up to 15 jobs across the workspace
• Daily processing volume cap of approximately 250 GB/day
• Licensed-only connectors and features remain unavailable in Community Edition

Use this guide when you are ready to upgrade so you can add external workers, raise limits, and unlock licensed-only features and support.

Request a free evaluation license via email using the license request form.

Evaluation license limits

Evaluation licenses are time-limited and include a daily processing volume cap and a worker limit. The exact limits depend on your evaluation program; after activation, check Settings → License for the values shown in your License Summary.

For production or higher-throughput deployments, contact us to review available licensing tiers and pricing.

Configuring a server license

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

1. Sign in to the UI as admin using the one-time password from the server log.
2. Open the main navigation menu and choose Settings → License.
3. Click Change license, paste your key, and select Activate.

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:

# 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.