Community Edition

Note

Review Licensing if you expect to move from Community Edition to a licensed edition; it explains how to request keys and automate activation.

LyftData exposes two broad runtime states in the product UI:

• Community: constrained surfaces and limits for evaluation, local development, and CI.
• Licensed: production-oriented surfaces and limits based on signed license claims.

The 3.0.0 beta-track edition ladder is:

• Community Edition: no license configured; one built-in Worker, at most 15 jobs, the local 250 GB/day rate limiter, and MCP included.
• Community+: licensed and free, renewed annually; 1 TB/day observed with no product rate limiter, one Worker, and all generally available self-managed features.
• Standard Edition: paid; from 1 TB/day scaling by committed TB/day, with no licensed Worker limit.
• Enterprise Edition: paid and negotiated; no licensed throughput or Worker limit.

Volume entitlements use decimal units: 1 GB is 10⁹ bytes and 1 TB is 10¹² bytes.

Community edition at a glance

Community Edition surfaces and limits are active when no license key is configured.

• No activation required – the system recognizes the missing license and treats it as a valid Community Edition state.
• One worker – the built-in worker is always available; external workers cannot be added or enrolled and the built-in worker cannot be removed.
• 15 job limit – job creation and cloning calls are capped at 15 total jobs (existing jobs can still be edited or redeployed).
• Daily volume limit – processing is rate-limited to approximately 250 GB/day in Community Edition.
• MCP included – the MCP server is part of the Community Edition feature set.
• Feature gating – licensed-only connectors and capabilities remain disabled in Community Edition.
• Core API availability – control-plane APIs remain available so dashboards and automation can operate in constrained mode.

These are boundaries of the unlicensed edition. They are not applied to licensed editions; see Observe and assist.

Why community edition exists

Community Edition gives teams a frictionless way to explore LyftData and to run lower-scale automation locally:

• Try the platform quickly – no keys or activation steps are needed before creating jobs and running them.
• Local & CI usage – ideal for test suites, proofs of concept, or developer environments that only need the built-in worker.
• Seamless migration – once you activate a licensed key, Community limits are lifted without rebuilding your existing jobs.

Feature comparison

Capability	Community Edition	Community+	Standard Edition	Enterprise Edition
License requirement	None	Licensed; no charge; renewed annually	Paid license	Paid, negotiated license
Worker entitlement	Built-in worker only	One Worker	No licensed Worker limit	No licensed Worker limit
Job count	At most 15 jobs	No job maximum	No job maximum	No job maximum
Daily volume	250 GB/day, applied by the local rate limiter	1 TB/day, observed with no rate limiter	From 1 TB/day, by committed TB/day	No licensed throughput limit
MCP	Included	Included	Included	Included
Other features	Licensed-only connectors/capabilities are disabled	All generally available self-managed features	All generally available self-managed features	All generally available self-managed features
Commercial posture	Local edition boundaries apply	Usage observed for evidence and true-up	Usage observed for evidence and true-up	Usage observed; no volume or Worker true-up condition

Hosted or managed services, professional services, and support packages are contracted separately and are not product-feature gates.

Operating in community edition

When a server is running in Community Edition you will see the following behaviours:

• License and features views in the UI show Community surfaces.
• Job creation requests return a descriptive error once the 15-job limit is reached.
• Job cloning is also blocked once the job cap is reached.
• Worker APIs reject attempts to add or enroll additional workers and refuse to remove the built-in worker.
• Throughput is rate-limited against the Community daily-volume limit.

None of the above applies to Community+, Standard, or Enterprise: on licensed editions, commercial posture is observed and reported, and operations continue.

For automation and health checks, prefer /api/features (license_status.edition and license_status.tier) plus /api/license/show details, rather than assuming “license configured” means unrestricted.

Reading license_status

Current builds report the following values. These are the API values in the shipping product; they have not yet been renamed to the v3 edition names.

• license_status.edition: Community or Licensed.
• license_status.tier: FreeCommunity when no license is configured, CommunityPlus for a configured license that still resolves to Community Edition surfaces, and Licensed for a configured licensed-edition key. Older keys can also report the legacy tier values Free, Starter, Growth, or Enterprise.

Treat license_status as an indicator and read /api/license/show for the entitlement actually in force. A key issued before the current edition ladder can still report a legacy tier value.

Activating a license

Moving out of Community Edition is straightforward:

1. Acquire a license key — start with free Community+ activation, or request a Standard or Enterprise key from LyftData. Community+ requires no charge and renews annually.
2. Activate the license in Settings → License or provide LYFTDATA_LICENSE at startup for automation.
3. Refresh – as soon as activation succeeds, Community Edition limits are lifted. Community+ removes the rate limiter and the 15-job maximum, and neither is re-enabled afterwards.
4. No reconfiguration required – jobs, history, and settings remain intact.

Monitoring & best practices

• Detect edition explicitly – call GET /api/features and inspect license_status.edition plus license_status.tier instead of assuming license_configured=true means unrestricted.
• Plan for limits – watch job counts and worker requirements; activate a license before hitting Community caps.
• Observe volume – add alerts around daily volume consumption in Community Edition environments.
• Document your activation process – because activation is seamless, most teams just need a runbook describing where the license key lives and who can apply it.

Community Edition is ideal for learning and early pipeline development. When you need to remove the rate limiter and the job maximum, activate free Community+. When you need multiple Workers, more than 1 TB/day, or a commercial procurement relationship, move to Standard Edition; Enterprise Edition is the negotiated edition with no licensed throughput or Worker limit.