Compare Lolly's creative tools and lolly.work's organisation services with other ways to design, govern and produce assets.
For individual comparisons with Canva, Adobe, Figma, Penpot, brand portals, rendering APIs and online converters, see Lolly compared, tool by tool. Each page covers the combined solution and identifies which part provides each capability.
Lolly and lolly.work
Lolly provides the engine, apps and tools for creating, editing, converting and exporting on your device. lolly.work is the same project's separately deployed organisation service: SSO, SCIM provisioning, roles and input policies, shared catalogues and projects, approvals, work collaboration, usage reporting, audit records and server rendering. Both are MPL-2.0 open source; lolly.work is maintained in its own repository.
An individual can use Lolly without an account or server. An organisation can operate both parts on its own infrastructure. Local rendering remains on the device; shared projects, work collabs, server jobs and delivery use the configured services. The public lolly.work site is an evaluation sandbox. Its operator documentation covers durable deployments and current limits.
Pilot status: Lolly is a closed-pilot prototype, not a finished product, and its security is currently undergoing SUSE's strict infrastructure hardening, preparing for enterprise scale. The Adoption & Governance page covers the current state.
Today's tools
Each ring below scores how completely a product class delivers a capability, with every class scored on its best representative. The Lolly column covers both Lolly and lolly.work; each row distinguishes local and organisation features. Open a row name for the reasoning behind its score. Columns are sorted by the Overall completeness row at the top - the mean of the scored rows, with the spend row excluded.
Lolly includes lolly.work, the same project's separately deployed organisation service. Local creation needs no account; shared work and server rendering use the configured instance. Competitor scores: August 2026. Lolly coverage: 28 September 2026.
| Capability | Lolly+ lolly.work | Penpotopen design | CanvaAffinity Cavalry |
Adobedesktop pro | Brand DAMFrontify Bynder |
Cloudinarymedia pipeline | Figmaonline pro | Render APIsBannerbear Placid Creatomate |
|---|---|---|---|---|---|---|---|---|
| Overall completenessunweighted mean - weight rows for your own context · columns are sorted by this row | 84 | 70 | 57 | 48 | 41 | 41 | 41 | 34 |
Production maturity & track recordCanva, Adobe, Figma, Bynder/Frontify: a decade-plus at massive scale. Render APIs: years in production pipelines. Penpot: shipping, large community, younger at enterprise scale. Lolly: closed pilot, security hardening underway, no public case studies. Cloudinary: 2012, enterprise media infrastructure at global scale. |
25 | 75 | 100 | 100 | 100 | 100 | 100 | 75 |
Mass generation from data (CSV / API)Lolly: batch grid and CLI, plus lolly.work's recoverable server jobs and batches with retries, cancellation and retained outputs. Canva: Bulk Create + Autofill API - real, but Enterprise-gated, async, text/image fields only; Affinity Publisher adds desktop data merge. Adobe: InDesign data merge and scripting. Figma: Buzz fills templates from CSV or XLSX, free in beta (Aug 2026) - cloud- and account-gated, 50. Penpot: open API/MCP, not purpose-built. Render APIs: this is their entire product - account- and cloud-gated, so 75 under the method rule. DAM: Studio-style batch create and resize. Cloudinary: URL-driven overlays and named transforms derive variants at scale - account-gated, 75. |
100 | 50 | 50 | 50 | 75 | 75 | 50 | 75 |
Offline & air-gap operationLolly: standalone creation works offline once its assets are available; lolly.work's organisation services need a reachable instance, which can run on an internal network. The Canva column is scored on its best family member: Affinity (free since Oct 2025) runs offline as a desktop suite once a verified account activates it - 75, the same deduction Adobe takes. Canva's own Offline (2026) still edits pre-synced designs only, per device, in a 14-day window. Adobe: desktop apps run offline; licensing phones home. Figma: cached-file viewing and limited editing. Penpot: self-host on your infra behind a firewall (server required). Cloud APIs and DAM: none. |
100 | 75 | 75 | 75 | 0 | 0 | 25 | 0 |
On-device rendering - data never leavesLolly: local rendering and conversion in-browser or CLI need no upload. Choosing lolly.work's shared storage, work collabs or server rendering sends the relevant data to the configured instance. Adobe: local desktop rendering, but cloud services and telemetry in the suite. Figma: canvas renders locally, files live in Figma's cloud. Penpot: 90 - rendering happens in the browser and the save target is a server that can be your own sovereign private cloud, even your own laptop, with private export throughout; only the server hop separates it from Lolly. Canva itself is server-side by design; the column's 75 is Affinity - local desktop rendering, account activation and telemetry, the same shape as Adobe. Render APIs, DAM: server-side by design. |
100 | 90 | 75 | 75 | 0 | 0 | 25 | 0 |
Hard brand constraints (structural)Lolly: templates fix layout rules and expose permitted inputs. lolly.work adds group access, input policies, shared catalogues, approvals and audit records. Copy and usage rights can still need review. Canva: element locks - permission-based, admin-set and static: no template logic such as conditional logo switching or responsive recomposition at fill time, and Canva AI does not yet respect Brand Controls - 50. Render APIs: templates are fixed (only declared fields vary) but no governance layer. DAM: locked templates with restrictions. Figma: Buzz templates hold locked guidelines at fill time; the design surface stays review-enforced - 50. Penpot: tokens and systems enforced by review, not runtime. Adobe: libraries, little enforcement. Cloudinary: presets and Enterprise-gated transformation templates fix operations, not brand layout - 50. |
100 | 50 | 50 | 25 | 75 | 50 | 50 | 75 |
C2PA provenance, signed at creationAdobe: the broadest shipped implementation (Photoshop, Lightroom, Premiere, Firefly) - signing happens locally in the desktop apps and in the cloud for the Content Authenticity web app, and nothing signs without an Adobe account and an Adobe-provisioned identity, so it is account-gated end to end: 75 under the method rule. Lolly: optional on-device signing without an account, plus lolly.work server signing with a configured organisation identity. A verifier must trust the signer's root to show a trusted identity. The stack remains pilot-stage, so 75. Penpot: 50 via the official Lolly Export plugin - the same on-device engine signing Lolly uses, opt-in, as in Lolly (and disclosed plainly: it is Lolly's own plugin). No evidence of C2PA writing in Canva, Figma, render APIs or DAM as of Aug 2026. Cloudinary: 50 - signs images on delivery (fl_c2pa, CAI member since 2020), attesting delivery by Cloudinary rather than creation by you. |
75 | 50 | 0 | 75 | 0 | 50 | 0 | 0 |
CLI, pipeline & AI-agent automationLolly: CLI, TUI, MCP server and URL mode, plus lolly.work's authenticated render API, recoverable batches and governed delivery. One engine across the local and server paths. Render APIs: API-first, webhooks, integrations - account- and cloud-gated, so 75 under the method rule. Penpot: open API, plugins, official MCP server. Canva: Connect API - Enterprise-gated, async, rate-limited. Adobe: UXP/ExtendScript plus Firefly APIs. Figma: strong REST/plugin API, no render pipeline. DAM: asset-management APIs. Cloudinary: API-first media pipeline - account-gated, 75. |
100 | 75 | 50 | 50 | 50 | 75 | 50 | 75 |
Live collaboration (real-time co-editing)Figma: the scale benchmark - 200 simultaneous editors, up to 500 people in a file - account and cloud required. Canva: mature real-time editing across the product, same precondition. Penpot: real-time multiplayer with live cursors; self-hosting lifts the vendor-account precondition, but a server is still required. Lolly: direct two-device private collabs without an account, plus authenticated work collabs through lolly.work with shared edits, cursors and saved team sessions. Partial reflects the current single-node work deployment and limited operating history. Private collabs work without internet on a shared network; work collabs need the organisation's instance. Adobe: Live Co-Editing in beta, cloud documents only. Render APIs: no editing surface. DAM: comments and approvals, not canvas co-editing. Cloudinary: DAM comments and workflows, no canvas co-editing. |
50 | 75 | 75 | 25 | 25 | 25 | 75 | 0 |
No design skill requiredCanva: the category benchmark for ease. DAM: fill a locked template. Lolly: fill in fields using an existing tool, or publish a tool from Design through Share with rules. lolly.work manages access and input policy for the team. Render APIs: swaps design skill for developer skill. Adobe, Figma, Penpot: professional tools. Cloudinary: the media library is easy; transformations are developer territory. |
100 | 25 | 100 | 25 | 100 | 50 | 25 | 50 |
Open source, self-hosted, no lock-inPenpot: MPL-licensed, 51k+ stars, self-host via Docker/K8s - fully verifiable today. Lolly and lolly.work: MPL-2.0 open source in separate repositories, both self-hostable. lolly.work provides the organisation services as part of the project. The current 75 reflects the young project and limited deployment history. Everything else is proprietary SaaS or proprietary desktop. |
75 | 100 | 0 | 0 | 0 | 0 | 0 | 0 |
Cost at production scaleLolly + lolly.work and Penpot: no per-seat software licence charge for the open-source self-hosted path; hardware, storage and operations remain costs. Render APIs: metered - roughly $0.005–0.049 per image, credits often expiring monthly. Canva/Figma: per-seat; Canva's automation needs Enterprise, though Affinity itself is free since Oct 2025. Adobe: premium per-seat suite. DAM: sales-led enterprise quotes, MAU or seat models. Cloudinary: credit-metered across transforms, storage and bandwidth - 25. |
100 | 100 | 50 | 25 | 25 | 25 | 50 | 25 |
Annual medium enterprise spendIndicative list-price arithmetic for a medium enterprise - think 500-5000 people - August 2026: a guess range, not a quote; deals vary and the seat mix dominates. Ring = how much of the board's largest annual spend (US$500k) you keep; the number in the ring is each range's upper bound. Canva (US$75k-400k; Affinity free since Oct 2025 pulls the design-seat share down), Adobe (US$100k-500k) and Figma (US$30k-250k) assume the realistic creative-seat share of an organisation this size - tens to hundreds of seats, not a licence for every employee. Render APIs price by usage (US$5k-60k). DAM is quote-only, commonly US$50k-250k and up. Penpot is hand-set at 99: "your server" can be your own laptop - a small technical hurdle at well under 1% of an Adobe-scale spend. Lolly + lolly.work: US$0 in software licence charges for self-hosting. The figure excludes devices, organisation hosting, storage, support and administration; these need a separate budget. Standalone Lolly does not need the organisation service. Cloudinary: US$30k-150k, credit-based; enterprise contracts commonly sit near US$82k. |
$0 | $0 | $400k | $500k | $250k+ | $150k | $250k | $60k |
Capability comparison: competitor research and scores from August 2026; Lolly + lolly.work coverage reviewed 28 September 2026. Scoring: 0 absent, 25 workaround-grade, 50 real but gated or partial, 75 strong with caveats, 100 core competency.
signed by Lollypositioning-comparison.htmlHTMLAI generatedgenerated by GPT-6Check it yourselfGet the signed filepixels, not shapes39 KBScoring notes. Available features and production maturity are separate considerations. Lolly's maturity score reflects its pilot status and security hardening; the presence of SSO, approvals or server rendering does not establish a production track record. The feature descriptions below include lolly.work, while competitor scores retain their dated August review.
Canva is scored on its best family member per row, since it owns Affinity and Cavalry (both given away October 2025). Offline and on-device rendering score 75 through Affinity - a desktop suite that still needs a verified account and carries telemetry, the deduction Adobe also takes - while Canva's own offline mode edits only pre-synced designs, one device, limited window. Autofill scores 50: real but Enterprise-gated, async, text and image only. Figma's mass generation rose 25 to 50 when Buzz shipped spreadsheet fill (free beta, August 2026).
One rule governs the board: Full (100), on rows that touch your content or identity, needs a capability you can use with no account and no cloud precondition; rows describing the product itself (maturity, ease of use) are exempt. It costs Adobe on provenance: the broadest shipped C2PA (Photoshop, Lightroom, Premiere, Firefly) signs locally and in the cloud, but never without an Adobe account and identity, so 75. It caps the render APIs on mass generation and automation for the same reason.
Lolly's provenance 75 includes optional on-device signing and lolly.work's server signing with a configured organisation identity. Signature integrity and signer trust are separate: a verifier must trust the certificate's root to identify the signer as trusted. Penpot's 50 arrives through the Lolly Export plugin: the same engine signing, opt-in, disclosed as Lolly's own. Penpot scores 90 on on-device rendering: browser canvas with a save target on its server, which can be self-hosted. Cloudinary gets its own column for its DAM, transform API and CDN; the August review scored its delivery signing at 50.
Lolly's live collaboration includes direct two-device private collabs and authenticated work collabs through lolly.work, with shared edits, cursors and saved team sessions. The Partial score reflects the current single-node work deployment and limited operating history, rather than an absence of team editing. Price estimates are dated list-price arithmetic for scale, not procurement. Lolly and lolly.work carry no per-seat software licence charge; organisation hosting, storage and operations still have costs.
Lolly combines an on-device creative path with optional organisation services. Design, its direct-manipulation canvas, can use a design system's colours, type and assets. A finished layout can become a reusable tool whose declared inputs control the changes a recipient can make.
A team can author in Design or bring existing work across: Import a design opens supported Figma, Penpot, Illustrator, InDesign and PDF files as editable layouts. Specialist editing and prototyping needs can still determine which authoring tool a designer chooses.
signed by Lollyvector SVGCheck it yourselfGet the signed file65 paths~2.7k nodes63 groups91 KB
signed by Lollyvector SVGCheck it yourselfGet the signed file65 paths~2.7k nodes63 groups91 KB
Use it for
- Rapid generation of operationalised creative assets (event tiles, badges, signatures, alerts)
- Free-form arrangement on the open canvas (Design) when the pieces - colours, type, icons, images - must stay conformed to the brand globals
- Landing a finished Figma, Penpot, Illustrator, InDesign or PDF design (the Design tool's Import a design) so it can be edited, governed and re-rendered deterministically in every Lolly format
- One-to-many "fill in three fields, get the finished asset" flows - including bulk runs from a spreadsheet/CSV in the
/probatch grid (paste or import rows, one finished asset per row, download as a zip) - Always-on, recurring branded outputs
- Things where central control of brand expression matters more than expressive flexibility
Deck Studio is a good measure of the ceiling here: a whole slide deck declared as data, laid out live on the canvas and exported as a native editable PowerPoint.
signed by Lollyvector SVGCheck it yourselfGet the signed file251 paths~17k nodes292 groups1 image290 KB
signed by Lollyvector SVGCheck it yourselfGet the signed file251 paths~17k nodes292 groups1 image290 KB
Choosing an authoring workflow
Choose the editor by the operations your design needs: illustration, detailed retouching, prototyping or video production. Lolly's canvas and tools can create original work as well as repeatable assets. Imported designs and shared tokens let a team combine Lolly with specialist applications, while lolly.work governs shared assets, review and delivery.
Innovate probabilistically, scale deterministically
Most "AI creative" pitches put the model on the wrong side of an old line. Scribes and illuminators already settled where it falls: you work loose on the sketch, where anything can be tried and nothing is committed, and then you go to the printing press, which is intimidating exactly because it commits. The sketches were where the art was. The press was how it travelled. Two instruments, two jobs, each inventive in its own way, and the printed work could be trusted because the press kept its promise on every pull.
Lolly is the press, not the sketch. Bring whatever you like to the ideation - a model, a designer, a napkin - but the moment an idea has to become many assets it goes through something that renders the same way every time, from inputs anyone can read back. That is what the comparison above is really about: not who has the better generator, but who makes the committed step reproducible.
Trust the creative process, scale with rigour.
The rules live in the tool and its templates
Lolly puts reusable brand rules in the tool: colours, fonts, bleed margins, spacing and permitted inputs. The template fixes the parts a recipient must not change. lolly.work adds group access and input policies around that template, with approval chains available for catalogue submissions and governed delivery.
Reviewing a tool once makes repeatable production easier: each output inherits its layout rules. Copy, uploaded imagery and usage rights can still need review, and lolly.work supplies shared catalogues and approval workflows for that process.
This is the change the deterministic engine actually delivers. For the creative team it's a guard-rail, not a replacement - you still throw the ball (the data, the copy, the image) and the code is the bumper lane that keeps every throw out of the gutter.
signed by Lollyvector SVGCheck it yourselfGet the signed file120 paths~4.5k nodes196 groups2 images133 KB
signed by Lollyvector SVGCheck it yourselfGet the signed file120 paths~4.5k nodes196 groups2 images133 KB
What this uniquely provides
- Wild design potential delivered safely in context. Tools can express adventurous design ideas inside hard coded guard-rails.
- Software-defined content automation that returns the final asset. Input → final file. No "now save it from your design tool and post-process it."
- Tools compose tools. One tool can embed another tool's render and return it as part of a single finished asset, with no tool-to-tool code coupling - a primitive no open-canvas or DAM-templating product on the board offers.
- Vendor neutrality. Full feature and cost control. Open-source engine. Tools and assets are git-tracked content, not locked in a SaaS database.
The first of those is the one people underestimate. A poster-grade city map, drawn as true vector road and water paths, from a dropdown and two colour fields that cannot be pointed outside the brand:
signed by Lollyvector SVGCheck it yourselfGet the signed file8 paths~25k nodes7 groups287 KB
signed by Lollyvector SVGCheck it yourselfGet the signed file8 paths~25k nodes7 groups287 KB
Content sovereignty
Lolly's creative pipeline can run on hardware you own. Design tokens, fonts, logos and tool definitions are files you can hold in version control. Standalone rendering stays on the device. With lolly.work, shared projects, instance assets, policy and audit records live in the organisation's configured storage, and server rendering runs on its infrastructure. Both parts are open source and inspectable; existing third-party libraries remain optional integrations.
This matters to anyone whose work should outlive a subscription: the parent whose photo book lives on that laptop as much as the public body whose brand library sits under procurement rules. For organisations - public bodies, regulated industries, anyone whose brand is a strategic asset rather than a decoration - "where does our content live and who can turn it off" is a governance question, not a preference. Sovereignty here is a property of the architecture rather than a hosting feature added for compliance, and the Privacy Policy and Verify It Yourself pages exist so you can check that claim rather than take it.
Underneath it all is one promise, stated as a commitment rather than a feature: if it renders on your device, it is free forever. The engine, the shells, the tools and the formats are open source. lolly.work is open source as well: the same project's separately deployed service for coordinating people, policy, shared work and server production. An organisation pays for the infrastructure and operation it chooses, with no per-seat or per-render software licence charge for self-hosting.