Verdict
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.
An enterprise DAM module within Adobe Experience Manager, for large organizations managing thousands to millions of brand assets across marketing channels.
An image/video optimization and delivery API with a lightweight DAM layered on top, aimed at EU-based teams that want GDPR/France-hosted processing and hands-on vendor support.
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
No
No
Yes
Billed on
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.
No public price list; sales quote required for both packages (Prime and Ultimate). Adobe's own on-premise product description sheet lists separate license metrics per component — AEM Assets itself is licensed 'Per Instance', 'Users' are licensed 'Per User', Brand Portal is licensed 'Per Brand Portal User', and Dynamic Media/Personalized Media are licensed by 'Page Views per month' — so billing is multi-metric and only available via custom quote, not a single flat per-user or per-GB rate.
Quoted per customer
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
Not checked
Not checked
10%
80%
Most common complaint
Not checked
Not checked
Three tiers described by features, none of them priced
It is a file platform with DAM features rather than a DAM: asset-level metadata and rights are thinner