Penpot vs Rive

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 Rive
   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

   Rive✓fullprobed8/10

   Rive documents an MCP integration letting AI tools create/modify complex View Models, State Machines, Layouts, and Shapes directly in the Editor, plus RML (a text-based file format) explicitly designed so coding agents can build/modify Rive files programmatically, and a CLI for agent-driven generation. This goes beyond read-only access into genuine write-capable agent tooling. Missing for 10: independent/hands-on verification of the MCP tools working in practice and more detail on the write-scope limits of the MCP server.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   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

   Rive!disputedcontradicted4/10

   Rive's runtimes expose a documented programmatic Renderer interface (rive-gh-1/2/3) and RML lets code/agents construct .riv content (rive-docs-13/20/25), and export docs describe exporting to 'websites, mobile apps, games, videos' (rive-docs-7/8) — suggesting a programmatic render/export surface. However, hands-on community feedback directly contradicts image/video export capability: users report 'no way to export movie files' and ask 'can I export video assets with this!?' with no answer (rive-comm-3, rive-comm-10), indicating the actual exportable surface is limited to the .riv runtime format rather than screenshots/images/production video as the story requires. Missing for 10: documented API/CLI for agent-triggered screenshot or image/video export, and confirmation this gap has been resolved.

   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   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 to Penpot
   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

   Rive~partialprobed5/10

   Rive documents an official MCP server connecting the Editor to AI tools, letting agents create/modify View Models (variable-like data), State Machines, Layouts, and Components (rive-docs-19, rive-docs-27, rive-docs-10, rive-docs-11). This covers some 'design context' elements (component mappings, variables via view models) but is framed as agents building/editing Rive content rather than pulling existing frames or screenshots for implementation elsewhere. Missing for 10: explicit screenshot/frame extraction capability, evidence of pulling existing design context (vs. generating new), and independent/hands-on confirmation of the MCP workflow.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round to Penpot
   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

   Rive✓fullprobed7/10

   Rive's docs are served in agent-friendly markdown (docs/*.md return 200) and explicitly point agents to a documentation index at https://rive.app/docs/llms.txt for full-site context, satisfying the 'point an agent at llms.txt or agent-oriented docs' story even though the conventional root-level /llms.txt path 404s. Missing for 10: direct confirmation that /docs/llms.txt itself loads and contains a complete index, and no independent (non-vendor) corroboration of an agent successfully using it.

   • [probe] “PROBE llms.txt: HTTP 404 at https://rive.app/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://rive.app/docs/getting-started/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”

   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

   Rive~partialclaimed4/10

   Rive exposes open-source runtimes as libraries (rive-gh-1, rive-docs-21) and mentions a CLI for agent-driven generation and RML for text-based/coding-agent workflows (rive-docs-26, rive-docs-25, rive-docs-30), suggesting some scriptable/automatable path outside the interactive editor. However, there is no explicit documentation of headless rendering, CI pipeline integration, or automated test/build usage of the CLI or runtimes. Missing for 10: explicit headless/CI usage docs, CLI reference/flags, examples of automated pipeline integration, independent confirmation of non-interactive operation.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullprobed7/10

   Rive documents a first-party MCP integration letting users connect the Rive Editor to AI tools via MCP so AI can perform tasks like creating View Models, State Machines, Layouts, and Shapes, confirmed by both docs and a dedicated probe. Missing for 10: independent/hands-on verification of the MCP integration working in practice and details on which MCP clients/servers are supported beyond the editor's own tools.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   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

   Rive✓fullprobed8/10

   Rive's docs explicitly describe an official MCP server that connects the Rive Editor to AI agents/tools, letting AI handle View Models, State Machines, Layouts, Shapes, etc., and this is confirmed via a dedicated docs page and probe. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice beyond first-party docs.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Rive
   Penpot—none0/10

   Evidence covers Penpot's MCP server, plugin API, webhooks, and REST access tokens, but there is no mention of an official CLI tool for interacting with Penpot as an AI-native workflow interface. The MCP server is a distinct integration mechanism, not a CLI.

   ⚑ flag

   Rive~partialclaimed3/10

   The Rive homepage claims users can 'let an agent generate them with the CLI' (rive-docs-26), indicating an official CLI exists for AI-agent workflows, but no other evidence pack item documents CLI installation, commands, or usage — most AI-agent tooling evidence instead centers on the MCP server and in-editor AI agent, not a standalone CLI. Missing for 10: dedicated CLI docs/reference, install instructions, command examples, and independent/hands-on corroboration of the CLI working.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Rive✓fullprobed8/10

   Rive documents open-source runtime APIs (web, mobile, game engines) for loading and controlling animations programmatically (rive-docs-21, rive-gh-1, rive-docs-14/15), plus a text-based file format (RML) explicitly designed for coding agents and automated workflows (rive-docs-13, 20, 25, 30), and an official MCP server/AI agent integration for driving the Editor via AI tools (rive-docs-19, 27, rive-probe-4, rive-docs-9/18). Together these give an AI-native user multiple documented, agent-friendly ways to control the product beyond the GUI. Missing for 10: a formal REST/OpenAPI-style public API (probe shows 404s for openapi/swagger endpoints) and independent third-party corroboration of programmatic API usage.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Rive
   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

   Rive✓fullclaimed8/10

   Rive documents open-source official runtimes (SDKs) for web, mobile, game engines, and other platforms, with a public GitHub repo (rive-runtime) implementing the loading/rendering API, plus explicit guidance on caching and using the same exported .riv file across supported runtimes. This directly satisfies 'build against official SDKs' for developers, including AI-native workflows via RML/MCP integration for programmatic file creation. Missing for 10: independent third-party corroboration of SDK quality/completeness across all listed platforms and more granular per-language SDK documentation (e.g., npm/Swift/Kotlin package specifics).

   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Penpot
   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

   Rive—none0/10

   No evidence anywhere in the pack mentions webhooks, event subscriptions, or any push-notification API for Rive; the product is documented as a design/animation tool with editor, runtime, and MCP/AI-agent integrations, none of which reference webhook-based event delivery.

   ⚑ flag

Agentic features

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

   weight 2 · round to Penpot
   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

   Rive—none0/10

   Rive's docs describe an AI agent, MCP integration, and CLI that generate animations/code when invoked by a user, but there is no evidence of scheduled, unattended, or continuously running background automations — all AI features described are user-triggered, session-based interactions within the Editor.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullclaimed8/10

   Rive documents a built-in AI agent inside the Editor that writes code, generates layouts, data models, view models, state machines, and animation, letting users delegate repetitive/complex tasks to it directly within the product. This is first-party documented with specific task examples, though there's no independent/hands-on corroboration of its real-world effectiveness. Missing for 10: independent verification of the AI agent's actual capability/reliability, more detail on scope/limits of delegation.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   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

   Rive~partialprobed6/10

   Rive documents a built-in AI agent and MCP integration that let users describe tasks in natural language to generate ViewModels, state machines, layouts, and animation code, plus a CLI for agent-driven generation (rive-docs-9,10,18,19,26,27). However, this is entirely first-party documentation with no independent or hands-on confirmation that natural-language commands reliably drive the full editor experience, and community feedback focuses on pricing/licensing rather than the AI agent's real-world behavior. Missing for 10: independent/hands-on verification of the AI agent's natural-language command success, broader coverage beyond docs-based claims, and detail on command scope/limits.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   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

   Rive—none0/10

   While Rive has extensive documentation (runtime parameters, data binding, RML), there is no evidence of an interactive API reference with runnable/live code examples, and the OpenAPI probe returned 404s with no playground or sandbox mentioned.

   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   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

   Rive—none0/10

   A direct probe for OpenAPI/swagger spec endpoints (openapi.json, swagger.json, etc.) returned 404 for all candidates, and no docs mention a machine-readable API spec being downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   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

   Rive—none0/10

   No evidence of any versioned API scheme or documented deprecation policy for Rive's runtimes, editor APIs, or MCP integration; OpenAPI probes returned 404s and no changelog/versioning docs are cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   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 drawn
   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

   Rive—none0/10

   Rive's AI agent/MCP tooling is focused on generating code, view models, state machines, layouts, and animation logic — not on image generation, background removal, content-aware fill, or copy suggestions for asset creation. No evidence names any of these specific asset-chore AI features; missing for 10: image generation, background removal, content-aware fill, copy/text suggestions.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   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 Rive
   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

   Rive~partialprobed6/10

   Rive documents an AI agent/MCP integration that generates View Models, State Machines, Layouts, Shapes and animation from prompts or via coding-agent workflows, and even an 'agent generate them with the CLI' claim on the homepage — this matches the story's spirit of prompt-driven first drafts. However, all evidence is first-party docs describing 'the first set of tools' as handling repetitive tasks rather than full end-to-end mockup generation, and there's no independent/hands-on corroboration of output quality. Missing for 10: independent or hands-on validation of AI-generated designs, clearer evidence of full mockup/layout generation (not just repetitive sub-tasks) from a single prompt.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   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

   Rive~partialclaimed6/10

   Rive documents an AI agent/MCP integration explicitly designed to let AI 'handle repetitive tasks, like creating complex View Models, State Machines with hundreds of states/layers, Layouts, Shapes, and more,' and RML provides a text-based file format enabling coding agents to script bulk edits outside the Editor. Components/instances also let one source change propagate across many instances. However, there's no independent/hands-on evidence of actual bulk-operation performance at scale, no documented API for batch scripting beyond RML/MCP, and no benchmarks or examples of large-scale bulk edits succeeding. Missing for 10: independent verification of bulk-task performance, concrete examples/benchmarks of large-scale batch operations, and a documented API/CLI for scripted bulk edits beyond the AI agent's stated purpose.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive~partialclaimed4/10

   Rive's State Machines and data-binding docs imply event-driven behavior (inputs, user actions, and data changes automatically triggering animation/state updates), and its AI Agent/MCP tooling can generate these State Machines and scripting-based behaviors programmatically. However, there's no explicit documentation of a rule-authoring system (e.g., conditional 'if event then action' automation) framed for AI-native/automation use beyond interactive animation triggers. Missing for 10: explicit rule-definition API/interface for arbitrary automation, examples of AI-native users authoring trigger-action rules, and independent confirmation beyond first-party docs.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Use scripting to create custom interactions, procedural animation, and behaviors that go beyond the built-in tools.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”

   proof ↗⚑ flag

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

   weight 1 · round to Rive
   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

   Rive~partialclaimed4/10

   Rive's Revision History provides automatic tracking of changes, previewing of past revisions, and non-destructive rollback to prior versions of a file (rive-docs-12, rive-docs-17, rive-docs-29), which covers version/rollback for the design file itself. However, the story targets 'automations' (AI-agent/MCP-driven workflows), and there is no evidence of versioning, diffing, or review specifically for AI-generated scripts, MCP actions, or automation pipelines — only generic file revision history. Missing for 10: dedicated versioning/review/rollback for AI-agent or MCP-generated automations, audit trail of agent actions, diff/compare tooling, and any independent confirmation of this workflow in practice.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   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 Penpot
   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

   Rive—none0/10

   Evidence covers animation, data binding, revision history, AI/MCP tooling, and export, but there is no mention of commenting, @mentions, or thread resolution features in Rive's editor. Revision history tracks changes but is not a comment/review workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive~partialclaimed4/10

   Docs confirm multiple people can work on the same file simultaneously with all changes tracked in Revision History, implying some multiplayer support, but there is no mention of live cursors, presence indicators, or real-time instant sync mechanics that the story specifically asks for. Missing for 10: explicit live cursor/presence UI, real-time sync latency claims, independent hands-on confirmation of simultaneous editing experience.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   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

   Rive—none0/10

   Rive is an animation/interactive-graphics tool with components, data binding, and view models, but there is no evidence of a design-tokens/variables system (colors, spacing, typography) with modes/themes applied across designs — the closest concepts (components, data binding) address reusability and runtime data, not token/theme management. Missing for 10: token or variable definitions, theme/mode switching, cross-design application of shared style values.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

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

   weight 3 · round to Rive
   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

   Rive✓fullclaimed8/10

   Rive's docs directly describe Components as reusable artboards where instances can be customized while changes to the source component propagate to all instances, matching the story's core requirement of variants/overrides linked to source. Missing for 10: no independent/hands-on corroboration of override behavior at scale, and no detail on variant-specific overrides beyond basic customization examples.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   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

   Rive—none0/10

   Rive's docs describe components/instances reused within a single Rive file where changes to a source component propagate to instances (rive-docs-11, rive-docs-28), but there is no evidence of a shared-library system that publishes components/styles across separate files or projects with controlled update propagation, which is the core of this story. Missing for 10: cross-file/cross-project library publishing, subscribing to a library, and controlled update notifications when a source library changes.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   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 Rive
   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

   Rive✓fullclaimed8/10

   Rive's core value prop is explicitly design-to-shippable-runtime: 'No mockups, no prototypes, no handoff... What you build in the editor is what ships in your app, game, or website' (rive-docs-23), backed by real runtime libraries that load .riv files directly into apps/games/web (rive-gh-1, rive-docs-21), reusable components/instances (rive-docs-11, rive-docs-28), and RML text representation enabling coding-agent-driven file construction (rive-docs-13, rive-docs-25, rive-docs-30). This is a genuine direct design-to-production path rather than a code-generation handoff, and MCP/AI agent tooling further bridges design and code workflows (rive-docs-9, rive-docs-19, rive-docs-27). Missing for 10: independent developer case studies confirming the 'no handoff' claim holds up in large production codebases, and clearer detail on how designers' Rive files integrate with existing component libraries/design systems in code.

   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   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

   Rive~partialprobed5/10

   Rive offers RML (text-based file format) and an MCP server that let AI/coding agents create View Models, State Machines, Layouts, and Shapes programmatically, plus open-source runtimes for playback/control — but the evidence pack does not confirm full parity with the Editor UI (e.g., no OpenAPI/REST API, no confirmation that timeline keyframing, revision history management, or component/instance authoring can be done entirely via API/CLI). missing for 10: a documented public REST/OpenAPI API surface, confirmation that all editor features (keyframe timelines, revision history, component instancing) are scriptable/API-accessible, and independent hands-on verification that AI/API workflows match UI capability.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”

   proof ↗⚑ flag

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

   weight 3 · round to Penpot
   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

   Rive!disputedcontradicted4/10

   Rive documents an open, text-based file representation (RML/XML) and open-source runtimes, suggesting some data portability (rive-docs-13, rive-docs-20, rive-docs-25, rive-docs-21, rive-gh-1). However, community feedback directly contradicts a full 'export and leave' story: users report no way to export movie/video assets (rive-comm-3, rive-comm-10) and note the open-source license only covers a narrow rendering subset while the actual content-creation editor remains proprietary and subscription-locked (rive-comm-5, rive-comm-1, rive-comm-2), undermining claims of full open-format data portability. missing for 10: documented full-fidelity export to universal open formats (e.g. video/SVG/JSON), open-source editor or file-format spec, and independent confirmation that RML round-trips 100% of file data without proprietary lock-in.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   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

   Rive~partialcommunity5/10

   Rive's runtimes are documented and confirmed on GitHub as open-source libraries (rive-docs-21, rive-gh-1, rive-gh-2), giving AI-native users real source access to the rendering/runtime layer, but community evidence notes the MIT license only covers a 'rendering abstraction layer, a subset of the Rive runtime' while the Editor itself (where files are authored) remains closed-source (rive-comm-5, rive-comm-1). missing for 10: full-product open license (editor/design tool source not published), independent confirmation of license file/terms, clarity on what runtime components are excluded from the OSS layer.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ 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

   Rive—none0/10

   Rive's core product is the proprietary Editor (a SaaS/desktop app); only a subset of the runtime rendering layer is open-source (MIT), and community evidence explicitly notes the editor itself cannot be self-hosted and requires the hosted tool to author content. No docs or evidence describe self-hosting the Editor or backend service.

   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   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

   Rive—none0/10

   No evidence of a documented editor plugin/extension API, typings, or samples for building third-party editor extensions; the evidence only covers runtimes, data binding, AI agent/MCP integration, and RML scripting, none of which document an extensibility API for building/distributing editor plugins.

   ⚑ 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

   Rive—none0/10

   No evidence of a plugin marketplace, third-party extension ecosystem, or add-ons like icon packs, data fillers, or accessibility checkers. The evidence only covers Rive's own built-in features (components, data binding, MCP/AI agent, RML) — none of which describe an external plugin/marketplace ecosystem. Missing for 10: any mention of a plugin API, extension marketplace, or third-party-built add-ons.

   ⚑ flag

Pricing

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

   weight 1 · round drawn
   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

   Rive—none0/10

   The evidence pack contains only product/docs content about Rive's features (animation, data binding, AI agent, MCP) and community discussion referencing informal price points ($25-$39/month) but no published pricing page, seat-type breakdown, tier comparison, or explicit AI-feature gating documentation.

   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   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

   Rive—none0/10

   No evidence describes what the free tier includes for editor/collaboration access; the only relevant community signal explicitly states that basic solo-dev animation work requires a paid subscription ($25-39/month), suggesting the free tier is not sufficient for real design work.

   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”
   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ 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 Rive
   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

   Rive✓fullcommunity8/10

   Rive's docs explicitly describe building interactive experiences responding to user input, screen size, scrolling, and application state (rive-docs-4), state machines/timelines/keyframes (rive-docs-3), and real-time data binding so animations update live (rive-docs-5, rive-docs-15, rive-docs-22, rive-docs-24) — directly matching the story's states/conditions/variables/scroll-effect prototyping needs. Community evidence corroborates real-world adoption for production-grade interactive UI/UX work (rive-comm-4, rive-comm-7), and Rive's own positioning ('no mockups, no prototypes... the real thing', rive-docs-16/23) reflects this design intent. Missing for 10: independent hands-on verification specifically of scroll-triggered effects and variable/condition-driven prototypes beyond vendor docs.

   • [claimed-docs] “Bring your designs to life with timelines, keyframes, and smooth interpolation.”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Connect animations, text, colors, layouts, and other properties to real-time data.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “I've been pushing over the past six months or so for multiple clients... to adopt Rive over Lottie and other past solutions, as I think it's…”
   • [community] “Truthfully the program they have looks fantastic at empowering UI/UX designers to do more with games... the workflow of this tool is definit…”

   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

   Rive~partialclaimed5/10

   Rive's State Machines and interaction docs (rive-docs-4, rive-docs-22, rive-docs-24) support building input-driven, trigger/transition-based interactivity without code, and rive-docs-16/23 frame the tool as skipping separate 'prototype' handoff entirely. However there is no evidence of a Figma-style multi-screen/overlay prototyping paradigm (linking distinct screens, overlay layers, click-through flows across artboards) — Rive's interactivity is scoped to state machines within/across components rather than an explicit screen-flow prototyping mode. Missing for 10: evidence of multi-screen linking, overlay/modal wiring, and click-through flow prototyping across separate artboards/screens.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”

   proof ↗⚑ flag

Canvas

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

   weight 2 · round drawn
   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

   Rive~partialclaimed5/10

   Rive's docs repeatedly reference "responsive layouts" and building interfaces that respond to screen size (rive-docs-1, rive-docs-4, rive-docs-9, rive-docs-18, rive-docs-26), and the AI tooling explicitly generates "Layouts" as an artboard-level construct (rive-docs-10). However, no evidence details the specific mechanics of auto layout, constraints, or grid systems the way Figma-style tools describe them. Missing for 10: explicit documentation of constraint-based resizing rules, grid systems, or auto-layout algorithms, and independent/hands-on confirmation that layouts flex like real UI frameworks.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   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 Rive
   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

   Rive!disputedcontradicted3/10

   Rive's docs market it as a full design-to-ship tool ('design, animate, and code in one place... no mockups, no prototypes, no handoff') and mention vector graphics and components, but there is no documentation of boolean operations, precise alignment/snapping tools, or advanced path editing. A hands-on community comment directly contradicts the 'professional vector tools' claim, calling the drawing toolset just 'a pen and a couple of basic shapes' and comparing inefficient pen-only workflows unfavorably to real illustration tools. missing for 10: boolean operations, alignment/snap tooling, path-editing depth, and any rebuttal to the community criticism of basic drawing tools.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “Looks kinda interesting but I am not gonna touch anything that thinks an acceptable set of drawing tools is 'pen and a couple of basic shape…”

   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

   Rive—none0/10

   Rive's documentation focuses on exporting .riv files for runtime playback across platforms (web, mobile, games) rather than static production assets like PNG/SVG/PDF with per-layer presets, scales, or slices; no such export presets are described anywhere in the evidence. Community feedback explicitly confirms this gap — one user complains 'it's so insane they don't offer any way to export movie files' and another asks 'can I export video assets with this!?' — indicating the tool lacks traditional multi-format asset export entirely.

   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   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

   Rive!disputedcontradicted4/10

   Rive documents RML (a text-based/XML representation of Rive files) and open-source runtimes that can load/parse .riv files (rive-docs-13/20/25/30, rive-gh-1/3), suggesting some portability outside the editor. However, community evidence directly disputes this: the open-source runtime is described as only a rendering/playback layer, and actually authoring or building Rive content still requires the proprietary, paid Rive Editor (rive-comm-5), undercutting claims of full format openness/portability. Missing for 10: a public, versioned .riv binary spec independent of RML, third-party tools that can author/edit .riv files without the vendor's editor, and confirmation that RML round-trips losslessly with the binary format.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   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

   Rive—none0/10

   Evidence shows only the rendering runtime is open-source (rive-docs-21, rive-gh-1/2/3), while the Editor itself is a hosted SaaS product requiring Rive's cloud service—there is no documentation of a self-hostable full design platform. Community discussion explicitly confirms this gap, noting the MIT license covers only 'a subset of the Rive runtime that requires the Rive Editor to build content for' (rive-comm-5), meaning the actual design/editing platform cannot be self-hosted.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

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

   weight 2 · round to Rive
   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

   Rive~partialclaimed6/10

   Rive's docs confirm automatic revision tracking, non-destructive restore, and the ability to select and edit a prior revision (rive-docs-12, rive-docs-17, rive-docs-29), which covers 'restore any earlier state.' However there is no evidence of naming/labeling milestones or a compare/diff view between versions. Missing for 10: named milestone/labeling capability, side-by-side or diff comparison between revisions, independent corroboration of the restore workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag