LICENSING, MODULES AND DISTRIBUTION

Build with Developer. Deploy with the right entitlements.

Developer gives everyone free development and non-production testing rights, including employees and teams. Solo adds own-use production for eligible holders; customer deployments need separate licences.

Talk to sales Explore Community

Non-contractual pre-release: new terms planned from November 2026, subject to final LGC approval.

EXECUTION RIGHTS

One Runtime, four distinct entitlements.

Developer is not a separate Runtime build; Community is the ecosystem programme.

Free · non-production

Developer

Free after registration for individuals, employees, IT services firms, integrators and vendors. Build, test, run CI and acceptance tests, demonstrate and carry out non-production POCs without an overall development time limit. One Developer certificate is planned per registered developer, with five concurrent sessions per certificate: no shared team-wide limit, including across separate projects. Technical enforcement remains subject to acceptance. No production use is permitted.

Solo

Includes Developer plus one own-use production application for an individual or a business with exactly one distinct person in total, counting owners and employees. The application can serve personal or professional needs. Exceptional headcount cases require legal clarification.

Client Runtime

One entitlement per identified application and legal end customer. Chargeable from the first concurrent user, with no ceiling. Rights follow application concurrency, not the customer’s headcount. Catalogue pricing and contractual conditions remain subject to approval before public launch.

Standard and above

A platform for loading multiple applications. Actual build, availability and production qualification must be verified under contract.

Solo is for the eligible holder’s own needs. An application used by customers or other third parties needs the appropriate deployment entitlements; their use is not covered by Solo.

CUSTOMER EVALUATION

A customer POC is not production use.

Ordinary Developer work has no general expiry date. A POC at a prospect follows a separate procedure.

Before the POC

Provide LGC with the prospect, application, owner and proposed start date. Developer registration does not automatically register a customer POC; the declaration process remains subject to acceptance.

90 days, with confirmation

The period begins on the date confirmed in writing by LGC. Extension requires written approval before expiry. The POC must stay non-productive, even when tests use real data; any live business operation or decision requires production rights.

There is no catalogue Pilot licence. LGC-assisted POC services may be quoted separately. Customer project questions →

TWO DISTRIBUTION ROUTES

Store or direct white label.

A — Store

The Store is a planned channel for publishing and acquiring free or paid modules and applications, subject to component-specific licences. Self-service is not yet live: publishing, checkout and activation require end-to-end acceptance.

B — Direct distribution

Assemble an application from models, code and permitted modules, then distribute it under your brand. Dedicated Client Runtime rights are needed for each app and legal end customer, chargeable from the first concurrent user. Activation follows validated operational procedures.

Adding a module to an app does not by itself multiply Runtime licences. Industrial Runtime redistribution and multi-app OEM embedding require separate contracts.

AVAILABILITY

Commercial rights are not proof of a delivered feature.

Downloads, Store publication, checkout and CLI activation need end-to-end validation before being promoted as self-service.

Your next step

Learning or building? Start with Developer. Planning a customer POC? Obtain prior written confirmation from LGC. For production deployment or OEM, discuss the appropriate rights.

Talk to sales