Penpot vs Spline

Agent ops

1. ai-native userAn agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them

   weight 2 · round to Spline
   Penpot~partialprobed6/10

   Penpot has a documented MCP server explicitly for connecting AI agents/LLMs to design files, plus a plugin API and integrations API with access to objects/properties, suggesting agents can both read and modify designs programmatically. However, MCP docs emphasize agents 'reading and interacting with' design files for high-fidelity artifacts, and no independent/hands-on evidence confirms write operations via MCP or API actually work reliably, and openapi/spec probes 404'd. Missing for 10: concrete documented write/create examples via MCP or API, independent verification of agent-driven design edits, and a working OpenAPI spec.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Connect Penpot MCP server to your trusted AI agent. Customize your models and design infrastructure however works best for your team.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline✓fullprobed8/10

   Spline ships a dedicated MCP Server (bundled in desktop app) that lets Claude, Cursor, Codex, VS Code, Antigravity and ChatGPT drive the live editor to create/modify designs, plus a write-capable Code API for programmatic scene manipulation and webhooks/Real-time API for external event-driven updates. This goes beyond read-only access into genuine programmatic creation/modification. Missing for 10: independent hands-on validation of the MCP server's write actions and no public OpenAPI spec was found (openapi probe 404s), so full API surface is only documented, not independently verified.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “the desktop app gives you a few things the browser can't: **tabs** for working across several files, **system fonts**, and **MCP** support”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “Spline works fully in the browser, but the desktop app gives you a few things the browser can't: **tabs** for working across several files, …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

2. ai-native userAn agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface

   weight 2 · round to Penpot
   Penpot~partialprobed5/10

   Penpot documents an MCP server and plugin/integrations API that give agents structured access to design objects and mentions 'external rendering' as a use case (penpot-docs-3, penpot-docs-32), and design data can be exported to open formats like SVG/CSS/HTML (penpot-docs-21). However, there is no concrete documented endpoint or workflow for producing screenshots/images/production export files programmatically, no OpenAPI spec was found (404s in penpot-probe-2), and one community report describes limited export options (single-layer only) in hands-on use (penpot-comm-5). missing for 10: an explicit documented render/export API or endpoint (PNG/PDF/JPG) usable by an agent, a working OpenAPI/schema reference, and independent confirmation that MCP/plugin API can actually produce exported artifacts.

   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [community] “Maybe I'm using it wrong... when I tried Penpot about a year ago, I had no way to export the diagram as one file like PDF or JPG. I could on…”

   proof ↗⚑ flag

   Spline~partialprobed4/10

   Spline documents multiple export/programmatic surfaces (export-as-code for Vanilla JS/Three.js/React/Next.js/r3f, self-hosted ZIP export, Code API, Real-time API, webhooks) and an MCP server that lets agents like Claude/Cursor drive the editor, but none of the docs explicitly describe an agent invoking a screenshot/image render or export action through these interfaces — the MCP surface is framed as scene building/editing, not export/rendering. Missing for 10: explicit MCP or API tool for triggering exports/screenshots/renders programmatically, and independent confirmation this works end-to-end for an agent.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

3. ai-native userMy coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design

   weight 3 · round drawn
   Penpot~partialprobed6/10

   Penpot documents an official MCP server that lets any AI agent connect to design files, described as exposing design as code so agents can 'read and interact with your design files' and access objects/properties for external rendering, plus separate docs on components, design tokens, and design-system alignment (penpot-docs-1,18,27,31,32,3,33,11). However, no evidence explicitly confirms screenshot export or an explicit frame/variable/component mapping schema via the MCP itself, and there is no independent/hands-on report validating the MCP server's real-world behavior (only first-party docs, plus unrelated community comments about general app performance). Missing for 10: independent verification of MCP server functioning as described, explicit mention of screenshot/visual context retrieval, and concrete component-mapping API examples.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files. This can help you maintain consistency across a gr…”
   • [claimed-docs] “Design Tokens - Make design decisions that align designers and developers' workflows.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline~partialprobed6/10

   Spline ships an official MCP server bundled with the desktop app that connects Claude, Cursor, Codex, Antigravity and other MCP clients directly to the open editor, and separately offers a Code API, Real-time API and code export (React/Next.js/Three.js/react-three-fiber) that could let an agent read variables and scene structure to implement designs. However the MCP server's documented purpose is to let AI clients drive/edit the Spline scene ('straight into your open editor tab'), not explicitly to pull frames, screenshots, or component mappings as design-context for an external implementation — that specific dev-mode-style extraction flow is not evidenced. Missing for 10: explicit support for screenshot export via MCP/API, frame-level context retrieval, and documented component-mapping extraction for code implementation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Spline
   Penpot✓fullprobed8/10

   Penpot publishes an actual llms.txt at penpot.app/llms.txt with structured content (design tokens, plugin marketplace stats, Figma comparison) as cited in penpot-docs-16 and penpot-docs-24, plus extensive agent-oriented docs for its MCP server (penpot-docs-1, 18, 19, 27, 31, 32, 39) explicitly aimed at AI agents. missing for 10: an independent probe directly confirming penpot.app/llms.txt resolves (the probe only tested the unrelated help.penpot.app subdomain and got 404), and no third-party corroboration that agents successfully consume this file.

   • [claimed-docs] “Penpot vs Figma: Open-source alternative with self-hosting, unlimited files, native design tokens.”
   • [claimed-docs] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”
   • [probe] “PROBE llms.txt: HTTP 404 at https://help.penpot.app/llms.txt”

   proof ↗⚑ flag

   Spline✓fullprobed9/10

   Spline has a verified llms.txt at docs.spline.design/llms.txt (HTTP 200 probe) plus .md-suffixed doc pages that render clean markdown for agent consumption, confirming genuine agent-oriented docs infrastructure. missing for 10: independent third-party confirmation that agents actually consume these docs successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.spline.design/llms.txt # Spline Documentation ## Docs - [Getting Started](https://docs.spline.des…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.spline.design/basics/what-is-spline.md # What is Spline? (/basics/what-is-spline) Spline is a web…”
   • [claimed-docs] “How Spline compares to traditional 3D tools like Blender, Maya and Cinema 4D.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

   Penpot ships self-host/Docker/Kubernetes deployment, access-token API auth, outbound webhooks, and a self-hostable MCP server, all of which could underpin automated/CI-driven workflows, but there is no explicit documentation of a headless mode, CLI, or CI pipeline usage. missing for 10: explicit headless/CI-mode documentation, CLI tooling, independent evidence of running Penpot in a CI pipeline.

   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Deploy with docker compose... Use Kubernetes in its different flavors: Deploy the official Helm Chart”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “you can set up an instance of Penpot in just 3 minutes!”

   proof ↗⚑ flag

   Spline—none0/10

   Spline is documented purely as a browser/desktop GUI editor with a multiplayer, real-time canvas; its MCP server explicitly requires the desktop app with 'your open editor tab' running interactively, and no CLI, headless render mode, or CI-triggerable build/export process is documented anywhere in the evidence pack. Webhooks and the Real-time API only affect published/runtime scenes, not the design-time editor pipeline, so there is no path to running Spline itself headlessly in automation.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Penpot
   Penpot~partialclaimed3/10

   Penpot's docs mention connecting to another product's MCP server ('Migrate your designs into Penpot by connecting Figma's and Penpot's MCPs') implying Penpot can act as an MCP client to import tool-provided data, but the vast majority of MCP evidence describes Penpot instead exposing its OWN MCP server for agents to connect to (the reverse relationship), not Penpot consuming arbitrary external MCP servers' tools. Missing for 10: documentation of a general-purpose MCP client/connector UI in Penpot, a list of supported external MCP servers beyond Figma, and any hands-on/community confirmation that this client-side integration works.

   • [claimed-docs] “Migrate your designs into Penpot by connecting Figma’s and Penpot’s MCPs.”
   • [claimed-docs] “Migrate your designs into Penpot by connecting Figma's and Penpot's MCPs.”
   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic”

   proof ↗⚑ flag

   Spline—none0/10

   All evidence describes Spline shipping an MCP *server* (docs-13, docs-25, docs-36, docs-53) that external MCP clients like Claude/Cursor/Codex connect to — the reverse of this story, which asks whether a user can plug external MCP servers into Spline so its own AI agent can use their tools. No evidence shows Spline acting as an MCP client or consuming third-party MCP tool servers.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [claimed-docs] “connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here — there's nothing to install or configure, the app…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Penpot✓fullprobed8/10

   Penpot documents an official MCP server (agnostic, self-hostable, connects to any AI agent/LLM) with dedicated marketing/docs pages and a probe confirming the page exists. Missing for 10: independent/hands-on third-party confirmation that the MCP server works reliably in practice, and technical setup/API reference details beyond marketing copy.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Connect Penpot MCP server to your trusted AI agent. Customize your models and design infrastructure however works best for your team.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline✓fullprobed8/10

   Spline documents an official MCP server bundled in the desktop app that connects Claude, Cursor, Codex, VS Code, Antigravity, and ChatGPT directly to the editor, requiring no separate install/config. This is a clear first-party MCP server offering with dedicated docs. Missing for 10: independent/hands-on community corroboration of the MCP server actually working, and no detail on the specific tools/capabilities exposed via the server.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to Penpot
   Penpot✓fullprobed8/10

   Penpot documents a public API with access tokens for authentication, outbound webhooks, an open plugin API, and a dedicated MCP server explicitly designed to let any AI agent/LLM read and manipulate design files programmatically. This directly matches the ai-native 'documented public API' story, with self-hosting options adding control. Missing for 10: no discoverable OpenAPI/swagger spec (probes returned 404s) and no independent/hands-on verification of the API's completeness beyond vendor docs.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline~partialprobed7/10

   Spline documents several external-facing interfaces an AI-native user could drive: the Real-time API and Webhooks for event-driven external integration, a Code API for web to control published scenes from external code/UI, and an MCP Server that lets AI coding agents (Claude, Cursor, Codex) manipulate the editor directly. These are genuine documented, public-facing APIs beyond just manual UI use. missing for 10: a formal REST/OpenAPI specification (probe explicitly found no openapi.json/swagger.json at any candidate path), and independent/hands-on corroboration that these APIs work reliably outside vendor docs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Penpot—none0/10

   Penpot offers access tokens as an alternative login method for API access (penpot-docs-6) and an MCP server for agent connectivity, but there is no evidence of scoped or least-privilege credential issuance (e.g., permission-limited tokens, role-based scopes, or granular API key restrictions) for agents. Missing for 10: scoped/permission-limited token creation, documentation of least-privilege API key options, agent-specific credential management.

   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”

   proof ↗⚑ flag

   Spline—none0/10

   Evidence shows Spline offers an MCP server for connecting AI coding tools to the editor, but there is no mention of scoped or least-privilege API credentials, API keys with permission scopes, or any access-control mechanism for issuing restricted agent credentials. Missing for 10: any documentation of credential/token scoping, permission levels, or least-privilege API key issuance for agents.

   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [probe] “official MCP server documented at https://docs.spline.design/basics/download-spline-for-desktop”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Penpot
   Penpot✓fullprobed7/10

   Penpot ships an official, self-hostable MCP server plus an open plugin API, REST API with access-token auth, and webhooks, explicitly marketed for AI agents to build against (penpot-docs-1,3,5,6,19,27,31,32,39). This gives AI-native users concrete official SDK/API surfaces to integrate with, though there's no independent hands-on validation of the MCP server and the OpenAPI spec could not be located (probe 404s), missing for 10: independent developer confirmation of MCP/plugin SDK reliability, discoverable machine-readable OpenAPI/llms.txt spec.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Our plugin system brings the flexibility that devs need to create and publish their own custom extensions.”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Connect Penpot MCP server to your trusted AI agent. Customize your models and design infrastructure however works best for your team.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline~partialprobed6/10

   Spline documents a Code API and multiple official code-export targets (Vanilla JS, Three.js, React, Next.js, react-three-fiber) plus a self-hosted runtime export, which functions as an SDK-like integration surface for developers (spline-docs-6, spline-docs-12, spline-docs-17, spline-docs-8). However, a live probe for a formal OpenAPI/SDK spec returned 404s, and there's no independent developer corroboration of SDK usage or versioned package docs beyond the docs site. Missing for 10: dedicated SDK/package documentation (e.g. npm SDK docs), OpenAPI/API reference, and third-party hands-on confirmation of building against these SDKs.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Penpot✓fullclaimed7/10

   Penpot's docs explicitly describe outbound webhooks that notify external apps of events like file creation/update or comments, directly matching the 'subscribe to events via webhooks' story. Evidence is vendor-documentation only with no independent/hands-on confirmation of webhook delivery or a full list of supported event types. Missing for 10: independent corroboration of webhook triggering/reliability, complete event-type catalogue, and details on webhook subscription management (payload schema, retries, security).

   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline docs explicitly document a Webhooks feature that allows listening for and responding to external events, triggering actions, updating variables, and reacting to data sent from external sources — directly matching the story. However, this is first-party documentation only with no independent/hands-on corroboration or detail on subscription mechanics (event types, payload schema, delivery guarantees). Missing for 10: independent verification of webhook reliability, detailed event-type/payload documentation, hands-on community testing.

   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Penpot~partialclaimed4/10

   Penpot provides building blocks for automation—an MCP server for AI agents, outbound webhooks, and a plugin API—that could underlie background automations, but all documented use cases (prompting an agent, plugin actions) are interactive/triggered rather than autonomous, unattended background processes. Missing for 10: explicit support for scheduled/triggered autonomous agent runs, evidence of agents operating without a live user prompt, and any independent confirmation that MCP/webhook flows work unattended in production.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “Penpot enables plenty of AI workflows, from generating editable design structures to connecting product logic, tokens, and implementation.”

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Spline offers webhooks and a Real-time API that let a published scene 'automatically trigger actions, update variables, and react to data sent from external sources' without a person driving it (spline-docs-9, spline-docs-10, spline-docs-26), which is a form of event-driven automation running unattended. However, this is scene-level reactivity to external events, not a general-purpose scheduled/autonomous agent workflow — the AI Agent and MCP integrations require an open editor tab and active AI-tool session (spline-docs-13, spline-docs-25) rather than running independently in the background. Missing for 10: evidence of scheduled/cron-like autonomous tasks, independent confirmation of webhook automation working in practice, and any agentic workflow that persists without an open editor session.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The MCP server is bundled in the desktop app, so connecting Claude, Cursor, VS Code, Antigravity or ChatGPT to your editor only works here —…”

   proof ↗⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Spline
   Penpot—none0/10

   Penpot's AI evidence is entirely about an MCP server that lets external AI agents/LLMs connect to Penpot's data (penpot-docs-1, penpot-docs-18, penpot-docs-27, penpot-docs-31, penpot-docs-39), not about a built-in AI assistant embedded in the product itself that users can delegate tasks to. No evidence describes an in-app AI chat/copilot feature within the Penpot UI.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “Connect Penpot MCP server to your trusted AI agent. Customize your models and design infrastructure however works best for your team.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline ships a built-in AI Agent that autonomously builds and edits 3D scenes ('describe what you want and it does the work through the editor itself — creating objects, setting up materials and lighting, animating, wiring interactivity') and a parallel Hana AI Agent for 2D screens, both directly matching the delegated-task story. Missing for 10: independent/hands-on verification of the agent's real-world reliability and scope beyond first-party docs.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Spline
   Penpot✓fullprobed7/10

   Penpot ships an official MCP server explicitly designed so any AI agent/LLM can 'prompt away' to read and manipulate design files expressed as code, directly enabling natural-language operation, backed by plugin API and access tokens for automation. Missing for 10: independent/hands-on evidence of the MCP server actually working end-to-end in practice (community comments only cover general UI/performance, not the AI/MCP workflow specifically).

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Connect Penpot MCP server to your trusted AI agent. Customize your models and design infrastructure however works best for your team.”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline✓fullclaimed8/10

   Spline's AI Agent lets users describe what they want in natural language and the editor builds objects, materials, lighting, animation, and interactivity accordingly (spline-docs-3, spline-docs-20, spline-docs-40), and Hana's AI Agent similarly designs UI screens from natural-language descriptions (spline-docs-21, spline-docs-39, spline-docs-54). AI texture generation also works by typing descriptions (spline-docs-4, spline-docs-28). This is reinforced by an MCP server enabling natural-language driven control from external AI clients like Claude/Cursor (spline-docs-13, spline-docs-36). Missing for 10: independent/hands-on user reports confirming natural-language command reliability and breadth of coverage beyond first-party docs.

   • [claimed-docs] “describe what you want and the 3D editor builds it: objects, materials, lighting, animation, interactivity.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Penpot—none0/10

   Evidence describes integrations-api, plugin system, and MCP server, but there is no interactive API reference with runnable examples; probes explicitly found no OpenAPI/swagger spec or llms.txt documentation endpoint (404s), and no mention of interactive docs/sandbox exists.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.penpot.app/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline documents several APIs (Code API, Real-time API, webhooks) but the evidence pack shows no interactive API reference with runnable examples — a probe for OpenAPI/swagger specs returned 404 on all candidate paths, and the docs are plain markdown descriptions rather than an interactive sandbox.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Penpot—none0/10

   While Penpot documents a general integrations API, access tokens, webhooks, and an MCP server, there is no evidence of a downloadable OpenAPI/Swagger spec; direct probes for openapi.json/swagger.json/llms.txt all returned 404s, indicating no machine-readable API spec is published.

   • [probe] “PROBE llms.txt: HTTP 404 at https://help.penpot.app/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”

   proof ↗⚑ flag

   Spline—none0/10

   A direct probe for OpenAPI/swagger specs at common paths returned 404 across all candidates, and no documentation references a downloadable machine-readable API spec; Spline offers a Real-time API and Code API but no OpenAPI equivalent is evidenced.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Penpot—none0/10

   Evidence documents an API, plugin system, and MCP server, but there is no mention of API versioning or a documented deprecation policy anywhere in the docs; probes for OpenAPI/llms.txt spec files return 404, and no changelog or versioning policy is cited. Missing for 10: any documented API version scheme, deprecation notices, or changelog governing breaking changes.

   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://help.penpot.app/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”

   proof ↗⚑ flag

   Spline—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the OpenAPI probe returned 404s across all candidate paths, and no docs mention version numbers, changelogs, or deprecation timelines for the Real-time API, Code API, or MCP server.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

Ai

1. designerBuilt-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor

   weight 1 · round to Spline
   Penpot—none0/10

   Penpot's AI evidence is entirely about an MCP server for connecting external AI agents/LLMs to structured design data, plus a generic plugin marketplace mention of 'AI tools' — there is no evidence of built-in editor features like image generation, background removal, content-aware fill, or copy suggestions happening inside Penpot itself. The axis is fair for a design tool (competitors ship such features), but nothing in the pack shows Penpot delivering it natively.

   • [claimed-docs] “Connect Penpot with any AI agent, any LLM. Penpot MCP server is agnostic and enables high-quality multi-directional AI workflows through our…”
   • [claimed-docs] “Penpot connects any AI agent with structured design. Automate tedious tasks, streamline your processes between apps, and build truly powerfu…”
   • [claimed-docs] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Penpot enables plenty of AI workflows, from generating editable design structures to connecting product logic, tokens, and implementation.”

   proof ↗⚑ flag

   Spline~partialclaimed3/10

   Spline documents built-in AI features—AI-generated textures via text prompts and an AI Agent/Hana that builds/edits 3D scenes and screens—which is a form of in-editor generative asset creation, but there's no evidence of background removal, content-aware fill, or AI copy/text suggestions inside the editor. missing for 10: background removal, content-aware fill, copy/text suggestions, general image asset generation beyond textures.

   • [claimed-docs] “Use Artificial Intelligence to generate textures like grass, concrete, wood, ceramic, and patterns just by typing!”
   • [claimed-docs] “Use Artificial Intelligence to generate textures like **grass**, **concrete**, **wood**, **ceramic**, and **patterns** just by typing!”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ flag

2. designerGenerate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces

   weight 2 · round to Spline
   Penpot~partialprobed5/10

   Penpot's docs describe an official MCP server that lets external AI agents/LLMs read and interact with Penpot files to 'generate editable design structures' and 'create high-fidelity artifacts' from prompts (penpot-docs-31, penpot-docs-32, penpot-docs-40), which supports the story's intent of prompt-driven design generation. However, this is achieved only via connecting a third-party AI agent through MCP rather than a native in-app 'type a prompt, get a mockup' feature, and there is no independent/hands-on evidence confirming actual generated layouts or mockups working in practice. Missing for 10: first-party demo/screenshots of actual generated designs, independent hands-on reports validating the MCP-to-mockup pipeline, and a native in-app generation UI not dependent on external agent setup.

   • [claimed-docs] “Choose your agent, connect to Penpot MCP and prompt away!”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Penpot enables plenty of AI workflows, from generating editable design structures to connecting product logic, tokens, and implementation.”
   • [claimed-docs] “Connect it to any AI agent or LLM you trust. Customize your models and design infrastructure however works best for your team.”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline documents two AI Agents that generate designs from natural-language prompts: the 3D AI Agent creates objects, materials, lighting, animation and interactivity from a description, and Hana's AI Agent designs full 2D screens (layout, type, colour, effects, states) from a text description, which can then be edited by hand. This directly matches the story of generating first drafts/mockups from a prompt. Missing for 10: independent/hands-on verification of the AI Agent's actual output quality, and no third-party reviews or demos confirming real-world reliability of these AI generation features.

   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “The **AI Agent** builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating object…”
   • [claimed-docs] “Hana's AI Agent designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interactions.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Penpot
   Penpot!disputedcontradicted5/10

   Penpot's API/plugin/MCP layer gives extensive access to objects and properties and lets agents 'automate tedious tasks' across files (penpot-docs-2, penpot-docs-3, penpot-docs-32), which implies scriptable bulk edits, but no documentation specifically demonstrates a bulk-operation workflow (e.g., batch renaming/restyling hundreds of layers). Independent hands-on reports directly contradict smooth handling of many items: performance 'starts dropping rapidly once you approach around 1000 layers' versus design systems that run 10-40k layers (penpot-comm-19), and users report crashes/lag with just a few pages of content (penpot-comm-10, penpot-comm-16). Missing for 10: a documented bulk-edit API/plugin example, benchmarks showing many-item operations succeed at scale, and resolution of the reported performance degradation.

   • [claimed-docs] “Penpot connects any AI agent with structured design. Automate tedious tasks, streamline your processes between apps, and build truly powerfu…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [community] “Currently Penpot's performance starts dropping rapidly once you approach around 1000 layers. Most robust design systems I see run around 10-…”
   • [community] “Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too. I run it on Dedicated server with 64GB …”
   • [community] “I want to like penpot, but on even my beefiest computers it causes the whole system to slow to a crawl when opening anything complex.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs describe single-scene editing, MCP/Code API/webhook integrations, and AI generation features, but nothing indicates batch or bulk processing across many objects, scenes, or files at once (e.g., no scripting loop API, no bulk export/import, no multi-file automation mentioned).

   ⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Spline
   Penpot~partialclaimed3/10

   Penpot's outbound webhooks fire on events (file created/updated, comment added) which is a basic event-trigger mechanism, and the MCP/plugin API lets external agents react to design changes, but there is no evidence of a rules engine or conditional logic layer where users define custom trigger conditions and automated actions within Penpot itself. missing for 10: rule-definition UI/config (conditions, filters, action chains), documented automation recipes, evidence of in-app if/then automation beyond simple webhook event notification.

   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Our plugin system brings the flexibility that devs need to create and publish their own custom extensions.”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline's states/events/actions system, webhooks, and Real-time API let users define rules that trigger actions automatically on events (e.g., 'automatically trigger actions, update variables, and react to data sent from external sources'), which is core automation-depth functionality. missing for 10: independent/hands-on verification of event-rule automation in practice, and more detail on the breadth/complexity of conditional logic supported beyond docs claims.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”

   proof ↗⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Spline
   Penpot—none0/10

   Penpot's evidence covers MCP/AI agent integration, webhooks, and plugins for automation, but there is no evidence of any mechanism to version, review, or roll back these automations themselves (e.g., automation history, audit trail, or undo for agent-driven actions). Component 'restore main' (docs-23) is a design-object rollback, not an automation/workflow rollback feature.

   ⚑ flag

   Spline~partialclaimed5/10

   Spline's Version History lets users preview, recover, and manually save previous file states, which would cover the interactivity/automation logic (events, actions, webhooks) embedded in a scene, but this is a whole-file history feature, not a dedicated review/diff mechanism for automations specifically, and no evidence of granular change review or approval workflows exists. missing for 10: automation-specific diffing/review UI, branching or approval workflow, independent confirmation of rollback reliability for complex automations.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

Collaboration

1. product managerComment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email

   weight 2 · round to Spline
   Penpot~partialclaimed2/10

   The only evidence touching commenting is a passing mention that webhooks fire when 'a comment has been added,' which confirms Penpot has some in-file commenting feature but gives no detail on @mentions or resolving threads. missing for 10: documentation or hands-on evidence of @mention functionality, thread resolution UI, and any community confirmation that review workflows actually replace email in practice.

   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”
   • [claimed-docs] “Outbound webhooks are event calls from Penpot to other applications. They notify that some event occurred, e.g. a file has been created or u…”

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Docs confirm real-time multiplayer editing and that users can 'give feedback in place, the way they would in a 2D design tool,' implying some in-file commenting, but there is no mention of @mentioning teammates or resolving comment threads. missing for 10: explicit mention/tagging of teammates, ability to resolve/close comment threads, dedicated commenting UI documentation.

   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”

   proof ↗⚑ flag

2. designerMy whole team can edit the same file simultaneously with live cursors and instant sync

   weight 3 · round to Spline
   Penpot!disputedcontradicted4/10

   Vendor marketing implies real-time team collaboration ("Collaborate freely with unlimited teams") but the evidence pack contains no explicit documentation of live cursors or instant sync mechanics, and multiple hands-on reports describe multiplayer editing as crash-prone or unstable when several users work simultaneously on a file. Missing for 10: first-party docs describing live cursor presence/conflict resolution, latency/sync architecture details, and independent confirmation that simultaneous multi-user editing performs reliably at scale.

   • [claimed-docs] “Unlimited Teams - Collaborate freely with unlimited teams.”
   • [claimed-docs] “No file limits. Create as many as you need within your storage capacity. ... Unlimited Teams. Collaborate freely with unlimited teams.”
   • [community] “Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too. I run it on Dedicated server with 64GB …”
   • [community] “I tried to self host penpot a few months ago but the app would crash after a few minutes and not properly show the canvases. So a no for me.”
   • [community] “I really wanted to like penpot, but when I tried a few months ago, simply navigating between pages (even on the example documents) was causi…”

   proof ↗⚑ flag

   Spline✓fullclaimed8/10

   Multiple first-party docs consistently describe Spline as "multiplayer from the ground up," cloud-hosted files enabling several people to edit the same file simultaneously with in-place feedback, similar to 2D design tools — directly matching the story. Missing for 10: explicit mention of live cursors specifically, and no independent/hands-on corroboration of real-time sync quality at scale.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “It's multiplayer. Several people can edit the same file at the same time and give feedback in place, the way they would in a 2D design tool.”
   • [claimed-docs] “Spline is two editors that share the same interactivity model, the same real-time collaboration, and the same publishing pipeline.”

   proof ↗⚑ flag

Design systems

1. designerManage design tokens or variables — colors, spacing, typography — with modes or themes applied across designs

   weight 2 · round to Penpot
   Penpot~partialclaimed4/10

   Penpot explicitly advertises 'Design Tokens' and being a 'native design tokens' tool (penpot-docs-33, penpot-docs-13, penpot-docs-16), which directly supports token management for design-system alignment, but the evidence is only marketing tagline text with no detail on how modes/themes, multiple token sets, or per-property (color/spacing/typography) switching actually work. Components with linked instances (penpot-docs-11, penpot-docs-22) support consistency but aren't tokens/modes specifically, and no community/hands-on evidence corroborates the tokens feature's real-world robustness. Missing for 10: detailed documentation of token modes/themes switching, per-property (color/spacing/typography) token examples, and independent/hands-on confirmation that the tokens feature works as described.

   • [claimed-docs] “Design Tokens - Make design decisions that align designers and developers' workflows.”
   • [claimed-docs] “Make design decisions that align designers and developers' workflows.”
   • [claimed-docs] “Penpot vs Figma: Open-source alternative with self-hosting, unlimited files, native design tokens.”
   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files. This can help you maintain consistency across a gr…”
   • [claimed-docs] “All component copies used in a file are linked in a way that updates made to the Main component can reflect in their component copies.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs mention 'variables and data' only in the context of real-time API/webhooks event data, not design tokens for color, spacing or typography, and the only 'theme' feature found is the editor's own Dark/Light/System UI theme, not a token system applied across a designer's own scenes. No evidence shows reusable style tokens with modes/themes propagated across designs.

   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “Spline supports **Dark**, **Light**, and **System** themes so you can customize the interface to your preference.”

   proof ↗⚑ flag

2. designerBuild reusable components with variants and per-instance overrides that stay linked to their source

   weight 3 · round to Penpot
   Penpot~partialcommunity5/10

   Docs confirm reusable components with main/copy linkage that propagates updates (docs-11,22,23,35) and mention 'variants' as an extension (docs-41), but per-instance override mechanics are never detailed, and hands-on community feedback explicitly flags that variants/states handling is 'not on Figma's level yet' and components can feel 'difficult to handle' (penpot-comm-1, penpot-comm-9). missing for 10: documented per-instance override workflow, detailed variant creation/management docs, independent confirmation that variant/override linkage works robustly at scale.

   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files. This can help you maintain consistency across a gr…”
   • [claimed-docs] “All component copies used in a file are linked in a way that updates made to the Main component can reflect in their component copies.”
   • [claimed-docs] “If a main component has been deleted and you have access to a copy of it, you can use the copy to restore its main.”
   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files.”
   • [claimed-docs] “Extend components with variants—simpler to use, easier to control.”
   • [community] “Good: It is a good copy of figma's UI... Bad: In design systems particularly at variants and states of components, it is not on figma's leve…”
   • [community] “I've been toying a little with self hosted Penpot and it was really nice... Penpot was easy to use though it felt a little difficult to hand…”

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Spline docs confirm a Components system where reusable objects propagate changes from a main component to all instances (spline-docs-5), which covers the 'linked to source' part of the story. However, there is no evidence of a variants system (multiple named states of a component) or per-instance override capability that persists while staying linked, as seen in dedicated design tools. Missing for 10: documented variants/property sets per component, explicit per-instance override UI, and evidence of overrides surviving source updates.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”

   proof ↗⚑ flag

3. designerShared libraries publish components and styles across files and projects, with controlled updates when the source changes

   weight 2 · round to Penpot
   Penpot~partialcommunity5/10

   Docs confirm components as reusable linked elements where main-component edits propagate to copies (penpot-docs-22, penpot-docs-23, penpot-docs-35) and design-system features like tokens and variants (penpot-docs-33, penpot-docs-41), but there is no explicit documentation of publishing a library across separate files/projects or how updates propagate cross-project, and community feedback notes design-system/component sophistication lags Figma (penpot-comm-1, penpot-comm-9). missing for 10: explicit shared/library publishing workflow across files and projects, documentation of controlled update/accept-changes flow at library level, independent confirmation of cross-project sync reliability.

   • [claimed-docs] “All component copies used in a file are linked in a way that updates made to the Main component can reflect in their component copies.”
   • [claimed-docs] “If a main component has been deleted and you have access to a copy of it, you can use the copy to restore its main.”
   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files.”
   • [claimed-docs] “Design Tokens - Make design decisions that align designers and developers' workflows.”
   • [claimed-docs] “Extend components with variants—simpler to use, easier to control.”
   • [community] “Good: It is a good copy of figma's UI... Bad: In design systems particularly at variants and states of components, it is not on figma's leve…”
   • [community] “I've been toying a little with self hosted Penpot and it was really nice... Penpot was easy to use though it felt a little difficult to hand…”

   proof ↗⚑ flag

   Spline~partialclaimed4/10

   Spline documents component reuse where instances update when the main component changes (spline-docs-5), and pricing mentions a 'Team Library' feature (spline-docs-33), implying some shared-library capability across a team. However, there's no documentation detailing publishing components/styles across separate files or projects, or how updates propagate/are controlled at that scope. Missing for 10: cross-file/cross-project library publishing workflow, versioned/controlled update mechanism, and any independent confirmation of Team Library behavior.

   • [claimed-docs] “Components are objects that can be reused multiple times throughout your scene and whenever there are changes made to the main component all…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

Handoff

1. developerDesigns map to production code — component-to-code mappings or direct design-to-code output I can actually ship

   weight 2 · round to Spline
   Penpot~partialclaimed6/10

   Penpot documents code-based design representation and an 'Inspect' feature exporting CSS/HTML/SVG/JSON that matches the design (penpot-docs-21/36), plus an MCP server letting AI agents read structured design files to generate implementation artifacts (penpot-docs-32, penpot-docs-40). However, this is inspection/AI-assisted code generation rather than a documented direct component-to-framework code mapping (e.g., to React/Vue components), and no independent/hands-on evidence confirms developers actually shipping this code in production. missing for 10: first-party or community evidence of production-ready component-to-code bindings (framework-specific), and independent verification that generated/inspected code is usable as-is in shipped products.

   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON”
   • [claimed-docs] “In Penpot, design is expressed as code, so AI agents can easily read and interact with your design files creating high-fidelity artifacts.”
   • [claimed-docs] “Penpot enables plenty of AI workflows, from generating editable design structures to connecting product logic, tokens, and implementation.”
   • [github] “developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline documents direct design-to-code export in multiple production-ready formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), plus a Code API for wiring exported scenes into existing codebases, a self-hosted ZIP export bundling assets/runtime, and a native <spline-viewer> web component for drop-in embedding — all clearly aimed at shipping designed 3D/2D scenes into real production code. Missing for 10: independent/hands-on verification that exported code is production-quality and maintainable, and explicit component-to-code sync (e.g., design system tokens/components mapped 1:1 to code components) beyond scene-level export.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: * **Vanilla JS**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “`<spline-viewer>` is a native HTML web component and can be used with most web builders, frameworks, or browsers.”

   proof ↗⚑ flag

2. developerInspect any layer and get measurements, styles, assets, and code snippets (CSS/iOS/Android) without an editor seat

   weight 3 · round to Penpot
   Penpot~partialclaimed5/10

   Penpot's docs confirm an inspect feature giving code that matches design (CSS, HTML, SVG, JSON), which covers measurements/styles/code snippets for web, but there is no evidence of iOS/Android-specific code snippet generation, and no explicit documentation confirming that viewers/inspectors can access this without a paid editor seat. missing for 10: iOS/Android code snippet support, explicit seat-free viewer/inspect access confirmation, asset-export detail in inspect mode.

   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON”
   • [claimed-docs] “Unlimited Teams - Collaborate freely with unlimited teams.”
   • [claimed-docs] “No file limits - Create as many as you need within your storage capacity.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs describe code export as full-scene exports (Vanilla JS, Three.js, React, Next.js, react-three-fiber) and a Code API for developers, but there is no evidence of a dev-handoff/inspect mode that lets a non-editor viewer inspect a specific layer for measurements, styles, assets, or CSS/iOS/Android snippets without holding an editor seat.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Penpot~partialprobed5/10

   Penpot documents extensive API/plugin/MCP access (objects and properties, webhooks, access tokens, plugin system) suggesting broad programmatic control, but there's no explicit claim or evidence of full UI/API parity, and probes for an OpenAPI/swagger spec returned 404s, indicating the API surface isn't fully discoverable or documented as complete. missing for 10: explicit statement of full UI-API feature parity, a public OpenAPI/schema reference, and independent (community/hands-on) confirmation that all UI actions are scriptable via API.

   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [claimed-docs] “Our plugin system brings the flexibility that devs need to create and publish their own custom extensions.”
   • [claimed-docs] “Use access tokens as an alternative login authentication. They can allow an app to access Penpot's API.”
   • [claimed-docs] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://help.penpot.app/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://help.penpot.app/openapi.json, https://help.penpot.app/swagger.json, https://help.penpot.app/…”
   • [probe] “official MCP server documented at https://penpot.dev/ai/mcp-server”

   proof ↗⚑ flag

   Spline~partialprobed5/10

   Spline offers real API-like surfaces for AI-native workflows — a Code API for runtime object/property control (spline-docs-6, -17), a Real-time API and webhooks for external data/events (spline-docs-9, -10, -26), and notably an official MCP server that lets AI clients like Claude/Cursor/Codex drive the live editor tab directly (spline-docs-13, -36, -53) plus an AI Agent that can create objects, materials, lighting and interactivity through the editor (spline-docs-20, -40, -55). However, probing for a formal REST/OpenAPI spec returned 404s across all candidate paths (spline-probe-3), and the documented APIs are scoped to runtime manipulation/events, not full parity with the UI's modeling toolset (booleans, hair systems, physics, gaussian splatting, materials library) — so full UI-equivalent API coverage is not evidenced. missing for 10: a documented comprehensive API/SDK exposing full scene-authoring parity (modeling, materials, physics, animation) rather than just runtime triggers/MCP-driven editor control, and independent confirmation of API completeness.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [claimed-docs] “The AI Agent builds and edits 3D scenes for you. Describe what you want and it does the work through the editor itself — creating objects, s…”
   • [claimed-docs] “The **Spline MCP Server** connects AI coding tools like **Claude**, **Cursor**, **Codex**, and **Antigravity** directly to your Spline edito…”
   • [claimed-docs] “The Spline MCP Server connects AI coding tools like Claude, Cursor, Codex, and Antigravity directly to your Spline editor.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Spline
   Penpot!disputedcontradicted5/10

   Penpot's docs promise open formats and no lock-in — the file format is open and design data can be inspected/exported as CSS, HTML, SVG and JSON, and self-hosting gives full data control (penpot-docs-21, penpot-docs-28, penpot-docs-38). However, a hands-on community report directly contradicts full-data export, stating the user 'had no way to export the diagram as one file like PDF or JPG. I could only export a layer' (penpot-comm-5), suggesting the practical export experience falls short of the 'export all my data and leave' promise. Missing for 10: independent confirmation of a full-project/all-files bulk export, verification that the open file format round-trips completely outside Penpot, and resolution of the community-reported export limitation.

   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [community] “Maybe I'm using it wrong... when I tried Penpot about a year ago, I had no way to export the diagram as one file like PDF or JPG. I could on…”

   proof ↗⚑ flag

   Spline✓fullclaimed7/10

   Spline documents self-hosted export (full project, assets, and runtime as a self-contained ZIP) and code export in multiple open web formats (Vanilla JS, Three.js, React, Next.js, react-three-fiber), giving users a way to take their scene data out of the platform entirely rather than being locked into a proprietary cloud-only format. Missing for 10: no evidence of exporting to standard interchange 3D formats (e.g., glTF/OBJ), no independent/hands-on confirmation that self-hosted exports are truly complete and portable, and no mention of exporting non-visual metadata (variables, version history) alongside the scene.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Penpot
   Penpot~partialclaimed6/10

   Penpot is well known as open-source (GitHub repo referenced) and docs emphasize open standards, open file format, and self-hosting, which implies source availability, but the evidence pack lacks an explicit statement of the license type or direct pointer to license terms. missing for 10: explicit license name/terms (e.g. MPL-2.0) cited in docs, confirmation that full source (not just plugin API) is published under that license.

   • [github] “developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [claimed-docs] “Penpot vs Figma: Open-source alternative with self-hosting, unlimited files, native design tokens.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline is a closed, proprietary commercial design tool; nothing in the evidence pack mentions an open-source license or publicly available source code for the core product (only exported project assets can be self-hosted, which is not the same as open-sourcing the tool's source).

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Penpot
   Penpot✓fullcommunity8/10

   Penpot provides extensive first-party self-hosting documentation (Docker Compose, Kubernetes/Helm, on-prem, private cloud, 3-minute setup) and explicitly extends this to AI tooling by letting users deploy the MCP server in their own environment. Community reports corroborate real-world self-hosting via Docker/Portainer working, though some users report performance/stability issues at scale, which is a caveat rather than a failure of the self-hosting capability itself. Missing for 10: no first-party performance benchmarks or hardening guidance addressing the community-reported instability at scale.

   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Deploy with docker compose... Use Kubernetes in its different flavors: Deploy the official Helm Chart”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “you can set up an instance of Penpot in just 3 minutes!”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [community] “I've been toying a little with self hosted Penpot and it was really nice... Penpot was easy to use though it felt a little difficult to hand…”
   • [community] “Have been self-hosting this on Docker/Portainer for several weeks for a few people. Works fine so far.”
   • [community] “I'm willing to pay the 'performance tax' of the web stack/self-hosting if it means my design files aren't held hostage in a proprietary clou…”

   proof ↗⚑ flag

   Spline—none0/10

   Spline is an inherently cloud/multiplayer SaaS editor ('files live in the cloud', 'multiplayer from the ground up') with no evidence of a self-hostable core editor. The 'Self-Hosted' feature only lets users export a finished scene/runtime as a static ZIP for embedding elsewhere — it does not let anyone run the Spline design tool itself on their own infrastructure.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ flag

Plugins

1. developerA documented plugin API with typings and samples lets me build and distribute my own editor extensions

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

   Docs confirm a dedicated plugin API/system ('Our plugin system brings the flexibility that devs need to create and publish their own custom extensions', 'Use community plugins or build your own') and a marketplace with 113+ community plugins, showing developers can and do build/distribute extensions. However, no evidence pack item shows actual typings, SDK reference docs, or code samples/tutorials for the plugin API itself. Missing for 10: documented TypeScript typings, published API reference/sample plugin code, and independent developer confirmation of using the plugin API to build an extension.

   • [claimed-docs] “Our plugin system brings the flexibility that devs need to create and publish their own custom extensions.”
   • [claimed-docs] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [claimed-docs] “Use community plugins or build your own.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline documents a Code API, MCP server, webhooks, and export pipelines for integrating exported scenes into external apps, but there is no evidence of a documented plugin/extension API (with typings and samples) for building and distributing extensions to the Spline editor itself, and an OpenAPI/SDK probe returned 404s. Missing for 10: a documented editor plugin SDK, typings/type definitions for plugin development, and sample plugin code or a plugin marketplace/distribution mechanism.

   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “Spline MCP Server — drive Spline from Claude, Cursor, Codex and other MCP clients, straight into your open editor tab.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.spline.design/openapi.json, https://docs.spline.design/swagger.json, https://docs.splin…”

   proof ↗⚑ flag

2. designerExtend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more

   weight 2 · round to Penpot
   Penpot~partialcommunity6/10

   Docs confirm a plugin system and marketplace with 113+ plugins spanning accessibility, code, AI, and design-system tools, plus first-party docs on building custom extensions (penpot-docs-24, penpot-docs-5, penpot-docs-37). However, community feedback suggests the plugin ecosystem is still much smaller/younger than competitors' (penpot-comm-20 notes needing a 'bigger community' and missing pre-built element libraries), and there's no independent hands-on verification of marketplace breadth or quality. Missing for 10: independent reviews of specific popular plugins, marketplace UI/discovery evidence, and confirmation the 113+ figure reflects an actively curated, high-quality ecosystem rather than a small/early one.

   • [claimed-docs] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [claimed-docs] “Our plugin system brings the flexibility that devs need to create and publish their own custom extensions.”
   • [claimed-docs] “Use community plugins or build your own.”
   • [community] “Needs a bigger community. I know this project but still use Figma because in Figma I can simply use pre-created Elements from e.g. Ionic or …”

   proof ↗⚑ flag

   Spline—none0/10

   No evidence of a plugin community, marketplace, or third-party extensions (icons, data fillers, accessibility checkers) for Spline; the evidence only covers Spline's own built-in features (AI tools, MCP server, code export, materials library).

   ⚑ flag

Pricing

1. product managerPublished plan pricing makes seat types, tiers, and AI-feature gating clear before procurement

   weight 1 · round to Spline
   Penpot—none0/10

   The evidence pack includes only scattered pricing-page fragments (unlimited teams, no file limits, community plugins) but no structured breakdown of seat types, plan tiers, or which AI features are gated behind specific plans. No pricing table, tier comparison, or AI-feature-gating disclosure is documented anywhere in the pack.

   • [claimed-docs] “Unlimited Teams - Collaborate freely with unlimited teams.”
   • [claimed-docs] “No file limits - Create as many as you need within your storage capacity.”
   • [claimed-docs] “No file limits. Create as many as you need within your storage capacity. ... Unlimited Teams. Collaborate freely with unlimited teams.”
   • [claimed-docs] “Use community plugins or build your own.”

   proof ↗⚑ flag

   Spline~partialclaimed2/10

   Only one evidence item references the pricing page at all, and it's a bare fragment listing a few feature bullets (code/self-hosted export, version history, team library) with no visible seat types, tier names, or explicit AI-feature gating breakdown. Missing for 10: documented tier names/pricing, seat-type definitions, explicit AI feature gating per tier, and any independent corroboration of the pricing page's clarity.

   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

2. designerThe free tier supports real design work — usable editor and collaboration without a paid seat

   weight 2 · round to Penpot
   Penpot~partialcommunity6/10

   Penpot's free tier documented as unlimited files and unlimited teams, and the core editor supports components, prototyping, and design tokens without gating behind a paid seat, which supports real collaborative design work. However, community reports raise concerns about performance/stability at scale (crashes, lag with many layers/pages) that could limit usability for complex real work, and there's no explicit pricing-page breakdown confirming free tier includes full collaboration features like comments/permissions. missing for 10: explicit free-tier feature/seat-limit breakdown from pricing page, independent confirmation that free tier collaboration (comments, real-time multiplayer) is unrestricted, and resolution of community-reported performance/stability issues affecting real design work.

   • [claimed-docs] “Unlimited Teams - Collaborate freely with unlimited teams.”
   • [claimed-docs] “No file limits - Create as many as you need within your storage capacity.”
   • [claimed-docs] “No file limits. Create as many as you need within your storage capacity. ... Unlimited Teams. Collaborate freely with unlimited teams.”
   • [claimed-docs] “Use community plugins or build your own.”
   • [claimed-docs] “A component is a layer or group of layers that can be reused multiple times across files. This can help you maintain consistency across a gr…”
   • [claimed-docs] “Penpot allows you to prototype interactions by connecting boards, which can act as screens.”
   • [community] “Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too. I run it on Dedicated server with 64GB …”
   • [community] “I really wanted to like penpot, but when I tried a few months ago, simply navigating between pages (even on the example documents) was causi…”
   • [community] “Currently Penpot's performance starts dropping rapidly once you approach around 1000 layers. Most robust design systems I see run around 10-…”

   proof ↗⚑ flag

   Spline~partialclaimed3/10

   Docs describe Spline as 'multiplayer from the ground up' with cloud-based files that several people can edit at once, suggesting collaboration is core to the product rather than gated behind a paid seat, but the evidence pack has no explicit free-tier pricing page detail confirming seat limits, viewer/editor caps, or whether real-time collaboration is unrestricted on the free plan. The one pricing-page snippet (spline-docs-33) lists Code/self-hosted exports, version history, and Team Library without clarifying tier boundaries. missing for 10: explicit free-tier plan page detailing seat/collaborator limits, independent user reports confirming free-tier collaboration works in practice.

   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once”
   • [claimed-docs] “is multiplayer from the ground up: your files live in the cloud and several people can edit the same one at once.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Penpot
   Penpot✓fullclaimed7/10

   Penpot's self-hosting model directly delivers data residency choice: users can run Penpot in their own private cloud, on-premise, or any environment, giving full control over where data lives, and this extends to the MCP server which can also be self-deployed rather than routed through third-party clouds. Missing for 10: no first-party managed 'choose a region' feature for the SaaS-hosted offering, and no independent verification of self-hosting data-control claims beyond docs.

   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [claimed-docs] “you can set up an instance of Penpot in just 3 minutes!”

   proof ↗⚑ flag

   Spline—none0/10

   No evidence in the pack mentions data residency, region selection, or storage location controls; Spline docs discuss cloud storage, multiplayer, exports and MCP but never a data-region choice. missing for 10: any mention of region/residency options, data center choice, or compliance certifications tied to storage location.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Penpot
   Penpot~partialclaimed6/10

   Penpot's self-host docs explicitly state 'Keep your data private. Penpot will never make business out of your data. Choose where and how to host it,' which directly addresses preventing data from being used for AI training by keeping it entirely under user control. However, this is a general privacy claim tied to self-hosting rather than an explicit AI-training opt-out policy or contractual clause, and there's no independent/third-party corroboration of this specific promise. missing for 10: explicit AI-training-specific policy/ToS language, independent verification of the no-training claim, and clarity on cloud-hosted (non-self-hosted) instance data usage.

   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”

   proof ↗⚑ flag

   Spline—none0/10

   No evidence in the pack addresses AI-training data opt-out, privacy settings, or data usage policies for model training; the docs focus entirely on design/collaboration/AI-generation features with no mention of privacy controls or training data exclusion.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Penpot
   Penpot~partialclaimed4/10

   Penpot's self-hosting and 'keep your data private... decide where and how to host it' messaging (penpot-docs-28, penpot-docs-38) implies data control, and self-hosting inherently lets an org manage retention/deletion at the infrastructure level. However, there is no explicit documentation of data retention policies, file/version deletion mechanisms, or GDPR-style erasure APIs for AI-processed data. Missing for 10: explicit retention/deletion API or policy docs, confirmation of how MCP-accessed data is retained/purged, independent verification of deletion behavior.

   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”

   proof ↗⚑ flag

   Spline—none0/10

   The evidence pack contains no mention of data retention policies, deletion controls, data export for compliance, or privacy/GDPR settings for AI-native users; it covers only design, collaboration, export, and MCP/AI features. Missing for 10: any documentation of data retention settings, account/file deletion controls, or privacy compliance mechanisms.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Penpot—none0/10

   The evidence pack shows self-hosting and data-privacy marketing claims (e.g., 'Keep your data private,' 'never make business out of your data') but never mentions a specific telemetry/usage-tracking opt-out setting or configuration flag. Missing for 10: explicit documentation of a telemetry toggle or opt-out mechanism, confirmation of what usage data is collected, and any independent verification that self-hosted instances disable tracking by default.

   • [claimed-docs] “Keep your data private. Penpot will never make business out of your data. Choose where and how to host it, and decide who has access to it.”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”

   proof ↗⚑ flag

   Spline—none0/10

   No evidence in the pack addresses telemetry, analytics, or usage tracking opt-out settings for Spline; the docs cover design features, MCP, exports, and collaboration but nothing about privacy/tracking controls. This is a fair axis for a cloud-based SaaS design tool, so absence of evidence yields 'none'.

   ⚑ flag

1. designerPrototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product

   weight 1 · round to Spline
   Penpot—none0/10

   Evidence only shows basic board-to-board click interactions (penpot-docs-12, penpot-docs-14); nothing in the pack mentions animation/transition effects between states, conditional logic, variables, or scroll-triggered effects in prototypes. This is an applicable axis for a prototyping tool, but no evidence supports these advanced behaviors.

   • [claimed-docs] “Penpot allows you to prototype interactions by connecting boards, which can act as screens.”
   • [claimed-docs] “Design responsive and rules-based interfaces with wireframes, interactive prototypes, and CSS Grid and Flex layouts.”

   proof ↗⚑ flag

   Spline✓fullclaimed8/10

   Spline's docs strongly evidence advanced prototyping behavior: states/events/actions interaction model, variables and real-time API, webhooks for event-driven reactions, animation, multi-scene transitions, physics, and even code/HTML embedding for custom logic — all built to make prototypes feel like real products. Missing for 10: independent hands-on validation of complex behavior chains (scroll-driven effects specifically) and no dedicated 'scroll trigger' doc beyond general events/actions system.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “The Real-time API feature in Spline allows you to integrate external services, retrieve or send data, and automate responses based on events…”
   • [claimed-docs] “Webhooks in Spline allow you to create real-time, event-driven interactions by listening for and responding to external events.”
   • [claimed-docs] “By using webhooks, your Spline project can automatically trigger actions, update variables, and react to data sent from external sources”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “On Spline you can create different types of physics simulations, each object can be adjusted to react to gravity and collision forces.”
   • [claimed-docs] “A file can carry one HTML document — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the 3D …”
   • [claimed-docs] “It enables you to trigger actions, modify object properties, and create dynamic, responsive 3D environments directly from your existing code…”

   proof ↗⚑ flag

2. designerWire screens into clickable prototypes with triggers, transitions, and overlays — no code required

   weight 2 · round to Penpot
   Penpot✓fullcommunity6/10

   Docs confirm board-to-board prototyping ("connect boards, which can act as screens") and marketing copy references "interactive prototypes"; a community user corroborates that "the prototype feature is working great." However, the evidence pack never details specific trigger types, transition/animation options, or overlay behavior, so the depth of the interaction model is unverified. Missing for 10: detailed documentation of trigger/transition/overlay options, hands-on walkthrough of prototyping fidelity, and independent reviews specifically praising or critiquing interaction complexity.

   • [claimed-docs] “Penpot allows you to prototype interactions by connecting boards, which can act as screens.”
   • [claimed-docs] “Design responsive and rules-based interfaces with wireframes, interactive prototypes, and CSS Grid and Flex layouts.”
   • [community] “It's really a fantastic tool, we are using it since several months in replacement of figma and Adobe XD. The prototype feature is working gr…”

   proof ↗⚑ flag

   Spline~partialclaimed6/10

   Docs confirm no-code interactivity via states/events/actions (spline-docs-31) and multi-scene transitions via the Events system's Scene Transition action (spline-docs-61), which directly supports triggers and transitions for prototyping. However, 'overlays' are only evidenced via the Code tab feature, which requires writing HTML/CSS/JS (spline-docs-11/24), contradicting the 'no code required' framing for that specific element, and there is no dedicated hands-on or independent account of designers building full clickable multi-screen prototypes end-to-end. Missing for 10: a no-code overlay/layering mechanism, and independent/hands-on evidence of a complete click-through prototype workflow across screens.

   • [claimed-docs] “Most interactivity in Spline needs no code at all. It's built from **states, events and actions**”
   • [claimed-docs] “You can create multiple scenes within the same Spline file... It's possible to transition between scenes with the Events system by using a S…”
   • [claimed-docs] “A file can carry one **HTML document** — markup, CSS and JavaScript — that the editor renders in a sandboxed iframe layered exactly over the…”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”

   proof ↗⚑ flag

Canvas

1. designerFrames can behave responsively — auto layout, constraints, and grids resize designs the way real UIs flex

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

   Penpot's marketing docs confirm CSS Grid and Flex layout support for responsive/rules-based interfaces (penpot-docs-14), but there is no detailed documentation of auto-layout resizing behavior, constraints on resize, or grid systems working the way native UI frameworks flex, and no independent/hands-on confirmation of these specific behaviors. Community evidence instead focuses on general performance/stability issues rather than confirming responsive layout fidelity. missing for 10: detailed docs on constraints-based resizing, auto-layout resize rules, hands-on validation that grids/flex truly mimic real UI responsiveness.

   • [claimed-docs] “Design responsive and rules-based interfaces with wireframes, interactive prototypes, and CSS Grid and Flex layouts.”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”

   proof ↗⚑ flag

   Spline—none0/10

   Spline's docs cover 3D modeling, materials, animation, multiplayer, AI generation, and code export, and even mention a 2D canvas (Hana) for interfaces, but nowhere is there mention of auto layout, constraints, or responsive grid systems that would let frames resize like real UI layouts. Missing for 10: any documentation of auto-layout, constraint-based resizing, or grid systems for frames.

   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Hana's **AI Agent** designs for you. Describe a screen and it builds it on the canvas: layout, type, colour, effects, states and interaction…”
   • [claimed-docs] “describe a screen and Hana designs it, then edit it by hand”

   proof ↗⚑ flag

2. designerI get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work

   weight 3 · round to Spline
   Penpot—none0/10

   The evidence pack covers AI/MCP integration, self-hosting, plugins, components, prototyping, and design tokens, but contains no documentation or hands-on mention of pen/path editing tools, boolean path operations, or precise alignment/snapping features. Community comments only compare general UI polish and performance to Figma without confirming these specific vector-editing capabilities.

   ⚑ flag

   Spline~partialclaimed5/10

   Docs confirm a pen tool for custom 2D shapes (spline-docs-43), boolean operations (Union/Subtract/Intersect) for objects (spline-docs-60), a dedicated 2D canvas with vector networks for interfaces (spline-docs-38), and extrusion turning 2D shapes into 3D (spline-docs-42) — core vector-editing primitives are present. However, there's no documentation of precise alignment/distribution tools, grids, or snapping, and no independent/hands-on evidence validating these tools for serious interface design work versus its primary 3D focus. Missing for 10: alignment/snapping tooling documentation, path-editing depth (e.g., bezier handle controls), independent corroboration of professional UI design usage.

   • [claimed-docs] “The pen tool enables you to create custom 2D shapes in the 3D space. It works in a familiar way to other 2D or UI design tools.”
   • [claimed-docs] “There are 3 different Boolean Operations that you can apply to a set of selected 3D objects: Union ... Subtract ... Intersect”
   • [claimed-docs] “A 2D canvas for interfaces and animated graphics — vector networks, effects, typography, and real 3D shapes lifted straight out of flat vect…”
   • [claimed-docs] “Although 2D objects don't have a depth parameter, they can quickly become 3D using a modeling operation called **Extrusion**.”

   proof ↗⚑ flag

Files

1. designerExport production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices

   weight 2 · round drawn
   Penpot—none0/10

   The evidence pack contains no first-party documentation describing PNG/SVG/PDF export options, per-layer export presets, scale factors, or slices — the closest data point is a community comment noting an inability to export a whole file (only a single layer) in past testing, which is negative rather than supportive. No docs, help-center pages, or hands-on confirmation of this specific export feature set are present.

   • [community] “Maybe I'm using it wrong... when I tried Penpot about a year ago, I had no way to export the diagram as one file like PDF or JPG. I could on…”

   proof ↗⚑ flag

   Spline—none0/10

   Spline's documented export options are all code/runtime based (Vanilla JS, Three.js, React, Next.js, react-three-fiber, self-hosted ZIP, spline-viewer web component) with no mention of PNG/SVG/PDF raster/vector asset export, per-layer presets, scales, or slices anywhere in the evidence pack.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag

2. developerThe file format is open or documented, so my designs stay portable and toolable outside the vendor's editor

   weight 1 · round to Penpot
   Penpot✓fullclaimed8/10

   Penpot explicitly documents an open file format built on open standards (SVG, CSS, HTML, JSON) and is open-source itself, explicitly contrasting with Figma's proprietary format, plus REST/webhook APIs and plugin system for external tooling. Missing for 10: independent third-party corroboration that .penpot files are actually opened/edited by external tools, and no dedicated file-format spec page (llms.txt/openapi probes 404).

   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON as well as Penpot's open file for…”
   • [claimed-docs] “Inspect and integrate code that actually matches design. Enjoy open standards like CSS, HTML, SVG and JSON”
   • [claimed-docs] “Penpot vs Figma: Open-source alternative with self-hosting, unlimited files, native design tokens.”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”
   • [github] “developers feel at home using Penpot, because design is expressed as code, enabling a direct translation and shipping products faster.”

   proof ↗⚑ flag

   Spline~partialclaimed5/10

   Spline's native .spline file format itself is never documented as open or given a public schema; instead portability is achieved indirectly via export mechanisms — code export to Vanilla JS/Three.js/React/Next.js/react-three-fiber, a self-hosted ZIP with the runtime, and a Code API — which let designs be used outside the editor without exposing/documenting the native format. missing for 10: an open/published spec for the native .spline file format, third-party tooling that reads/writes it directly, independent confirmation that exported code is a full fidelity substitute for the file itself.

   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS, Three.js, React, Next.js, react-three-fiber”
   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “The Code API allows you to seamlessly integrate interactive 3D experiences into your projects, offering greater control and customization.”
   • [claimed-docs] “Spline allows you to export the code of your scene as: **Vanilla JS**... **Three.js**... **React**... **Next.js**... **react-three-fiber**”
   • [claimed-docs] “Spline allows you to export the code of your scene as: Vanilla JS ... Three.js ... React ... Next.js ... react-three-fiber”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”

   proof ↗⚑ flag

3. developerSelf-host the full design platform on my own infrastructure under an open-source license

   weight 2 · round to Penpot
   Penpot!disputedcontradicted6/10

   Docs strongly document self-hosting (docker compose, Kubernetes/Helm/OpenShift/Rancher, private cloud/on-prem deployment, 'set up in 3 minutes', open-source positioning vs Figma) with no artificial file/team limits, which is exactly what this story asks for. However, hands-on community reports contradict the ease-of-self-hosting claim: one user says self-hosted instance 'crash after a few minutes and not properly show the canvases. So a no for me' and others report it being 'unstable, very crash prone... huge memory hog' under modest load, even as another reports self-hosting 'works fine so far.' Missing for 10: explicit confirmation of the open-source license terms/scope, independent security/production-readiness audit of self-hosted deployments, and resolution of the stability complaints reported by self-hosters.

   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Deploy with docker compose... Use Kubernetes in its different flavors: Deploy the official Helm Chart”
   • [claimed-docs] “Deploy with docker compose ... Use Kubernetes in its different flavors”
   • [claimed-docs] “you can set up an instance of Penpot in just 3 minutes!”
   • [claimed-docs] “Penpot is the only open-source design platform that is truly deployment agnostic. Run it in your private cloud, on-premise, or any environme…”
   • [community] “I've been toying a little with self hosted Penpot and it was really nice... Penpot was easy to use though it felt a little difficult to hand…”
   • [community] “I tried to self host penpot a few months ago but the app would crash after a few minutes and not properly show the canvases. So a no for me.”
   • [community] “Unstable, very crash prone with just a few users designing 10 plus pages. And a huge memory hog too. I run it on Dedicated server with 64GB …”
   • [community] “Have been self-hosting this on Docker/Portainer for several weeks for a few people. Works fine so far.”

   proof ↗⚑ flag

   Spline—none0/10

   Spline is a cloud-based, closed-source SaaS design tool; the only 'self-hosted' feature documented is exporting a finished 3D scene as a self-contained ZIP for use in your own web app, not self-hosting the design editor/platform itself. There is no evidence of an open-source license, on-prem installer, or self-hostable server for the full editor.

   • [claimed-docs] “The Self-Hosted export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a fully se…”
   • [claimed-docs] “allows you to export your entire project, including all assets and the Spline runtime, as a fully self-contained ZIP file”
   • [claimed-docs] “The **Self-Hosted** export option in Spline allows you to export your entire project, including all assets and the Spline runtime, as a full…”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”
   • [claimed-docs] “Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”
   • [claimed-docs] “It's web-based. Spline runs in the browser on any platform, with nothing to install and no GPU requirements to check.”

   proof ↗⚑ flag

4. designerFull version history lets me name milestones, compare, and restore any earlier state of a file

   weight 2 · round to Spline
   Penpot—none0/10

   No evidence in the pack mentions version history, milestone naming, diffing/comparison, or restore-to-earlier-state functionality; only component/plugin/self-host/AI features are documented. missing for 10: any mention of file version history, snapshot naming, diff/compare tools, or restore capability.

   ⚑ flag

   Spline~partialclaimed6/10

   Docs confirm a Version History feature that lets users preview all saved versions, track changes, and restore/recover earlier file states, plus manually save new versions ([spline-docs-15],[spline-docs-29],[spline-docs-33]). However, there is no evidence of explicitly naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: explicit naming/labeling of milestone versions, a diff/compare UI between versions, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files. This feature helps you track changes, recover previou…”
   • [claimed-docs] “Version History allows you to access and preview all the saved versions of your files.”
   • [claimed-docs] “Code & Self-hosted exports * File version history * Team Library”

   proof ↗⚑ flag