Lolly Beta
Launch App

Lolly compared, tool by tool

Lolly covers creative work from a single on-device conversion to a governed organisation's asset production. These pages compare the workflows each product supports, the way it is deployed and the limits that matter when choosing a solution.

_Last checked: 28 September 2026._

One project, two separately deployed parts

Lolly is the engine, apps and tools for creating, editing, converting and exporting. It runs on your device, works offline once the required assets are available, and needs no account for standalone use.

lolly.work is the project's organisation service, maintained in the lolly-work repository. It provides SSO, SCIM provisioning, roles and policies, shared catalogues and projects, approvals, work collaboration, usage reporting, audit records and server rendering. Both parts are MPL-2.0 open source. An organisation hosts lolly.work alongside Lolly and decides which services to enable.

The comparisons cover Lolly + lolly.work. Features that need the organisation service are identified explicitly. Standalone use keeps files on the device; choosing shared projects, work collaboration, server rendering or delivery sends the relevant data to the configured services. The public lolly.work site is a sandbox; see the deployment guide and current status for an organisation deployment.

Compare by workflow

For the capability-by-capability view, see How Lolly compares. Each comparison is dated; a claim that no longer matches either product needs correcting.