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
• Each worker can run up to five concurrent jobs and only the asic job type

Use this guide when you are ready to upgrade so you can add external workers, lift the concurrency/job limits, or unlock production support.

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

Note

Evaluation licenses are valid for 45 days and accommodate up to 500 GiB of data processing per day, on up to 15 workers.

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 Lyft Data 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 Manage → 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
LYFTDATA_LICENSE="<paste-your-license-jwt>"

• When set, the Server will pick up the provided license at startup and override any existing license.
• For first-run automation, you can also accept the EULA via LYFTDATA_LICENSE_EULA_ACCEPT=yes.

See also: Reference -> Configuration for details on these environment variables.