Verdict
An API-first, developer-configurable content platform with DAM features, built for enterprise teams (100+ users) with in-house developers, not a low-code tool for non-technical editors.
A PIM platform with a built-in DAM module, used by manufacturing and ecommerce companies to manage product data and assets; also available as a free open-source Community Edition.
A cloud service for storing, resizing, optimizing and delivering images via API and CDN, aimed at developers building web and mobile apps that handle images at scale.
A self-hosted file-sync and collaboration platform some organisations stretch into asset-library duty; tagging, batch metadata editing and dynamic tag-based collections are still limited or missing.
Price published
No
No
Yes
Yes
Billed on
Quoted per customer
No genuine dollar pricing is published. The vendor's package-comparison page lists four tiers: Community Edition (free, open-source, self-hosted), Growth (SaaS, shown only as "Starting at $0 Annually" with a free-trial CTA — no real recurring price disclosed), Advanced and Premium (both "Call for a quote"). No billing unit (per user, per SKU, per asset, per GB) is stated anywhere on the site for the paid tiers.
Storage ($5 / 100,000 images stored / month), delivery ($1 / 100,000 images delivered / month), and transformations (first 5,000 unique transformations/month free, then $0.50 / 1,000 unique transformations/month). A unique transformation is billed per distinct parameter combination (e.g. same image at 100x100 and 200x200 counts as two). Storage/delivery charges apply only to images hosted in Cloudflare Images; transforming externally-hosted images is billed only under transformations.
Subscription per user per year, cheaper at volume
Deployment
Cloud
Cloud, On-premise
Cloud
On-premise, Cloud
Free plan
No
No
No
Yes
Free trial
No
No
No
No
Transparency index
10%
Not checked
Not checked
80%
Most common complaint
No prices, and no explicit confirmation of on-premise on the product page
Not checked
Not checked
It is a file platform with DAM features rather than a DAM: asset-level metadata and rights are thinner