Lolly 是同一个开源项目的两个部分。Lolly 是在你的设备上制作、编辑、转换和导出的引擎、应用和工具,无需账号。Lolly Work 是在你自己的基础设施上运行的组织服务器,用于登录、共享项目、审批和服务器渲染。两者都采用 MPL-2.0。本页把这一对与人们设计、管理和制作文件的其他方式进行比较。
核心理念是内容主权:控制内容如何在自己选择的系统之间创建、治理、存储和流转。创意应用可以提供设计,DAM 可以继续作为记录的来源,Lolly 可以把获准的输入和已批准的素材变成新文件。在现有 DAM 中使用 Lolly 介绍了这种组合。
当今的工具
每个圆环为一类产品评分,衡量它对某项能力的完整交付程度,每一类都以其最佳代表来评分。Lolly 列涵盖 Lolly 和 Lolly Work 两者,每一行都说明哪一部分提供什么。点开行名可以看到其评分的理由。各列按顶部的 Overall completeness 行排序:即已评分各行的平均值,不含花费这一行。
这些评分采用的是 Lolly 偏好的标准:无需账号或云端即可掌控。它们是在这些标准下的比较,不是对产品完整度的中立排名,也不是企业采购评分。评估具体工作流时,请分别阅读能力、部署和证据方面的限制。
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: version 1.0 public since 30 August 2026 under MPL-2.0, and SUSE runs it as an internal deployment; no usage data is shared yet and there are no public case studies yet. 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. Version 1.0 is public and SUSE runs it internally, but no usage data is shared yet, 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 Lolly 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 |
能力对比:竞品调研和评分截至 2026 年 8 月;Lolly + Lolly Work 的覆盖情况于 2026 年 9 月 28 日审阅。评分:0 缺失,25 勉强可用,50 真实但受限或不完整,75 强但有保留,100 核心竞争力。
signed by Lollypositioning-comparison.htmlHTMLpixels, not shapes40 KBAI editedgenerated by GPT-6Check it yourself获取已签名文件评分说明
可用的功能与生产成熟度是两回事。Lolly 已经发布:1.0 版本于 2026 年 8 月 30 日以开源形式发布,其安全性尚未经过独立审计,其采用证据只有几个月(采用与治理有当前状态)。具备单点登录、审批或服务器渲染并不能证明生产环境的长期记录,所以成熟度评分反映了这一点。竞品评分保持其带日期的 8 月评审。
有一条规则管着整张表。对于涉及你的内容或身份的行,满分(100)需要一项无需账号、无需云端前提即可使用的能力;关于产品本身的行,例如成熟度和易用性,则不受此限。这条规则让 Adobe 在 Content Credentials 上失分:它是已出货的最广泛的实现(Photoshop、Lightroom、Premiere、Firefly),在本地和云端签名,但从不脱离 Adobe 账号和身份,所以是 75。出于同样的原因,它也让渲染 API 在批量生成和自动化上封顶。
Canva 的每一行都以其最佳的家族成员评分,因为它拥有 Affinity 和 Cavalry(两者都在 2025 年 10 月免费放出)。离线和设备端渲染通过 Affinity 得到 75,这是一套仍需要已验证账号并带有遥测的桌面套件,Adobe 也被扣了同样的分;Canva 自己的离线模式只能在一台设备上、在有限的时间窗口内编辑预先同步的设计。Autofill 得 50:它是真实的,但仅限 Enterprise 且是异步的,只填充文字和图片。Figma 的批量生成从 25 升到 50,因为 Buzz 推出了电子表格填充(2026 年 8 月的免费测试版)。
Lolly 的 Content Credentials 得分 75,涵盖设备端签名和 Lolly Work 以已配置的组织身份进行的服务器签名;验证者仍必须信任签名者(Content Credentials 身份)。Penpot 的 50 来自 Lolly 自己的 Penpot 导出插件:同样的引擎签名,选择加入并像 Lolly 的一样披露。Penpot 在设备端渲染上得 90:浏览器画布,保存目标是它的服务器,而这个服务器可以自托管。Cloudinary 因其素材库、转换 API 和 CDN 而有自己的一列;8 月评审给它的交付签名打了 50 分。
Lolly 的实时协作包括两台设备之间直接的私密协作,以及通过 Lolly Work 进行的经过认证的工作协作,带有共享编辑、光标和保存的团队会话。Partial 评分反映的是目前单节点的 Lolly Work 部署和较短的运营历史,而不是缺少团队编辑。价格估算是带日期的标价算术,用于了解量级,不是采购依据。
什么时候选择 Lolly
在以下情况选择 Lolly
- 反复需要同一类文件:活动方块、证件、证书、提醒、社交卡片
- 许多文件来自一个模板和一张值的表格,使用 Lolly Batch 或 CLI
- 颜色、字体和素材必须留在设计系统之内,即使在开放的画布上
- 一份完成的 Figma、Penpot、Illustrator、InDesign 或 PDF 设计应该变得可编辑、可重复(导入设计)
- 文件必须在你自己的设备或服务器上制作
在以下情况选择别的
- 工作是精细的照片修饰或插画
- 你在设计和原型制作应用界面
- 你第一天就需要一个庞大的素材库和模板库
- 你需要一项在大规模上有长期记录的托管服务
导入的设计和共享的设计令牌让团队可以把 Lolly 与专业应用结合使用,而 Lolly Work 管控共享素材、审阅和交付。
对于有精心管理的 DAM 的团队,先保持该素材库及其管理员不变。SUSE 的 Brandfolder 经验记录了集成如何支持采用和审批的变更管理。DAM 厂商和实施合作伙伴可以通过合作伙伴工作流评估同样的安排。
一整套幻灯片演示稿显示了上限:在 Lolly Markdown Slides 中,演示稿被声明为数据,实时排版,并导出为原生可编辑的 PowerPoint 文件。
signed by Lollyvector SVG135 paths~17k nodes252 groups1 image226 KBCheck it yourself获取已签名文件
signed by Lollyvector SVG128 paths~17k nodes252 groups1 image225 KBCheck it yourself获取已签名文件
规则存在于工具中
Lolly 把可复用的品牌规则放进工具:颜色、字体、出血边距、间距和允许的输入项。模板固定了接收者不得更改的部分。Lolly Work 在该模板周围增加组访问和输入政策,并为目录提交和交付配备审批链。
检查一次工具会让重复的生产更容易,因为每个输出都继承其版面规则。文案、上传的图像和使用权仍然可能需要检查,Lolly Work 为此提供共享目录和审批步骤。对创意团队来说,工具是护栏:你仍然带来数据、文案和图像,工具让每个结果都符合品牌。
signed by Lollyvector SVG121 paths~4.6k nodes197 groups2 images113 KBCheck it yourself获取已签名文件
还有三点让这种做法与众不同:
- 最终文件,来自输入。 输入进去,成品文件出来,不需要“现在从你的设计工具保存再修整一下”。
- 工具组合工具。 一个工具可以把另一个工具的渲染结果嵌入单个成品文件,它们之间没有代码耦合。
- 彻底开放。 引擎是开源的,工具、素材和设计令牌是你可以放在版本控制中或在 Lolly Work 中管理的文件,而不是别人数据库中的行。
大胆的设计经得起护栏。这幅海报级的城市地图是真正的矢量道路和水域路径,来自一个下拉菜单和两个颜色字段,它们无法被指向设计系统之外:
signed by Lollyvector SVG8 paths~25k nodes7 groups287 KBCheck it yourself获取已签名文件
signed by Lollyvector SVG8 paths~25k nodes7 groups287 KBCheck it yourself获取已签名文件
概率式创新,确定性规模化
大多数“AI 创意”的推销都把模型放在了一条古老界线的错误一侧。抄写员和彩饰师早就划定了这条线在哪里。你在草图阶段随意发挥,在那里什么都可以尝试,什么都不必定下来。然后你走向印刷机,印刷机负责定稿。艺术在草图里,印刷机是它传播的方式,印出来的作品之所以可信,是因为印刷机每一次印制都兑现了它的承诺。
Lolly 就是印刷机。你可以带着任何东西来构思,模型、设计师或一张草图,但一旦一个想法要变成许多文件,它就要经过某个每次都以同样方式渲染的东西,其输入任何人都可以读回。上面的对比,说到底是在比较谁让这个定稿的步骤可重复。
信任创意过程,以严谨实现规模化。
永远免费
只要它在你的设备上渲染,就永远免费。 引擎、外壳、工具和格式都是开源的,已发布的版本无法被收回。Lolly Work 也是开源的。组织为自己选择的基础设施和运营付费,自托管没有按席位或按渲染次数收取的软件许可费用。问答讲述了这个承诺背后的故事。
你的内容存放在哪里
Lolly 的创意工作可以在你自己拥有的硬件上运行,它的设计令牌、字体、徽标和工具都是你可以保存的文件。使用 Lolly Work 时,共享项目、素材、政策和审计记录存放在你的组织配置的存储中。信任解释了这为什么重要,隐私政策和自行验证让你去检验这一说法,而不是只听我们说。
逐个工具对比
逐个工具对比 Lolly把 Lolly 与 Canva、Adobe、Figma、Penpot、品牌门户、渲染 API 和在线转换器逐个对比,每个一页,并列出了什么在哪里运行。