Penpot vs Canva

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

   Canva✓fullprobed9/10

   Canva ships an official MCP server explicitly documented to let AI assistants create designs from text, edit existing designs via natural language, manage assets/brand kits, and export/resize outputs — a clear write-capable agent surface, corroborated by a dedicated MCP docs probe. This is backed further by the Connect APIs (write-capable REST API with OpenAPI/SDK generation) and Apps SDK for programmatic design manipulation. missing for 10: independent/hands-on third-party verification that the MCP write operations work reliably in practice.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/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 Canva
   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

   Canva✓fullprobed8/10

   Canva's Connect APIs and MCP server both provide documented programmatic export capability — the MCP server explicitly supports 'Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, etc.) and resize designs for different channels', and the Connect APIs allow creating/syncing designs and assets with OpenAPI-generated SDKs, confirmed via a live probe of the MCP docs. This directly satisfies an agent's need to render/export designs programmatically. Missing for 10: independent/hands-on confirmation of actual export calls succeeding (no third-party corroboration, only first-party docs), and the OpenAPI spec itself wasn't resolvable via direct probe.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Penpot~partialprobed6/10

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

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

   proof ↗⚑ flag

   Canva~partialprobed6/10

   Canva has an official documented MCP server enabling AI assistants to search/retrieve designs, pages and folders, manage assets and brand kits, and export in multiple formats (PDF/PNG/JPG/etc.), which covers much of 'pulling real design context' for an agent to act on. However, the story's specific terms — frames, variables, component mappings — aren't explicitly evidenced, and there's no independent/hands-on confirmation that a coding agent can actually reconstruct implementation-level design context via this server. Missing for 10: explicit support for design variables, frame-level structural access, component-to-code mapping, and third-party corroboration of agent workflows.

   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

Agent access

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

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

   Canva✓fullprobed8/10

   Canva confirms an accessible llms.txt file (HTTP 200) plus multiple scoped llms.txt files for sub-docs (e.g., scim/llms.txt, admin/llms.txt, audit-logs/llms.txt) and dedicated .md docs pages (mcp.md, connect.md, apps.md) explicitly structured for agent consumption. missing for 10: independent/third-party confirmation of an agent successfully using llms.txt to navigate docs, and a root-level single canonical llms.txt covering all products rather than fragmented per-section files.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.canva.dev/llms.txt # Canva Developers Documentation This file lists documentation for Canva product…”
   • [claimed-docs] “Use the SCIM API to automate the provisioning of Canva user accounts for your team.”
   • [claimed-docs] “The Canva Admin API lets you manage teams, groups, and users in a Canva organization.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”

   proof ↗⚑ flag

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

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

   Canva~partialprobed5/10

   Canva's Connect APIs and bulk/personalization features (canva-docs-2, canva-docs-7, canva-docs-8, canva-docs-16, canva-docs-26) show that programmatic, non-interactive design generation and export are possible, and an OpenAPI description exists for SDK generation (canva-docs-31, canva-docs-36) which could support CI pipelines. However, Connect APIs are OAuth-based integrations meant for user-authorized platforms, not clearly documented as headless/service-account CI automation, and a probe for a hosted OpenAPI spec returned 404s (canva-probe-3), suggesting the automation surface is less mature for pure CI use. Missing for 10: explicit CI/service-account authentication flow, documented headless execution examples, and a verifiable OpenAPI spec endpoint.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Automatically create resized versions of designs in new dimensions, formats, or aspect ratios.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

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

   weight 3 · round to Penpot
   Penpot~partialclaimed3/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   All evidence describes Canva exposing an official MCP *server* so external AI assistants (Claude, ChatGPT, etc.) can call Canva's own design tools (canva-docs-5, canva-docs-28, canva-probe-4) — the opposite direction of the story, which asks whether Canva itself can act as an MCP client plugging into external MCP servers to use their tools. No evidence shows Canva consuming or configuring external MCP servers.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “If you're a user wanting to connect your personal AI assistant to Canva's AI Connector, see our Help Center”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

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

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

   Canva✓fullprobed9/10

   Canva ships an official MCP server (canva-docs-28, canva-probe-4) that lets AI assistants connect via natural language to Canva's design capabilities, with documented features spanning design generation, editing, discovery, export, asset/brand management, and collaboration (canva-docs-17 through 22, 33-35). Missing for 10: independent/hands-on third-party corroboration of the MCP server working in practice.

   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

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

   Canva~partialprobed5/10

   Canva does ship an official CLI, but it is scoped narrowly to creating and managing Canva Apps (the Apps SDK), not a general-purpose CLI for AI-native workflows like design generation, export, or automation via Connect APIs — those are exposed via APIs/MCP, not the CLI. missing for 10: evidence of CLI supporting broader AI-native tasks (design generation, bulk export, Connect API operations), independent/hands-on usage reports.

   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   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

   Canva✓fullprobed8/10

   Canva provides well-documented Connect APIs with an OpenAPI description for client SDK generation, plus Apps SDK, Admin API, SCIM API, and a first-party MCP server enabling AI assistants to drive Canva programmatically — directly matching an AI-native user's ability to drive the product via public API. Missing for 10: independent hands-on corroboration of API robustness/rate limits and a directly resolvable public OpenAPI file (probe found candidate OpenAPI endpoints 404, though docs claim one exists).

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Penpot—none0/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   While Canva exposes Connect APIs, OAuth-based integrations, and an MCP server for AI assistants, none of the evidence describes issuing scoped or least-privilege credentials specifically for an agent (e.g., granular OAuth scopes, per-agent API keys, or restricted permission sets). Private integrations are gated by plan tier (docs-41) rather than granular scoping, and MCP/AI Connector docs discuss connecting an assistant but not credential scoping controls. Missing for 10: explicit scope/permission model for API keys or OAuth tokens issued to agents, documentation of least-privilege credential issuance, and any audit/control mechanism tied to agent-specific access.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “If you're a user wanting to connect your personal AI assistant to Canva's AI Connector, see our Help Center”
   • [claimed-docs] “Private integrations can only be used by your team on a Canva Enterprise plan.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

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

   Canva✓fullprobed8/10

   Canva provides official SDKs (Apps SDK, Connect APIs) plus an OpenAPI description enabling generated client SDKs in various languages, a CLI for app development, and an official MCP server for AI-native integration—covering the core of building against official SDKs. Missing for 10: independent/hands-on developer corroboration beyond first-party docs, and the openapi.json probe returned 404 suggesting the spec isn't trivially discoverable at expected paths.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

9. 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

   Canva—none0/10

   No evidence of any webhook/event-subscription capability in the Canva Connect APIs, MCP server, or other docs — only REST-style APIs, SCIM, audit logs, and MCP tool interactions are described. missing for 10: any mention of webhooks, event subscriptions, or push notifications for state changes.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

   Penpot exposes design data via its MCP server, plugin API, and webhooks so external AI agents can read structured design data and generate outputs (e.g., 'AI agents can easily read and interact with your design files creating high-fidelity artifacts') and the plugin marketplace lists AI tools, but there is no evidence of a built-in, first-party AI feature that proactively surfaces insights or suggestions from a user's own data inside the product itself. Missing for 10: a native in-app AI insight/suggestion feature (vs. only enabling third-party agents via MCP/plugins), and any hands-on/community confirmation that such insights actually work in practice.

   • [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] “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] “Plugins (113+): Community plugin marketplace with accessibility, code, AI, and design system tools.”
   • [claimed-docs] “Get extensive access to objects and properties to enable external rendering, workflow automation, enhanced app functionality, and more.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack shows Canva letting users import external data to drive design generation, bulk creation, and personalized template population (canva-docs-7, canva-docs-8, canva-docs-32), but nothing shows Canva's AI analyzing a user's own data to surface insights or proactive suggestions (e.g., analytics-style recommendations). This is closer to data-driven content generation than 'AI-generated insights and suggestions from my data,' so there is no concrete evidence the described capability exists.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Penpot~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Canva~partialclaimed4/10

   Canva provides integration surfaces (Connect APIs, Apps SDK, Bulk create, Brand Template autofill, MCP server) that let developers or AI assistants trigger Canva actions programmatically, but these are all invoked by an external caller rather than being a built-in autonomous scheduler or background automation engine within Canva itself. Missing for 10: evidence of native scheduled/triggered automations, event-driven workflows, or an 'autopilot' feature that runs without external initiation.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”

   proof ↗⚑ flag

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

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

   Canva~partialclaimed3/10

   Evidence mentions a 'Canva AI' feature only in passing (pasting links to add context to designs) but provides no detail on delegating broader tasks to a built-in assistant; most AI-related evidence instead describes the MCP server that lets *external* AI assistants control Canva, not an assistant embedded within Canva's own UI. missing for 10: documentation of an in-app AI assistant's task scope, examples of users delegating multi-step design tasks to it, and independent/hands-on confirmation of its capabilities.

   • [claimed-docs] “Bring content into Canva AI by pasting links from other platforms to design with more context.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

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

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

   Canva✓fullprobed8/10

   Canva ships an official MCP server explicitly designed so AI assistants can operate Canva via natural language — supporting design generation, editing, discovery, asset/brand management, export, and comments through NL commands, and this is corroborated by a probe confirming the documented endpoint. This directly satisfies the AI-native natural-language operation story, though it relies on third-party AI clients rather than a native in-product NL interface. Missing for 10: independent/hands-on user reports of NL command reliability, and evidence of a first-party conversational interface within Canva itself.

   • [claimed-docs] “give your users access to Canva's design capabilities through natural language, directly from the AI tools they already use”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/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

   Canva—none0/10

   Canva documents an OpenAPI description for its Connect APIs (used for generating client SDKs) but there is no evidence of an interactive API reference with runnable/try-it examples; probes for openapi.json/swagger endpoints returned 404s, suggesting no live interactive console is exposed.

   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

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

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

   Canva✓fullprobed7/10

   Canva's developer docs explicitly state it provides an OpenAPI description of the Connect APIs that can be used with code-generation libraries to produce client SDKs, directly matching the story. Confidence is tempered because the probe couldn't locate the actual spec file at common guessed paths (only generic /openapi.json etc. were tried, not the real documented location), so independent verification of downloadability is thin. Missing for 10: a probed/verified working download URL for the OpenAPI file and independent (non-vendor) confirmation it's actually fetchable.

   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries... to generate client SDKs in var…”
   • [claimed-docs] “You can use this description to generate a client SDK in your preferred language, using a code generation library”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Penpot
   Penpot~partialclaimed4/10

   Penpot has no dedicated 'sandbox' or 'test environment' feature, but its self-hosting capability (docker-compose/Kubernetes deployment, MCP server deployable in your own environment) means an AI-native user could spin up an isolated instance separate from production to test agent workflows. This is an indirect workaround rather than a purpose-built sandbox/staging mode. Missing for 10: an explicit sandbox/staging environment feature, documented separation of test vs production data within the same account, and any first-party guidance on safely testing AI agents against non-production data.

   • [claimed-docs] “Run it in your private cloud, on-premise, or any environment you control.”
   • [claimed-docs] “Deploy the MCP server in your own environment without relying on third-party clouds.”
   • [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…”
   • [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.”

   proof ↗⚑ flag

   Canva—none0/10

   No evidence of a sandbox/test environment separate from production data; Canva's docs describe live APIs, MCP server, and Connect APIs but nothing about a sandbox mode, test accounts, or mock environment for safe experimentation.

   ⚑ flag

4. 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

   Canva—none0/10

   Evidence shows Canva has Connect APIs, an OpenAPI description, SDKs, and an MCP server, but there is no mention anywhere of API versioning scheme or a documented deprecation policy for these APIs; the OpenAPI spec itself isn't even discoverable at expected endpoints (canva-probe-3). missing for 10: explicit API versioning scheme, documented deprecation/sunset policy, changelog or migration guides for breaking changes.

   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   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

   Canva—none0/10

   The evidence pack only covers developer-facing surfaces (Apps SDK, Connect APIs, MCP server, Admin/SCIM/audit APIs) and never mentions Canva's native in-editor AI asset tools like Magic Media image generation, Magic Eraser/background removal, Magic Edit content-aware fill, or Magic Write copy suggestions used directly by a designer inside the editor. Missing for 10: any documentation of built-in Magic Studio-style tools (image generation, background removal, content-aware fill, copy suggestions) operating natively within the Canva editor UI.

   ⚑ 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 Canva
   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

   Canva~partialprobed6/10

   Canva's docs describe design generation and editing from natural language via its MCP server (canva-docs-17, canva-docs-18, canva-docs-28, canva-docs-33), which lets AI assistants create and modify designs from text descriptions and specifications, plus discovery, export, and asset management. However, this capability is delivered through an external MCP integration/AI connector rather than a native in-editor 'Magic Design'-style prompt feature, and there's no independent/hands-on evidence confirming quality of generated mockups. Missing for 10: first-party in-product documentation of native prompt-to-design (e.g., Magic Design) generation, independent hands-on verification of output quality, and confirmation this works without third-party AI tool setup.

   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”
   • [claimed-docs] “Design generation:** Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design discovery:** Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”

   proof ↗⚑ flag

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

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

   Canva✓fullclaimed7/10

   Canva explicitly supports bulk operations via Bulk Create with data import, personalized Brand Template population at scale, and Connect APIs to sync/create many designs/assets programmatically, plus MCP/API access for AI-native automation across many items. Missing for 10: independent/hands-on verification of scale limits, no explicit rate-limit or batch-size documentation, and no third-party confirmation of true 'many items' throughput.

   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Scale design output - generate personalized content in bulk using your own data and visuals.”
   • [claimed-docs] “Import data directly from third-party sources to use for design generation or Bulk create.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “The Canva MCP server enables AI assistants to seamlessly interact with Canva's design capabilities.”

   proof ↗⚑ flag

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

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

   Canva—none0/10

   Canva's evidence covers APIs, apps, MCP server, bulk creation, and integrations, but nothing describes user-defined rule/trigger automation (event-condition-action logic) that fires actions automatically on events. No workflow/automation-rule engine, webhooks-as-triggers, or 'when X happens do Y' capability is documented.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Penpot—none0/10

   Penpot's automation surface (MCP server, plugins, webhooks, API/access tokens) supports event-driven and on-demand integrations, but no evidence anywhere in the pack describes scheduling, cron-like recurring jobs, or timed workflow execution.

   • [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 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] “Penpot enables plenty of AI workflows, from generating editable design structures to connecting product logic, tokens, and implementation.”

   proof ↗⚑ flag

   Canva—none0/10

   The evidence covers Canva's Connect APIs, Apps SDK, MCP server, and bulk creation features, but none of it describes any scheduler, cron-like trigger, or recurring/automated job execution capability. Bulk create and template population are one-shot batch operations, not recurring scheduled workflows.

   ⚑ flag

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

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

   Canva—none0/10

   Evidence shows audit logs tracking user activity, but no documentation of versioning, review, or rollback specifically for automations (Connect API integrations, MCP workflows, or bulk create jobs). There's no mention of automation history, diffing, approval workflows, or reverting automated changes.

   • [claimed-docs] “Use audit logs to track changes made by your team in Canva.”
   • [claimed-docs] “Canva provides audit logs that contain records of user activities in Canva, such as installing a Canva App, exporting a design for download,…”

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

   Canva~partialclaimed5/10

   Evidence confirms Canva supports commenting on designs and even integrating comments into external workflows (canva-docs-9, canva-docs-22, canva-docs-37), implying in-file review is possible, but there is no direct documentation of @mentioning teammates or explicitly 'resolving' comment threads within the editor. missing for 10: explicit documentation of @mention functionality, thread resolution/closing feature, and any first-party or independent confirmation of the full in-app review workflow.

   • [claimed-docs] “Receive and reply to Canva comments from any platform and simplify team communication.”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   proof ↗⚑ flag

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

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

   Canva—none0/10

   The evidence pack focuses entirely on developer APIs, SDKs, MCP servers, and admin/provisioning tools; there is no mention of real-time multi-user editing, live cursors, or simultaneous in-editor collaboration features that are core to this story.

   ⚑ 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

   Canva—none0/10

   Canva's evidence covers Brand Templates, Apps SDK, Connect APIs, and MCP integrations, but nothing describes design tokens/variables (colors, spacing, typography) as reusable, mode-based theme objects applied programmatically across designs — Canva's brand kit concept is not documented as a token/variable system with theme modes.

   ⚑ flag

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

   weight 3 · round to Penpot
   Penpot~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and Brand Templates but contains no mention of a component system with variants, per-instance overrides, or linked source instances (like Figma-style components). Brand Templates allow personalization but are not described as variant-based linked components. Missing for 10: any documentation of a component/variant system, linked instance overrides, or source-of-truth syncing mechanism for design elements.

   ⚑ 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

   Canva~partialclaimed4/10

   Canva offers Brand Kits and Brand Templates that centralize on-brand assets/styles for teams to reuse across designs (canva-docs-15, canva-docs-7, canva-docs-20), which is the closest analog to a shared component library. However, there is no evidence of a true library-linking mechanism where edits to a source style/component automatically or optionally propagate updates to files that already used it, which is the core of the story. missing for 10: documentation of update propagation/versioning when a Brand Template or Brand Kit element changes, evidence of per-instance 'update available' notifications, independent confirmation of this workflow in practice.

   • [claimed-docs] “Make Brand Templates easily accessible, so teams can quickly create and edit on-brand designs.”
   • [claimed-docs] “Automatically personalize and populate Brand Templates with real-time content from your data sources.”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”

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

   Canva—none0/10

   Canva's developer docs cover Apps SDK, Connect APIs, MCP server, and CLI for building integrations, but none of the evidence describes design-to-code output or component-to-code mappings that map a Canva design to shippable UI code (e.g., React/CSS export) as design tools like Figma do.

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [probe] “official MCP server documented at https://www.canva.dev/docs/mcp/”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

   proof ↗⚑ flag

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

   weight 3 · round to Penpot
   Penpot~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ 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

   Canva~partialclaimed5/10

   Canva offers substantial API surface (Connect APIs, Apps SDK, SCIM, Admin API, MCP server) covering design creation, editing, export, comments, and asset management, but this is a curated set of endpoints rather than full parity with the UI editor's rich manual design capabilities (e.g. free-form drag-and-drop editing, most granular design tools). No evidence confirms full UI-API parity; the docs describe specific supported operations, not a claim of complete equivalence. Missing for 10: explicit parity claim or evidence that every UI editing action (e.g. fine-grained manual layout, all effects/filters) is API-accessible, and independent verification of coverage limits.

   • [claimed-docs] “Use the Canva Connect APIs to integrate Canva capabilities into your platform or your users' workflow.”
   • [claimed-docs] “Design generation: Create designs programmatically from text descriptions and specifications”
   • [claimed-docs] “Design editing: Apply targeted modifications to existing designs through natural language commands”
   • [claimed-docs] “Design discovery: Search and retrieve designs, pages, and folders from your design library”
   • [claimed-docs] “Asset and brand management: Upload and organize assets, manage folders, and access brand kits and templates”
   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Collaborative workflows: Add comments to designs and integrate feedback loops directly into your workflows”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”

   proof ↗⚑ flag

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

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

   Canva~partialclaimed4/10

   Canva supports exporting individual designs in open, standard formats (PDF, PNG, JPG, PPTX, MP4) via both the Connect API and the MCP server, giving users a way to pull their design content out in interoperable formats. However there is no evidence of a comprehensive account-level data export (brand kits, comments, team assets, settings, history) or a documented 'export all my data' / account deletion-and-portability feature that would let an AI-native user fully leave with everything intact. missing for 10: bulk/account-wide data export, documented data portability or GDPR-style export tool, evidence of exporting non-design data (comments, brand assets, admin/audit data) in open formats.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “You can use the Connect APIs to create web app integrations that create and sync assets, designs, comments, and more.”

   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

   Canva—none0/10

   Canva is closed-source SaaS; the evidence pack only covers APIs, SDKs, MCP server, and developer docs — none of it indicates any open-license availability of Canva's own product source code.

   ⚑ 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

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Plugins

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

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

   Canva✓fullprobed8/10

   Canva provides a documented Apps SDK for building editor extensions, a CLI for creating/managing apps, and distribution via public Apps Marketplace or private team sharing, matching the developer story closely. missing for 10: independent/hands-on corroboration of typings quality and sample completeness, and a working OpenAPI/typings endpoint (probe found openapi.json paths returning 404).

   • [claimed-docs] “Use the Canva Apps SDK to bring new design and editing experiences into the Canva editor.”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [claimed-docs] “You can then either distribute the app publicly via the Apps Marketplace, or share it privately with members of your team.”
   • [claimed-docs] “Team apps are created solely for a team using Canva, such as an app created to integrate into a specific system.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   proof ↗⚑ flag

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

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

   Canva~partialprobed6/10

   Canva has a real extensibility ecosystem: the Apps SDK/CLI for building apps, an Apps Marketplace for public distribution, and team-private app sharing — directly supporting icon/data/accessibility-style plugins built by third parties. However, evidence is entirely first-party docs describing the SDK/marketplace mechanics; there's no independent evidence of marketplace size, breadth of existing third-party plugins (icons, accessibility checkers, data fillers), or community adoption. Missing for 10: independent verification of marketplace scale/quality, concrete examples of third-party apps in categories named in the story, user reviews or hands-on discovery of the marketplace.

   • [claimed-docs] “You can use the Apps SDK to create apps that import content into Canva, add elements to a user's design, automate common design tasks, and m…”
   • [claimed-docs] “You can then either distribute the app publicly via the Apps Marketplace, or share it privately with members of your team.”
   • [claimed-docs] “Make apps for your team and choose who can use them.”
   • [claimed-docs] “Leverage a command line tool designed for creating and managing Canva apps.”
   • [claimed-docs] “Team apps are created solely for a team using Canva, such as an app created to integrate into a specific system.”
   • [claimed-docs] “Learn how you can turn your app into a business.”
   • [probe] “official CLI documented at https://www.canva.dev/docs/apps/quickstart/”

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

   Canva—none0/10

   The evidence pack is entirely developer/API documentation (Connect APIs, Apps SDK, MCP, SCIM, Admin API) and contains no pricing page, plan comparison, seat-type breakdown, or AI-feature gating disclosure that a procurement-focused product manager would need. Only one mention ('Private integrations can only be used by your team on a Canva Enterprise plan') hints at plan gating but is far from a published pricing/tier matrix.

   • [claimed-docs] “Private integrations can only be used by your team on a Canva Enterprise plan.”

   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

   Canva—none0/10

   The evidence pack is entirely developer/API-focused (Connect APIs, Apps SDK, MCP server, SCIM, audit logs, admin API) and contains nothing about the consumer free-tier editor, its feature set, or free collaboration capabilities; one entry even implies enterprise-only integrations. No evidence supports or refutes what the free tier includes for a designer doing real design work.

   ⚑ flag

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

   weight 2 · round to Penpot
   Penpot✓fullclaimed7/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   No evidence in the pack mentions data residency, regional storage options, or location controls for Canva data; documentation covers APIs, SDKs, audit logs, and provisioning but not data residency/region choice.

   ⚑ flag

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

   weight 3 · round to Penpot
   Penpot~partialclaimed6/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack contains only Canva developer docs about APIs, SDKs, MCP servers, and admin/audit tools — nothing addresses AI training data usage policies or opt-out controls for user content. Missing for 10: any documentation on AI training data policy, opt-out settings, or privacy controls related to model training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Penpot
   Penpot~partialclaimed4/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   Evidence covers audit logs, SCIM provisioning, and admin/team management APIs, but nothing addresses data retention policies or user-initiated data deletion controls for AI-native usage (e.g., MCP/AI connector data handling, deletion of AI-processed content, retention settings).

   ⚑ flag

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

   weight 2 · round drawn
   Penpot—none0/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings for AI-native users; documentation covers APIs, SDKs, MCP server, audit logs, and provisioning but nothing about disabling telemetry collection.

   ⚑ flag

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

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

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of interactive prototyping capabilities such as animated state transitions, conditional logic, variables, or scroll-triggered effects within Canva designs. This is a fair axis for a design tool to be judged on, but nothing in the pack shows Canva delivers it.

   ⚑ 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

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

Canvas

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

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Canva—none0/10

   The evidence pack covers Canva's APIs, SDKs, MCP server, and admin/integration tooling, but contains no mention of responsive frames, auto layout, constraints, or grid-based resizing behavior akin to real UI flex layouts within the design editor itself. Design resizing mentioned (canva-docs-6, canva-docs-16) refers to static output resizing to new fixed dimensions, not dynamic responsive layout behavior.

   ⚑ flag

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

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

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and automation/integration features, but contains no mention of pen/path tools, boolean operations, or precision alignment controls for vector editing. Canva is a template-driven design tool, so this axis is fair to ask, but nothing in the evidence supports professional vector-editing capability.

   ⚑ flag

Files

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

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

   Canva~partialclaimed4/10

   Canva's docs confirm multi-format export (PDF, PNG, JPG, PPTX, MP4) and automatic resizing to new dimensions/aspect ratios, covering the basic 'PNG, SVG, PDF, and more' export need, but there is no evidence of SVG export, per-layer export presets, or slice-based export controls akin to design-tool layer/slice workflows. missing for 10: SVG export support, per-layer export presets, and slice/scale export tooling.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Design export:** Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “Automatically create resized versions of designs in new dimensions, formats, or aspect ratios.”
   • [claimed-docs] “Canva Pro and above: Design resizing to new dimensions”

   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

   Canva—none0/10

   Evidence shows only APIs (Connect API, Apps SDK, MCP) and export formats (PDF/PNG/PPTX/etc.) for integration, but no documented open native design file format — Canva's underlying .canva design representation itself remains proprietary and undocumented; users must go through the vendor's own APIs/exports to get data out, not a portable open format usable in other tools without Canva's platform.

   • [claimed-docs] “Design export: Generate exports in multiple formats (PDF, PNG, JPG, PPTX, MP4, and so on) and resize designs for different channels”
   • [claimed-docs] “The Canva Connect APIs let you integrate Canva's capabilities into your own web apps and platforms.”
   • [claimed-docs] “Canva provides an OpenAPI description of the Connect APIs. You can use this with code generation libraries...to generate client SDKs in vari…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.canva.dev/openapi.json, https://www.canva.dev/swagger.json, https://www.canva.dev/api/op…”

   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

   Canva—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

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

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

   Canva—none0/10

   The evidence pack covers Canva's developer APIs, SDKs, MCP server, and admin/audit features, but contains no mention of file version history, naming milestones, comparing versions, or restoring earlier states of a design.

   ⚑ flag