Acquia DAM (Widen) helps brands manage and distribute assets across teams, tools, and channels. A configurable metadata schema provides business-specific search and workflow capabilities. Plus, AI-powered auto tagging makes assets instantly findable. Content can be synced across systems using the API or pre-built integrations with over 50 tools, from creative suites to project management. Product-based companies can use Acquia DAM to build a unique 360º view of their product content. It…
N/A
Perforce P4
Score 7.7 out of 10
N/A
Perforce P4 (formerly Helix Core) is the company's version control and peer code review solution. Perforce offers add-on products for code review for free, and Git support products.
N/A
Pricing
Acquia DAM (Widen)
Perforce P4
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Acquia DAM (Widen)
Perforce P4
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
Guided or full-service implementation options and annual subscriptions based on capabilities required. Workgroup and unlimited user options available. Storage with Amazon Web Services.
Professional services available for strategy consulting, change management, administration services, design services, and managed integrations.
—
More Pricing Information
Community Pulse
Acquia DAM (Widen)
Perforce P4
Considered Both Products
Acquia DAM (Widen)
Verified User
Anonymous
Chose Acquia DAM (Widen)
There are some benefits like friendlier UI but it is not currently implemented with my organization.
We started with the Widen system but ended up switching to BrandFolder. BrandFolder had the consistent interface across internal and external platforms. It was easier to use and search for assets for our internal team and brand partners. I preferred the Widen system's ability …
We've used file-sharing platforms to share assets, but without any controls, it's a relative free-for-all. There's no control over which assets get used where; it's often dependent on one person's account hosting, or shared assets get deleted or moved if more than one person is …
While Canto Cumulus is a reputable DAM, users cite potential drawbacks such as a complex interface, customization challenges, integration limitations, scalability concerns, and reported issues with support responsiveness. These aspects should be considered based on specific …
They seem to do much of the same but we use Sharepoint for internal use only and there is higher security on our Sharepoint so access by external vendors could be problematic at times.
We decided to stick with Acquia DAM (Widen) in the short term but will be reviewing the options this or next year to better integrate with Social, Web, and Creative team needs. We use Sitecore for all our web services, so it needs to be compatible with that, Social also needs …
They are completely different. Dropbox is better for cloud storage whereas Widen is more assets library driven. They are both faily easy to share content through but Widen is set-up better visually.
Google Drive offers nowhere near the functionality that Acquia DAM (Widen) does (this is obviously like comparing apples to oranges because GD is ultimately a storage solution).
I do prefer AWS because it's more simplified and suited to our purposes. But the rest of our company uses Acquia DAM (Widen), so I had to switch. But I'm still pleased with Acquia DAM (Widen), and I love the portal option to create a PDF library.
We previously used the Planning feature in Teams for content flow needs. Acquia DAM (Widen) has exceeded Teams in many ways by improving organization and content flow needs.
Acquia DAM (Widen) had all the features we needed at a price that was not unaffordable. Also, having unlimited users and Admins is something few others have.
Acquia DAM (Widen) feels like a bigger platform to work within. Acquia DAM (Widen) has more options to choose from which allows us to partner with big companies.
Less expensive and more geared to our industry but reasons we went with Acquia DAM (Widen) included: chat support portals Wisconsin based (or it was) Customer service Reviews from other users were very positive
One reason was that we migrated to Acquia Drupal and Acquia DAM (Widen) is the Acquia product that comes with loads of features and seamless integration with Acquia Drupal. Also, Acquia DAM (Widen) aces in other features like granular user management, publishing workflow, …
Well, we use both but Wrike is more of a sharing Software between teams as opposed to Acquia DAM (Widen) that shared content with everyone. I like both for their different functionalities and what they offer in terms of efficiency. I would say that Wrike is faster the layouts …
In my opinion, Perforce Helix Core is on a top level of irritation and anti-user experience. In my experience, I can't do simple things like 1 word file edits, while I have never been confused when using something based on Git.
Git is great, I love Git. But it's not great for dealing with binary assets, even when using git LFS. Locking is not as simple as on perforce. Git presents some problems on using for non-tech people it can get overwhelming and tech people have to come by and help.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that …
My last two jobs used SmartSVN but it required a paid license to use regardless of the number of users. The initial setup for Perforce was much more difficult than SmartSVN. There is a lot of parity between the two software packages even though the terminology can be different. …
Perforce has a better built native visual client that is much simpler to use than Git's. It has a lot of optimizations in the workflow that can execute common patterns during a usual workday. Perforce also has an easier to understand method of presenting merge conflicts and …
Perforce is internally hosted, which makes it quite a bit faster. I found it easier to use that GitHub and Bitbucket, at least in terms of checking out files and creating changelists. GitHub and Bitbucket are much better for smaller teams, as they are cloud hosted, making …
Today's web based software makes them easier to integrate into a development process. Jira with integrated BitBucket as the versioning tool, is ahead of the competition. However for large organizations, Perforce is still a very good choice. GitHub can be used as free tool, but …
Perforce has more features than SVN. However even the simpler tasks in SVN require a degree more technical aptitude with Perforce. Git offers most of the same features, however most of these are only really supported via the command-line in Git, where as most tasks can be …
Perforce is similar to SVN but the SVN has better command line support. Git surpasses both SVN and Perforce because of its flexibility with multiple branches and code review.
Acquia DAM is well suited for large companies that need to organize and control the flow of assets being used by their teams and vendors. It provides much better control than file storage sites like Dropbox, where there's little control over what goes where and almost non-functional search functionality. If you're a smaller company, you may be able to get by or have someone dedicated to doing so, but for larger companies, it really takes a lot of the manual work out of it!
For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.
They offer valuable guidance and educational resources to Administrators
Their I.T. support is knowledgeable and responsive. And friendly!
They build community among Acquia DAM (Widen) Admins
They aren't as salesy and pushy as many of the other DAM Vendors that we considered. I don't feel like they are constantly trying to upsell me or take advantage. I hope this continues to be the case with the acquisition by Acquia.
The AI tagging is not very intuitive; if you upload 100 assets, you have to wait for ages to see if they have been tagged by constantly checking the field views over and over again. It would be good to have an AI tagging manager where you could submit and check tagging status.
For image downloading, it would be good to be able to select an image size rather than an aspect and then adjust the image to the size.
We would have jumped at the chance for SSO or Site Core integration, but the costs were so high it just was not worth it; we could have hired people to do it manually for cheaper.
Acquia DAM (Widen) is changing its pricing model and at this point, we are unsure whether it is a good thing for us or not. While we consider this a robust tool, we will take our time to evaluate the competitors.
We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.
Acquia DAM (Widen) is very intuitive, it does not take extensive training as some tools do to use the tool. Uploading assets, creating portals, collections and sharing are all very simple. Acquia DAM (Widen) also does not force you to fill out all of the metadata. You can fill out as little or as much as you would like.
With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!
In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.
There have been a couple of rare instance where after I uploaded an asset, I was unable to rename it, or after uploading it it took a while before it actually appeared and can be viewed in the DAM.
The Acquia DAM support team is fantastic! Not only do we have an amazing customer support contact, the regular chat support is a great resource. Our CSM schedules meetings with our team regularly to ensure that we're meeting our goals. And the general support is great at responding quickly!
I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.
The training was very thorough. The recordings for all our traning sessions were provided to us so that we could go back and review. Our trainer was always available for follow up questions. Our trainer shared a spreadsheet with us as a checklist for all things that needed to be done to ensure proper import and setup of our assets and DAM.
It was a lot of work! But worth the effort to get our assets cleaned up and organized. Enough time and personnel need to be allotted for any implementation, but we had some advantage in having our assets in a previous DAM with attached metadata in XML, and our users were prepared with knowledge of our existing DAM at that time. Though old habits present their own issues, a company that is starting from scratch with no DAM has to think farther ahead about how it will organize and collect assets. Far more pre-planning with stakeholders would be needed for a company starting an implementation from scratch.
This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.
We started with the Widen system but ended up switching to Brandfolder. Brandfolder had the consistent interface across internal and external platforms. It was easier to use and search for assets for our internal team and brand partners. I preferred the Widen system's ability to share assets with direct links and the ability to add metadata upon upload.
New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.