Penpot vs Framer

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

   Framer✓fullclaimed8/10

   Framer documents a write-capable external agent connection (Claude Code, Cursor, Codex) that can create/update/delete CMS items and modify canvas/components, backed by branching for safe review, plus a plugin surface and Server API for programmatic site automation. Missing for 10: independent/hands-on verification of the external-agent write capability and no public OpenAPI/formal API schema was found by the probe.

   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   Penpot~partialprobed5/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Evidence covers AI agents editing designs, CMS, and publishing via a Server API and external-agent connections, but nothing documents a programmatic render/export surface for screenshots, images, or production-format exports (no export/render API endpoints, and probes for OpenAPI specs all 404).

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

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

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

   Framer~partialclaimed7/10

   Framer explicitly markets a native 'External Agent' connection (explicitly positioned as replacing a separate MCP server) that gives coding agents like Claude Code, Cursor, and Codex direct access to canvas, components, CMS, and project context, including read/write CMS operations and branch-based change tracking. This closely matches the story's intent of pulling design context to implement changes, but the specific mention of 'screenshots' and 'variables' from the story isn't explicitly evidenced, and all evidence is first-party docs with no independent/hands-on corroboration of the external agent workflow. Missing for 10: explicit support for screenshots/variables extraction, independent developer confirmation of the external-agent integration working as described.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”

   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

   Framer✓fullprobed8/10

   A direct probe confirms Framer serves a live llms.txt file (HTTP 200) with structured content describing the product and linking to migration/agent docs, and Framer's own docs explicitly reference this file's content, giving concrete first-party evidence an AI agent can be pointed at it. missing for 10: independent/third-party confirmation that agents successfully consume this llms.txt in practice, and broader agent-oriented doc coverage beyond this single file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.framer.com/llms.txt # Framer > Framer is an AI website builder for designers and teams. Generate ed…”
   • [claimed-docs] “Switch to Framer](https://www.framer.com/switch/?md): Migration from another builder.”
   • [claimed-docs] “Framer allows you to host static files directly on your site or custom domain. This feature is available on the **Pro**, **Enterprise**, and…”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   Penpot~partialclaimed5/10

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

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

   proof ↗⚑ flag

   Framer~partialprobed3/10

   Framer advertises a Server API to 'automate publishing' and integrate with external products/agents, which implies some programmatic/headless control, but there is no documented CLI, headless mode, or CI-specific workflow, and probes show no OpenAPI/API spec is publicly discoverable (404s). Missing for 10: concrete CI/headless setup docs, API reference/spec, and evidence of automated pipeline usage beyond marketing blurbs.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   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

   Framer—none0/10

   Framer explicitly states it does not use or require MCP: 'Framer doesn't require a separate MCP server... without manual MCP setup' (framer-docs-34). Its actual capability runs in the opposite direction — external agents like Claude Code/Cursor connect INTO Framer to use Framer's canvas/CMS as their tool, not Framer consuming external MCP servers' tools. No evidence exists of Framer acting as an MCP client that plugs in third-party MCP servers.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

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

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

   Framer—none0/10

   Framer explicitly states it does not offer an MCP server, instead providing a proprietary 'External Agent connection' as an alternative to MCP (framer-docs-34). Since the story specifically asks for an official MCP server, and Framer's own docs assert this is unnecessary and unsupported by design, there is no evidence of an actual MCP server implementation.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

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

   Framer—none0/10

   Evidence shows Framer offers a Server API, plugins, and 'External Agent' connections for tools like Claude Code/Cursor/Codex, but nowhere does it mention an official Framer CLI tool for AI-native workflows.

   ⚑ flag

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

   weight 3 · round to Penpot
   Penpot✓fullprobed8/10

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

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

   proof ↗⚑ flag

   Framer~partialprobed6/10

   Framer documents a Server API for automation/publishing and CMS API access, and explicitly supports external AI agents (Claude Code, Cursor, Codex) reading/writing CMS collections via a documented connection flow (framer-docs-5,17,30,39,40,18,24,34). However, probes could not locate any formal API reference/spec (openapi.json/swagger 404s) or detailed endpoint documentation, and there's no independent/community corroboration of developers actually using the Server API. Missing for 10: a discoverable formal API reference/spec, authentication/rate-limit details, and independent developer testimonials confirming API usability.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   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

   Framer—none0/10

   Framer documents a Server API and an 'External Agent' connection that lets tools like Claude Code or Cursor read/write CMS data and canvas content, with branching as a safety net for undoing changes — but nothing describes issuing scoped, least-privilege, or permission-limited API credentials/tokens for agents. Missing for 10: any mention of API key scopes, granular permission levels, token expiration/rotation, or role-based credential issuance for agent access.

   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Penpot
   Penpot✓fullprobed7/10

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

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

   proof ↗⚑ flag

   Framer~partialprobed6/10

   Framer documents a Server API, plugin SDK, code components/overrides, and an external agent connection for building integrations against official interfaces, but there's no discoverable OpenAPI spec (probe found 404s across candidate paths) and no independent/hands-on developer corroboration of building against these SDKs. missing for 10: publicly discoverable API reference/OpenAPI spec, independent developer corroboration, SDK versioning/language support details.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   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

   Framer—none0/10

   Evidence covers Framer's Server API, external agent connections, and plugins, but there is no mention of webhooks or event subscription mechanisms anywhere in the docs or probes; OpenAPI probe also returned 404s with no webhook spec found.

   ⚑ 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

   Framer~partialclaimed4/10

   Framer's AI agent can restructure and suggest layout changes based on generic 'conversion best practices' (framer-docs-31/38) and manages/organizes CMS data (framer-docs-8/46), which is adjacent to data-driven suggestions, but there is no evidence of the agent analyzing a user's actual site/traffic data to surface analytical insights (e.g., performance, SEO, or visitor-behavior insights) — it is generative/design assistance rather than data-insight generation. Missing for 10: evidence of analytics-based insight generation, data pattern analysis, or dashboards summarizing user's own data trends.

   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ, and make sure every s…”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”

   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

   Framer~partialclaimed4/10

   Framer offers a Server API to 'automate publishing' and lets external agents (Claude Code, Cursor, Codex) connect to read/write CMS and canvas content, which could be wired into autonomous workflows, but all documented agent interactions (framer-docs-6/7/26) are conversational/on-demand rather than scheduled or self-running background automations. There's no evidence of triggers, schedules, or persistent background jobs — only API/connection primitives a developer would need to build such automation themselves. missing for 10: evidence of scheduled/triggered background jobs, autonomous run history or logs, native workflow/automation builder distinct from on-demand AI agent editing.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

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

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

   Framer✓fullclaimed7/10

   Framer ships multiple built-in AI agents (design agent, CMS agent, AI website generator) that users can delegate tasks to directly inside the product via natural-language prompts (e.g. 'make responsive', 'switch to dark mode', CMS setup) as shown in framer-docs-6,7,8,26,42,43,44,45,46. Missing for 10: independent/hands-on user reports specifically validating the built-in AI assistant's reliability and quality (community evidence available only covers older, unrelated Framer features like animations).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”

   proof ↗⚑ flag

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

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

   Framer✓fullclaimed8/10

   Framer's docs show extensive natural-language operation: the built-in AI agent creates pages/sections/copy from prompts, restyles sites ('switch to dark mode', 'use Fraunces/Inter'), reorganizes layouts, and makes sites responsive purely from described intent, plus a CMS agent and external-agent integration (Claude Code/Cursor/Codex) that reads/writes CMS and canvas content via natural language, with branch-based safety for changes. missing for 10: independent/hands-on third-party corroboration of the AI/CMS agent actually working as described (community evidence only covers older non-AI Framer features).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”

   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

   Framer—none0/10

   Framer documents a Server API, Plugins API, and Code Components, but nothing shows an interactive API reference with runnable/try-it examples; probe evidence explicitly found no OpenAPI/swagger spec (404s at all candidate paths), suggesting no such interactive reference exists.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Penpot—none0/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Framer offers a Server API and llms.txt, but the probe explicitly found no OpenAPI/swagger spec at any standard location, and no docs mention a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”

   proof ↗⚑ flag

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

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

   Framer~partialclaimed6/10

   Framer offers staging environments on a framer.app domain and automatic branching so AI agent changes happen in isolation from the live/main project, which functions as a sandbox against production data (framer-docs-10, framer-docs-11, framer-docs-25, framer-docs-36). However, this is framed around publishing workflow rather than an explicit 'sandbox for AI testing' concept, and there's no independent/hands-on verification of how well this isolation holds up in practice. missing for 10: independent corroboration of branch/staging isolation, explicit documentation framing this as an AI-testing sandbox rather than a publishing safety net, and detail on whether CMS data changes by agents are also fully isolated from production before merge.

   • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”

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

   Framer—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI specs returned 404s and the Server/Fetch API docs mention no versioning or deprecation terms.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

Ai

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

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

   Framer~partialclaimed3/10

   Framer's AI agent can generate pages, sections, copy, and visuals (framer-docs-6, framer-docs-26, framer-docs-42) and adjust layout/typography, which touches copy suggestions and some visual generation, but there is no evidence of dedicated asset-chore tools like image generation, background removal, or content-aware fill inside the editor. missing for 10: dedicated image generation tool, background removal feature, content-aware fill capability, hands-on/independent verification of these specific asset tools.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”

   proof ↗⚑ flag

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

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

   Framer✓fullclaimed8/10

   Framer's docs describe a native AI agent that generates editable pages, sections, copy, and visuals from prompts, with examples of full mockup edits (typography, grid layouts, brand colors, dark mode, responsive breakpoints, image-based starting points), and lets designers keep refining in canvas after generation. This directly matches the story of prompt-driven first drafts/layouts/mockups, though evidence is entirely vendor-sourced with no independent hands-on verification of AI-generation quality — missing for 10: independent/hands-on confirmation that generated designs are production-quality, and any documented limitations of the AI design agent.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”

   proof ↗⚑ flag

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

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

   Framer~partialclaimed6/10

   Framer docs show AI-agent driven bulk operations such as site-wide typography/color/theme changes across all pages (framer-docs-19,27,37), CSV bulk import of CMS collections with row-level linking (framer-docs-9,21), and external agents able to create/update/delete many CMS items via API (framer-docs-18,24,35). This supports bulk operations across many items in CMS/design contexts, but there's no documentation of scale limits, batch API endpoints, or performance at large volumes. Missing for 10: explicit bulk/batch API documentation with scale guarantees, independent verification of bulk operations succeeding at scale, and rate-limit/performance details.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”

   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

   Framer—none0/10

   Evidence shows Framer's API, plugins, and AI agents that can be manually invoked to modify a site, and an API to 'automate publishing,' but nothing describes a rule engine or event-trigger system where a user defines 'when X happens, do Y' automation. missing for 10: any event-trigger/rule definition mechanism, conditional logic, or workflow automation builder within Framer.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

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

   Framer—none0/10

   Framer's evidence covers AI agents editing sites, CMS, publishing, plugins, and APIs, but there is no mention of scheduling recurring jobs, cron-like automation, or workflow triggers of any kind. Automate publishing via API is a manual/programmatic action, not a recurring scheduled job.

   ⚑ flag

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

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

   Framer✓fullclaimed8/10

   Framer documents automatic version history with instant rollback, plus branching that isolates every external-agent change so it can be reviewed, undone, or merged — directly matching version/review/rollback for automations run by AI agents. Missing for 10: independent/hands-on confirmation of rollback and branch-merge workflows in practice, and detail on granular diff/review UI beyond marketing docs.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”

   proof ↗⚑ flag

Collaboration

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

   weight 2 · round to Penpot
   Penpot~partialclaimed2/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Evidence covers branching, version history, AI agents, CMS, and plugins, but nothing about in-file commenting, @mentions of teammates, or resolving comment threads for design review. Missing for 10: any mention of a commenting feature, mention/notification system, or thread resolution workflow.

   ⚑ 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

   Framer—none0/10

   The evidence pack includes docs on branching, version history, and staging (framer-docs-11, framer-docs-47) but contains no mention of real-time multiplayer editing, live cursors, or instant sync between simultaneous editors — the actual claim in the story. Missing for 10: any documentation of live cursors, simultaneous multi-user canvas editing, or real-time presence indicators.

   ⚑ 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

   Framer—none0/10

   Evidence shows Framer's AI agent can restyle colors/typography/light-dark mode on request (framer-docs-27, framer-docs-37, framer-docs-19), but there is no documentation of an actual design-token or variables system with reusable modes/themes applied consistently across designs, akin to Figma variables. Missing for 10: token/variable definition, mode-based theme switching infrastructure, cross-file/theme propagation evidence.

   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”

   proof ↗⚑ flag

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

   weight 3 · round to Penpot
   Penpot~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Framer~partialclaimed3/10

   Evidence only touches tangentially on component reuse — Code Components with visual controls and Code Overrides (HOCs to modify Layer/Component properties) hint at reusable, overridable components, but nothing explicitly describes variants or per-instance overrides that stay linked to a master component/source as in a design-system workflow. Missing for 10: explicit documentation of component 'variants', proof that per-instance overrides remain linked/syncable to the source component, and any hands-on/community confirmation of this specific workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   Penpot~partialcommunity5/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Framer's evidence covers code components, plugins, branching, and CMS collections within a single project, but there is no documentation of a shared/team library mechanism that publishes components or styles across separate files or projects with controlled update propagation (the Figma-style library model). Missing for 10: any mention of a cross-project component/style library, library publishing workflow, or update-notification/accept-update mechanism.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”

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

   Framer~partialcommunity7/10

   Framer supports genuine dev-facing code integration: Code Components (custom React components with visual controls), Code Overrides (HOCs), a Server API, and native external-agent access letting Claude Code/Cursor/Codex read/write the live project and CMS with branch-based review before merge. Community evidence corroborates that Framer's React-based model lets designers hand off working code to developers. However this is not a classic 'export design to code' pipeline (no Figma-style code export or OpenAPI-documented flow was found), and independent verification is thin/dated. missing for 10: independent hands-on proof of shipping exported production code, more recent community validation of the external-agent/dev handoff workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”

   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

   Framer—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 to Framer
   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

   Framer~partialprobed6/10

   Framer exposes a Server API, external-agent connections (Claude Code/Cursor/Codex) with read/write CMS access, branching for review, and a plugin system that covers many editor actions (framer-docs-5,17,18,24,34,35,36) — a real, substantive API surface for automation. But there's no evidence of full UI/API parity: no OpenAPI/spec discoverable (framer-probe-3 shows 404s across candidate spec paths), and the docs describe specific supported actions (CMS CRUD, canvas edits via agent, publishing) rather than a claim that literally everything achievable in the UI (e.g. fine-grained styling, animation editing, plugin marketplace management) is scriptable via API. Missing for 10: a documented comprehensive API/OpenAPI reference proving parity, explicit vendor claim of 'anything in UI = anything via API', and independent/hands-on verification of that parity.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

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

   weight 3 · round to Penpot
   Penpot!disputedcontradicted5/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Evidence shows Framer offers a Server API, CMS API, and CSV import for content, but nothing indicates the ability to export a full site (design, code, CMS data) into open, portable formats for migration away from Framer; only 'migrate to Framer' flows are documented, not exit/export paths.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

   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

   Framer—none0/10

   Framer is closed-source proprietary SaaS; no evidence pack item mentions an open-license source availability, and this is a mainstream commercial product with no indication of open-sourcing its codebase.

   ⚑ 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

   Framer—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 Framer
   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

   Framer~partialclaimed6/10

   Framer documents a Plugins API for building editor extensions (small apps that interact with the Editor/CMS, insert layers/images/code components) with a dedicated developer docs section, plus adjacent APIs like Code Components and Server API. However, the evidence pack doesn't show explicit TypeScript typings references or concrete code samples/SDK repo, and there's no distribution/marketplace mechanism described. missing for 10: explicit typings documentation, concrete code samples/starter templates, and a distribution/marketplace mechanism for sharing plugins.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   Penpot~partialcommunity6/10

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

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

   proof ↗⚑ flag

   Framer~partialclaimed5/10

   Framer's docs confirm a plugin system where developers build 'small apps' that can interact with the editor and CMS (inserting images, layers, code components, modifying canvas), which is the technical foundation for a plugin ecosystem. However, the evidence never mentions a marketplace, community size, or specific plugin categories like icon packs, data fillers, or accessibility checkers as the story asks. Missing for 10: evidence of an actual marketplace/directory, plugin discovery UX, and named example plugins matching icons/data/accessibility use cases.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”

   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

   Framer—none0/10

   The evidence pack contains no pricing page, plan tiers, seat types, or AI-feature gating details — only one mention that a static-file hosting feature is limited to Pro/Enterprise plans, which does not constitute published plan/seat/AI-gating clarity. No pricing comparison table or plan documentation is present anywhere in the pack.

   ⚑ 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

   Framer—none0/10

   The evidence pack contains no mention of Framer's free tier, its editor limitations, or free-tier collaboration features; all docs focus on AI agents, CMS, publishing, and plugins. No pricing or free-plan details are cited anywhere in the pack, so there is no basis to confirm the free tier supports real design work or collaboration.

   ⚑ 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

   Framer—none0/10

   No evidence in the pack addresses data residency, region selection, or data storage location controls for Framer; all evidence concerns AI agents, CMS, plugins, and publishing features unrelated to data residency.

   ⚑ 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

   Framer—none0/10

   No evidence in the pack addresses data usage for AI training, opt-out controls, or any privacy policy statement regarding training data; all evidence concerns AI agent features, plugins, and site publishing.

   ⚑ 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

   Framer—none0/10

   The evidence pack covers Framer's AI agent, plugins, API, CMS, and version control/branching features, but contains no mention of data retention policies, data deletion controls, or privacy/compliance settings for AI-native workflows. Missing for 10: any documentation on data retention periods, user-initiated data deletion, or privacy controls specific to AI agent interactions.

   ⚑ 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

   Framer—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for Framer's AI features or platform; all documentation covers unrelated capabilities (agents, CMS, plugins, publishing).

   ⚑ flag

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

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

   Framer!disputedcontradicted6/10

   Framer's docs and community evidence confirm rich prototyping behavior — animated menus, carousels, code overrides, data-driven components (docs-45, docs-32, comm-4, comm-5) — but hands-on reports document concrete failures that undercut the 'feels like the real product' promise: animations distort during size/geometry changes, performance is inconsistent (60fps then chugging) on the same device, and users found Framer 'falls through' vs alternatives like react-spring when chaining multiple interactive animated nodes (comm-6, comm-7, comm-9). Missing for 10: independent verification that these animation glitches are resolved, and evidence of robust variable/conditional-logic support beyond CMS data binding.

   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Fetch Building API endpoints that designers can use on their Framer sites without code.”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”
   • [community] “As a ux designer... this is quite an interesting tool if you design software. It gives a nice blend between design and code. Your prototypes…”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [community] “I feel react-spring is better suited for the job... tried them both with r3f, i think it's just about API design and framer starts to fall t…”

   proof ↗⚑ flag

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

   weight 2 · round to Penpot
   Penpot✓fullcommunity6/10

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

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

   proof ↗⚑ flag

   Framer~partialcommunity4/10

   Evidence shows Framer supports animations/transitions (community: 'great for more advanced prototyping needs w/ animations/transitions', 'declarative approach to creating nice animations') and AI-driven interactive elements like 'sticky navbars, animated menus, interactive carousels' handled via prompts, but there is no explicit documentation of screen-to-screen click triggers or overlay linking (the core Figma-style prototyping flow), and community reports flag animation performance/rendering glitches that undercut confidence. missing for 10: explicit docs on multi-screen click triggers, overlay/modal linking, and independent confirmation of a smooth no-code prototyping flow.

   • [community] “Framer is great for more advanced prototyping needs w/ animations/transitions/etc, but Adobe XD is pretty good and fast for many needs, and …”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”

   proof ↗⚑ flag

Canvas

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

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

   Framer~partialclaimed6/10

   Framer's docs describe breakpoint-based responsive adaptation ('adapts your layouts across breakpoints, adjusting stacks, type sizes, spacing, and image crops') and general layout refinement (breakpoints, spacing) via its AI agent and canvas, which implies auto-layout/stack-style responsive behavior. However, there's no explicit documentation of manual constraints or grid systems, and no independent/hands-on corroboration of responsive resizing quality. missing for 10: explicit docs on constraints/grid systems, independent verification of resize fidelity across breakpoints, non-AI-agent manual workflow evidence.

   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”

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

   Framer—none0/10

   The evidence pack is entirely about Framer's AI agents, CMS, publishing, plugins, and developer API — nothing addresses classic vector tools like pen/path editing, boolean operations, or precise alignment guides. No documentation or community evidence confirms these professional vector-editing capabilities.

   ⚑ flag

Files

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

   weight 2 · round drawn
   Penpot—none0/10

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

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

   proof ↗⚑ flag

   Framer—none0/10

   Framer is a website-builder/publishing tool, not a design/prototyping tool with layer-based asset export; the evidence pack contains no mention of PNG/SVG/PDF export, per-layer presets, scales, or slices — these are Figma/Sketch-style export features absent from Framer's docs.

   ⚑ 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

   Framer—none0/10

   The evidence pack covers Framer's APIs, plugins, CMS, and AI agent integrations, but contains no mention of an open or documented native file format that would let designs be opened, edited, or version-controlled by external tools outside Framer's own editor/publishing pipeline. Version history, branching, and staging are all Framer-hosted features, not a portable file format.

   ⚑ 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

   Framer—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 to Framer
   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

   Framer~partialclaimed5/10

   Framer's docs confirm automatic version history with one-click restore of any prior version (framer-docs-12, framer-docs-22) and branching to isolate changes (framer-docs-11, framer-docs-47), but there is no evidence of naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: named milestone/checkpoint labeling, version comparison/diff view, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”

   proof ↗⚑ flag