Marvel

The making itself: vector and layout tools, interactive prototypes, and the shared components, styles and tokens that keep a company's products and materials consistent — judged on what the feature and help pages document, not on showcase images.

0 — A single-purpose editor with no reusable components, no shared styles and no prototyping.

3 — Templates and basic shapes or layouts, with styles saved per file only and prototyping limited to linking screens.

5 — Reusable components and shared styles across files, responsive or auto layout, clickable prototypes with transitions, and team libraries that update where they are used.

8 — A design system managed in the tool: variables or tokens for colour, type and spacing with modes or themes, component variants and properties, prototypes with conditional logic, and library change notes with versions.

10 — The design system is a governed product: library releases versioned and reviewable, token export in a documented format for development, usage analytics per component, and accessibility checks such as contrast built into the editor.

Working on the same files with colleagues, clients and developers: comments and review, permissions for internal and external people, and the handoff that gives engineering measurements, assets and code rather than screenshots.

0 — Files shared as exports or links with no comments, no permissions beyond view or edit, and no developer view.

3 — Real-time co-editing and comments, but external reviewers need a paid seat or full access, and developers get only exported images.

5 — Comments with mentions and resolution, view-only and comment-only access for guests without a paid seat, permissions per file and project, and an inspect mode with measurements, styles and asset export.

8 — Branching or review of changes before they reach the main file, version history with restore, a developer mode that links components to code, an API and plugins documented, and named integrations with issue trackers and code tools.

10 — Handoff is a contract between design and code: component properties mapped to code components, token and asset export automated through the API, an audit log of access and sharing, and external access governed by domain, expiry and admin policy.

Keeping a brand usable and correct across a company: a central library for logos, images and templates, brand guidelines people can find, locked templates that let non-designers produce material, and rights and expiry metadata on every licensed asset.

0 — No shared asset library; logos and images are uploaded per file by whoever needs them.

3 — A shared folder of assets and some templates, but no guidelines, no locking of brand elements and no metadata beyond file names.

5 — A central brand library with logos, colours and fonts, templates with locked elements for non-designers, brand guidelines published in the tool, and tagging and search across assets.

8 — Rights, usage and expiry metadata on assets with warnings or automatic withdrawal on expiry, approval workflows for new assets and template output, version control on assets, and access per team, market or partner.

10 — Brand governance is auditable: every asset carries its licence, owner and permitted use, usage of each asset is tracked across files and channels, distribution to external partners is logged, and the whole library with metadata is exportable in a documented format.

Whether the work can leave: open or documented file formats, export that keeps layers, vectors and components, offline or self-hosted options, and what happens to files after a downgrade, a removed seat or a cancelled contract.

0 — Files exist only in the vendor's cloud in a proprietary format, export is a flat image, and nothing is said about files after cancellation.

3 — Export to PNG, PDF and SVG per frame, but no export of whole files with structure, and files after a downgrade or cancellation addressed only in general terms.

5 — Whole files exportable to a local or documented format, vector and layered export (SVG, PDF) with text kept as text, bulk export of a team's files, and a stated period during which files remain accessible after cancellation.

8 — An open or publicly documented file format, export and import with other tools documented, an API that reads full file structure, files of removed users transferred to the organisation by policy, and a stated deletion timeline after the contract ends.

10 — Portability is built in: an open-source or openly specified format, self-hosting or a local-first option, round-trip export without loss of components and prototypes, and the customer's ownership of all files and their export rights written into the terms.

What the vendor's AI does with the customer's files and what the customer may do with the AI's output: training on customer content and the opt-out, the models and where they run, commercial use of generated images, stock licences and indemnity.

0 — Generative features with no statement on training on customer files, no named models, and no word on whether output may be used commercially.

3 — An AI page that promises responsibility but leaves open whether customer files train models, and output rights are stated only for some features or only in community terms.

5 — Training on customer content excluded or opt-out documented, AI features switchable by an admin for the organisation, model providers named, and commercial use of generated output permitted in the terms.

8 — Training excluded by default for business plans, the processing location of AI features stated, generated content labelled or carrying content credentials, stock and template licences stated per asset type, and an IP indemnity for generated output on a named plan.

10 — AI is governed in writing: a per-feature list of models, providers and locations, admin controls per team and feature, a log of AI use, training exclusion and output ownership in the contract terms, and indemnity and licence limits published in full.

Who the contracting entity is, where design files, brand assets and AI prompts are stored and processed, and which subprocessors touch them. Independently sourced by the sovereignty pipeline.

0 — Non-EU contracting entity, no statement on where files are hosted, and subprocessors unnamed.

3 — EU data residency available only on an enterprise plan or not at all, or the subprocessor list is absent, or AI features send files outside the EU without an explained safeguard.

5 — EU hosting stated for files, a DPA available, but the contracting entity or significant parts of the chain (AI, rendering, support) are non-EU without a stated safeguard.

8 — EU contracting entity, files, assets and backups stored in the EU on named infrastructure, subprocessor list published with locations and purposes, and AI processing location stated.

10 — Sovereign end to end and evidenced: European ownership, EU entity, every hosting, AI and support subprocessor European or optional, self-hosting or a European cloud offered, and certifications published.

Whether a buyer can compute the annual cost for their team from public pages alone — which seat types exist and what each may do, how viewers and guests are billed, how seats are added and trued up, AI credits, and the plan where SSO, admin controls and brand features begin.

0 — No public prices at all; every plan is a sales conversation.

3 — A per-seat price for an entry plan, but the seat types, the billing of guests and reviewers, and the plan needed for business features are unclear.

5 — Plans priced per seat type with their main features, but at least one commonly incurred cost (seat upgrades on request, AI credits, storage, brand or SSO add-ons) is missing or "on request".

8 — Every plan and seat type priced, free viewers and guests stated with their limits, how and when added seats are billed explained, AI credits and storage priced or included explicitly, and the plan that unlocks SSO and admin controls named.

10 — Complete cost computability: annual cost derivable for a given mix of editors, viewers and guests, true-up and auto-upgrade rules published, every add-on priced publicly, and contract term, renewal and downgrade conditions stated.