Verdict
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.
An image and video API for real-time resizing, compression, and format conversion via URL parameters, built for developers at ecommerce, media, and agency teams.
A quote-only enterprise DAM (formerly Widen) built on configurable metadata and external sharing portals, for organisations already standardised on the Acquia stack.
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
Yes
Yes
No
Yes
Billed on
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.
Consumption-based credits, sold in monthly tiers ($25–$500/mo self-serve, custom above that). Credits are spent on Management (2 credits/GB/month for stored assets), Delivery (1 credit/GB bandwidth), and Transformation (variable by operation). Per-credit rate drops as plan tier rises ($0.25 down to $0.12, monthly billing; slightly cheaper on annual commitment). Each plan also states an implied storage/bandwidth cap in GB.
Organisation size, user count, storage volume and feature set
Subscription per user per year, cheaper at volume
Deployment
Cloud
Cloud
Cloud
On-premise, Cloud
Free plan
No
No
No
Yes
Free trial
No
No
Yes
No
Transparency index
Not checked
Not checked
20%
80%
Most common complaint
Not checked
Not checked
Cost depends on four variables at once, none of them priced publicly
It is a file platform with DAM features rather than a DAM: asset-level metadata and rights are thinner