Lolly 做到了当今创意工具做不到的哪些事,以及它有意留给这些工具去做的事。
逐一工具的对比版本,分别针对 Canva、Adobe、Figma、渲染 API 和在线转换工具各写了一页,见Lolly 逐一工具对比。每一页都说明了对方工具更擅长做什么,以及 Lolly 用什么来替代。
状态: Lolly 已经发布:1.0 版本于 2026 年 8 月 30 日以开源方式发布。它的安全性尚未经过独立审计,采用情况的证据也只有几个月的历史。采纳与治理页面介绍了当前状态。
当今的工具
下面每一个圆环给出的评分,衡量的是以今天实际发布的形态、而非营销宣传所说的形态,某一类产品在多大程度上完整交付了某项能力 - 每个类别都以其最佳代表产品作为评分对象。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 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 月。评分标准:0 分为不具备,25 分为需变通实现,50 分为具备但受限或部分实现,75 分为较强但有保留,100 分为核心能力。
signed by Lollypositioning-comparison.htmlHTMLpixels, not shapes40 KBAI generatedgenerated by GPT-6自己验证获取已签名文件评分说明。 功能是否具备与生产成熟度是两回事。Lolly 的成熟度评分反映的是 2026 年 8 月的首次公开发布,以及尚无独立安全审计;具备 SSO、审批或服务器端渲染,并不能证明它有生产环境中的实际记录。下面的功能描述包含 lolly.work,而竞品的评分仍保留其带日期的 8 月调研结果。
Canva 在每一行都以其旗下最强的产品成员来评分,因为它拥有 Affinity 和 Cavalry(两者均于 2025 年 10 月免费开放)。离线与本地设备渲染通过 Affinity 得到 75 分 - 这是一款仍需已验证账户、并带有遥测的桌面套件,而 Adobe 也因同样的原因被扣分 - 相比之下 Canva 自身的离线模式只能编辑已预先同步过的设计、限单一设备、可用时间窗口也有限。自动填充得 50 分:功能属实,但仅限企业版、异步执行,且仅支持文本和图像。Figma 的批量生成分数在 Buzz 上线电子表格填充功能后(免费公测,2026 年 8 月)从 25 分提升到了 50 分。
整张表遵循一条统一规则:在涉及你的内容或身份的各行中,满分(100)要求某项能力无需账户、也无需依赖云端前提条件即可使用;而描述产品本身的行(成熟度、易用性)不受此规则约束。这条规则在“来源可溯性”上让 Adobe 失分:目前发布范围最广的 C2PA 支持(Photoshop、Lightroom、Premiere、Firefly)可在本地和云端签名,但始终离不开 Adobe 账户和身份,因此只得 75 分。同样的原因也限制了渲染 API 在批量生成和自动化上的得分。
Lolly 在来源可溯性上的 75 分反映的是本地离线签名:架构上更强,但尚未经过审计,而且在获得身份或某个组织自有 CA 的背书之前,设备密钥在标准验证工具中会显示为未验证。Penpot 的 50 分来自官方的 Lolly Export 插件:同一套引擎签名机制,可选启用,并明确标注为 Lolly 自身提供。Penpot 还拿到了本表中唯一超出常规量表的圆环,即本地设备渲染的 90 分 - 浏览器画布、保存到你自己主权掌控的云(哪怕只是一台笔记本电脑)、私密导出;与 Lolly 之间只差服务器这一环。Cloudinary 单独占一列:它是一套媒体管线(DAM、转换 API、CDN),也是唯一在云端一侧发布了 C2PA 支持的产品(50 分,因为 fl_c2pa 是在交付时签名,证明的是“由 Cloudinary 交付”，而非“由你制作”)。
实时协作的情况正好相反:Figma 设定了规模基准(200 名编辑者同时在线),而 Lolly 点对点、air-gapped 的协作模式只得到“部分”评分。价格是一个估算值,且已明确标注为估算:基于常见座席组合的目录价粗算,故意留出较宽的区间,目的是体现规模量级而非用于采购报价。渲染 API 在约束能力上得 75 分:模板是锁定的,缺少品牌治理层。
差距在于:目前没有任何一款正在发行的产品是同时做到“约束优先”且“离线、无需账户、渲染路径中不经过服务器”的,也没有任何一家复制了这条账户条款。Lolly 如今也拥有了自己的开放画布 - Design,一个直接操作的自由画布 - 但其上的颜色、字体和素材都遵循品牌全局设定,所以即便是自由排布也依然保持约束优先。
Lolly 目前仍然不是一个无约束的设计套件;设计师仍会继续使用 Illustrator 和 Figma 来完成定制化的工作 - 而当这些工作需要变成一份受治理、可复现的资产时,Design 工具的导入设计功能可以把已完成的 Figma、Penpot、Illustrator、InDesign 或 PDF 文件带入画布,变成可编辑、且符合品牌规范的图形框。
signed by Lollyvector SVG71 paths~2.7k nodes59 groups75 KB自己验证获取已签名文件
signed by Lollyvector SVG64 paths~2.7k nodes59 groups74 KB自己验证获取已签名文件
适用场景
- 快速生成可运营的创意资产(活动图块、徽章、签名、提醒)
- 在开放画布(Design)上进行自由排布,同时颜色、字体、图标、图像等元素必须保持符合品牌全局设定
- 将已完成的 Figma、Penpot、Illustrator、InDesign 或 PDF 设计导入(Design 工具的 Import a design 功能),使其能够以任何 Lolly 格式被确定性地编辑、治理和重新渲染
- “填三个字段,拿到成品资产”这类一对多的流程 - 包括在
/pro批处理表格中基于电子表格/CSV 的批量运行(粘贴或导入数据行,每行生成一份成品资产,以 zip 打包下载) - 持续运行、周期性生成的品牌化输出
- 品牌表达的集中管控比表达灵活性更重要的场景
Deck Studio 很能说明这里的能力上限:整套幻灯片以数据形式声明,在画布上实时排版,并导出为原生可编辑的 PowerPoint 文件。
signed by Lollyvector SVG135 paths~17k nodes252 groups1 image226 KB自己验证获取已签名文件
signed by Lollyvector SVG128 paths~17k nodes252 groups1 image225 KB自己验证获取已签名文件
不适用场景
- 定制化或旗舰级的重点内容(广告牌、大型视频)
- 真正需要设计师参与的独特campaign作品
- 需要彻底跳出品牌体系的创意构思 - Lolly 的开放画布依然会让颜色、字体和素材遵循品牌全局设定,这正是它的意义所在
概率式创新,确定性规模化
大多数“AI 创意”的推销话术都把模型放错了一条古老界线的位置。抄写员和插画师们早就确定了这条线该画在哪里:你在草图上放手去做,那里什么都能尝试,什么都还没定型;然后你走向印刷机,而印刷机之所以令人敬畏,恰恰是因为它一旦启动就是定型的。艺术性在草图里。而作品能够传播,靠的是印刷机。两种工具,两种职责,各自以自己的方式富于创造力,而印刷出来的成品之所以可信,是因为印刷机在每一次印刷中都信守了自己的承诺。
Lolly 是那台印刷机，不是那张草图。构思阶段你可以带来任何你喜欢的东西 - 一个模型、一位设计师、一张餐巾纸 - 但一旦某个想法必须变成许多资产，它就要经过某种每次都以相同方式渲染、且任何人都能反读出其输入内容的机制。这正是上面这份比较真正想说明的：不是谁的生成器更好，而是谁能让这个定型的步骤变得可复现。
信任创意过程,以严谨实现规模化。
规则存在于工具，而不是文件
面板上的其他每个工具都会产出一个文件，而文件只能事后查看，一次一份。Lolly 把品牌规则往上游移了一步。精确的十六进制色值、授权字体文件、出血边距、间距 - 这一切都硬编码进工具的 HTML 和 CSS 里，因此模板不可能产出不符合品牌规范的资产。是版式本身在做强制执行。
于是值得关注的是工具本身，而不是它产出的每一份文件。把工具做对，它此后产出的每一份资产都会因构造方式而符合品牌规范。你如何检查自己的工作、由谁来检查，依然由你决定;Lolly 只是让被检查的东西变小，产出做得更快。
这才是确定性引擎真正带来的改变。对创意团队来说，这是一道护栏，不是替代 - 你依然要扔球（数据、文案、图片），代码是保龄球道两侧的护栏，让每一次投掷都不会滚进沟里。
signed by Lollyvector SVG121 paths~4.6k nodes197 groups2 images113 KB自己验证获取已签名文件
这一点带来的独特价值
- 在受控范围内安全地释放大胆的设计潜力。 工具可以在硬编码的护栏之内表达大胆的设计想法。
- 软件定义的内容自动化，直接产出成品资产。 输入 → 成品文件。不需要“先从设计工具里导出，再做后期处理”。
- 工具可以嵌套调用工具。 一个工具可以嵌入另一个工具的渲染结果，把它作为单份成品资产的一部分返回，且工具间没有代码耦合 - 这是市面上任何开放画布类或 DAM 模板类产品都不提供的原语。
- 厂商中立。 功能和成本完全可控。开源引擎。工具和资产是受 git 管理的内容，而不是被锁在某个 SaaS 数据库里。
第一点是最容易被低估的一点。一张海报级别的城市地图，道路和水系都以真正的矢量路径绘制，仅靠一个下拉菜单和两个颜色字段生成，而且不可能被指向品牌之外的颜色：
signed by Lollyvector SVG8 paths~25k nodes7 groups287 KB自己验证获取已签名文件
signed by Lollyvector SVG8 paths~25k nodes7 groups287 KB自己验证获取已签名文件
内容主权
上一节说的这些加在一起，其实有个名字：主权。你的媒体流水线跑在你自己拥有的硬件上。你的品牌 - 令牌、字体、标志，以及强制执行这些规则的工具 - 存在于你手上的文件里，受你自己掌控的版本控制系统管理，而不是躺在某家厂商数据库里、靠一个“导出”按钮才能拿回来。渲染发生在你面前的这台设备上，因此一份资产的存在从不需要经过第三方，从输入到成品文件的整条路径都开源、可检查。就算所有 SaaS 设计厂商明天全部消失，一套 Lolly 部署也不会受到任何影响。
这对任何“作品理应比订阅期更长久”的人都很重要：无论是照片集就存在那台笔记本电脑上的家长，还是品牌资产库受采购规则约束的公共机构。对组织而言 - 公共机构、受监管行业，任何把品牌当作战略资产而非装饰品的组织 - “我们的内容存在哪里、谁能把它关掉”是一个治理问题，不是一种偏好。这里的主权是架构本身的属性，而不是为了合规而追加的托管功能，隐私政策 和 自行验证 这两个页面存在的意义，正是让你能核实这个说法，而不是照单全收。
这一切的底层是一个承诺，是作为一项承诺而非一项功能来陈述的：只要它在你的设备上渲染，就永远免费。 引擎、外壳、工具、格式 - 整条设备端创作路径都是开源的，并且会一直保持这样。这个承诺是有机制保障的：已发布的版本一经授权就无法收回，也不存在任何可能日后重新授权这份工作的贡献者协议。整条边界一句话就说清楚：一切在你设备上渲染的内容都免费、开源，永远如此；跨网络协调人与机器则是另一个独立控制平面的工作，lolly.work。