<< back to results



WoodWing


Notice: All information has been provided by the vendors themselves.

Profile Navigator

Vendor Details

Contact Name
Magdalena Ivanova
Company Profile

WoodWing develops systems to streamline content creation.


We work with top media companies like editorial publishers, marketers, and corporate organizations, to create a customer-first approach to ensure our products are constantly exceeding expectations and addressing business challenges.


With over 20 years of experience in the media industry, partners in over 100 countries and more than 1,500 customers, we thrive by helping our clients stay competitive, leverage new industry opportunities and consistently grow with us.


Beginning life to assist print publishers with improving their publishing workflow, we now produce products to assist a range of organizations with their marketing, advertising, content creation, reporting and Digital Asset Management.


As a long-standing Adobe Technology Partner, the benefits customers experience with WoodWing's products include easy integration with third-party applications in any environment, due to the open architecture.

WoodWing Assets (previously called Elvis DAM) is WoodWing's flagship enterprise DAM solution, and forms part of WoodWing's product collection.

Leading portfolio of products

  • WoodWing Studio (a multichannel publishing solution formerly known as Enterprise) and WoodWing Assets: These are solutions for digital asset management and content creation that help users optimize the process of creating, managing, sharing and distribution of content.
  • Inception: Inception makes it incredibly easy for anyone to create responsive content for mobile devices.
  • Swivle: WoodWing's out-of-the-box SaaS solution that offers an intuitive interface, easy activation, and affordable pricing. While not having to install the software on-premise, Swivle mainly caters to SMBs, agencies and marketing teams that want to get started quickly with asset organization - all in the cloud.

Global support and resources

Our offices are located in Europe, the Americas, and the Asia Pacific and we work closely with over 80 partners in more than 100 countries, as well as other technology vendors worldwide.


Open technologies and easy integration

Based on our philosophy of helping our customers deliver content anytime, anywhere, in any format, WoodWing supports the use of open, credible technologies. Our solutions have open architectures that enable simple, easy integration in any environment and with any third-party application.


Household names and rising stars

The result is that today thousands of companies trust us to help them stay competitive, leverage new opportunities, and grow their business. It's something we are immensely proud of and if you'd like to know more, you can read about their success stories. Why not join them?



Contact Telephone
+31756143400
Contact Email
marketing@woodwing.com
Company Website
https://www.woodwing.com
Years Trading
20
Company Turnover Category
The turnover of the vendor can give an indication of their size. US Dollars is used as common currency to allow comparisons. Note that turnover is not necessarily any indicator of financial stability but as part of any procurement due diligence you are obliged to carry out by your organisation, any vendors who have not agreed to show their turnover here might be required to do so if subsequently appointed.
  • $10m - $50m
  • Company Turnover
    This is the actual turnover of the vendor in US Dollars.
    15000000
    Percentage of Revenue From DAM Software
    A vendor might have a large turnover and many employees, but their DAM software division is a very small element of what they offer. If a large proportion of their revenue comes from DAM solutions (licenses, support, hosting, consulting etc) then this may mean they are more specialised, but also there are risks to their overall financial stability if there is a downturn in the DAM software market.
    50
    Number of Full-Time Employees
    Along with turnover, the number of full-time employees gives an indication of the size of the vendor. Note that although a firm might have many employees, not all of them might be dedicated to developing DAM solutions, so this cannot be relied on in isolation.
    150
    Office Locations
  • Zaandam, the Netherlands
  • Detroit, MI, USA
  • Kuala Lumpur, Malaysia
  • Product Name
    WoodWing Assets
    Latest Version Number
    6.48
    Date Of Last Release
    19/05/2020
    Documentation URL
    https://helpcenter.woodwing.com/hc
    User group URL
    https://helpcenter.woodwing.com
    Trial download or sandbox link
    https://www.woodwing.com/en/digital-asset-management-system/elvis-dam-contact-form?channel=wwcom
    Company LinkedIn URL
    http://www.linkedin.com/company/woodwing
    Company Facebook URL
    https://www.facebook.com/WoodWingSoftware
    Clients & Customers
  • https://www.woodwing.com/en/clients
  • Hearst
  • Coca-Cola European Partners
  • Yamaha Motor Europe
  • Konica Minolta
  • Pacific Magazines
  • Conde Nast
  • ANWB
  • Dekamarkt
  • WPP
  • Tiskara Zagreb
  • UBM Medica Australia
  • Westmead Children's Hospital Sydney
  • Akcent Agency Prague Ltd
  • APN Holdings New Zealand Limited
  • Olive Media Greece
  • AVRO Broadcasting Netherlands
  • AVVIR Norway
  • Bonnier Books Germany
  • Burda Media Prague
  • Charterhouse Production UK
  • Columbia University NY
  • Design Concept Helsinki
  • Fetim Group
  • Gravity Agency Hamburg
  • Groupama Insurances Paris
  • Ingersoll Rand USA
  • Kaya Media Korea
  • Tana Bana Design
  • Partner Network
    If the vendor operates through a sales channel they may use intermediaries who have regional focus or additional specialisms in a given vertical market.
  • Yes
  • Partner Network Notes
    WoodWing has a partner network of 90+ business partners, covering more than 100 countries. All partners are extensively trained and are able to install, configure and support WoodWing Assets (Elvis DAM).

    Licensing

    Licensing Model
    This refers to the type of licence the DAM system software is supplied under. Proprietary means that the developer restricts access to the source code (the instructions used to generate the software). Open source means that the developer provides full access to the code so you can modify it yourself. Split model is hybrid and means they may offer both options with some restrictions removed (or added) depending on the model chosen. If split is selected, it is advisable to verify the differences with the vendor.
  • Proprietary
  • Licence Notes
    - perpetual - subscription

    Use of Open Source Components
    Many DAM systems use freely available open source components to deliver key functionality. The products themselves may not be open source, however. This question will help to identify to what extent they are open source.
  • Some open source components used, but core product is not open source
  • Open Source Component Usage Notes
    Open source components form part of the WoodWing Assets model.

    Hosting

    Software Delivery Methods
  • Installed (On-Premise)
  • Cloud/SaaS
  • Hybrid
  • Technology

    Client
    Client refers to the type of hardware or software device that can be used to access or control the DAM system.
  • Web client
  • Desktop client
  • iOS mobile app
  • Android mobile app
  • Client Notes
    Web client is responsive for use on tablets and mobile phones.

    Server Operating Systems supported
    This only applies for installed or hybrid DAM systems and refers to what types of OS they can be run on. This question is less relevant for DAM systems where a third party will be hosting it for you.
  • Windows
  • Linux
  • Mac OSX
  • Server Operating System Notes
    Runs on your system of preference. WoodWing Assets On-Premise runs on any popular server OS in the market, which means you have no dependency on the platform. Your WoodWing Assets server(s) can also be deployed in AWS to create a Private Cloud (PaaS) setup. Platform specifics: - Supported server operating systems: CentOS, Windows, OSX, AWS Linux. - HTML5 Web clients. - Integrated with Adobe Creative Cloud applications. - Available languages include English, Chinese (tra

    Web Server
    The type of web server software that the DAM system can operate with. Not all DAM systems use a web server and for pure SaaS products the question is irrelevant. If you either want SaaS or non-web DAM systems, do not choose an option.
  • Other
  • Web Server Notes
    Jetty

    Software Development Technologies Used
    This means the programming language or development technology used to implement the DAM system. This question is more important for open source software or if you have IT policy restrictions that require you to use (or not use) some technologies. It may not be relevant if you require a hosted DAM and never intend to host the system in-house.
  • Java/J2EE
  • Database Technology
    The Database that the DAM system uses. All DAM systems require some kind of storage for asset metadata and they are usually based on an existing technology - but that may not always be a conventional database. If the DAM will be hosted by someone else (e.g. SaaS/Cloud) this question may not be relevant.
  • No database
  • Database Notes
    ElasticSearch Index

    Search Technologies
    This refers to third party search components that the vendor uses to provide the text search features (and sometimes other related search functions).
  • ElasticSearch
  • Service Oriented Architecture
    Service Oriented Architecture (SOA) means the vendor's product uses a modular architecture where each core DAM function is delivered as a service which can be separated out independently from other functions. It is important for large-scale Digital Asset Management implementations or more complex integration requirements.
  • No
  • Service Oriented Architecture Definition
    Some vendors have widely differing opinions of what Service Oriented Architecture means. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a large scale DAM implementation or one with many complex integration requirements, SOA may not be relevant to your needs.
    A service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network. The basic principles of service-oriented architecture are independent of vendors, products and technologies.[1] A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online.

    Microservices
    Microservices are similar in nature to Service Oriented Architecture (SOA) with the key difference being that they can be deployed entirely independently of the platform that uses them. Microservices are usually prevalent in Digital Asset Supply Chain projects.
  • No
  • Microservices Definition
    As with Service Oriented Architecture (SOA) some vendors have different opinions of what microservices are. Their response to this question allows you to understand if their definition concurs with your own. If you are not contemplating a Digital Asset Supply Chain project, large scale DAM implementation or one with many complex integration requirements, microservices may not be relevant to your needs.
    NA

    Search

    Search Features
    This describes the search strategies that can be used to find assets. If you do not understand any of them, leave the options de-selected. Most DAM systems should support at least keyword search at a minimum.
  • Keyword
  • Auto-suggest
  • Folders
  • Filters
  • Faceted Search
  • Linked Asset Search
  • Other
  • Search Notes
    Also Taxonomy based search

    Index/Search Text Content Of Documents
    Some DAM systems can search the text content of document assets and that might be important for your DAM solution.
  • Yes
  • Metadata

    Embedded metadata support (reading)
    Embedded metadata refers to information stored within asset files which can be searched from the DAM system. There are different standards for this type of metadata. Some image cataloguing software like Adobe Lightroom will write this data to asset files and a device like a camera may capture details also such as GPRS coordinates where an photo was shot. XMP metadata is often used with other types of files such as InDesign or PDF. If you are unsure whether this applied to you, do not check any options.
  • IPTC
  • IPTC Core
  • XMP
  • EXIF
  • PLUS
  • Dublin Core
  • Other
  • Embedded metadata support (writing)
    See the reading question above for more details on what embedded metadata is. This question refers to whether embedded metadata can be written back to files if edited within the DAM system.
  • IPTC
  • IPTC Core
  • XMP
  • EXIF
  • PLUS
  • Dublin Core
  • Other
  • Controlled Vocabularies
    Controlled Vocabularies are predefined lists of search terms. They can be realised in many different ways but the common factor is the user picks from a restricted selection rather than enters a keyword. Most DAM systems will usually support both controlled vocabularies and keywords.
  • Yes
  • Controlled Vocabulary Notes
    We support a taxonomy structure.

    User Defined Metadata Fields
    The ability to configure metadata your own metadata fields is important for DAM systems so you can assign a dedicated field for certain items of information rather than using a generic classification method or one of the vendor's own standard fields.
  • Yes
  • Cataloguing Interface Options
    When cataloguing assets with custom fields, some metadata will be controlled selections, others will be free text. There are further choices like date fields, file attachments etc.
  • None
  • Business Intelligence & Reporting

    Asset Usage Records
    To enable reports to be generated, DAM solutions must retain records of asset usage, including searching, download and editing of records. The reporting should include the user who carried out the activity and the date/time it occurred.
  • Yes
  • Audit Trail
    A detailed audit trail that logs every user action in a central record is useful to gain insight into user behaviour. Comprehensive audit trails allow DAM system users to produce reports that address their unique needs.
  • Yes
  • Built-In Reports
    A range of built-in reports that you can quickly generate is useful to answer common questions such as the "what is our most popular asset?".
  • Other reports (please specify)
  • Reporting Notes
    Open source sample reports that can be adjusted & customized

    Asset Processing

    Dedicated/Scalable Proxy or Derivative Asset Generation
    Nearly all DAM systems will generate thumbnails and previews of media, including more dynamic types like video or audio. Some products use a separate server to do this which usually makes them more suitable for large scale asset ingestion and processing.
  • Yes
  • Dedicated/Scalable Proxy or Derivative Asset Generation Notes
    Admins can set up Elvis to run as a cluster during set-up, and instances/nodes can be assigned to be set-up to run as processing engines.

    Multi-Page Document Asset Previews
    If you deal with document oriented assets, having a solution which can generate multi-page previews (and also zoom in on them) can save the hassle of downloading a file only to discover it is not the one you need. For assets with very similar content, this can be a useful feature.
  • Yes
  • Asset Manipulation

    Image Manipulation
    Many DAM systems allow users to manipulate images by resizing, cropping etc. Choose any features which are important to your users.
  • Image re-sizing
  • Image cropping
  • Format conversion
  • Flip images
  • Rotate image
  • Batch manipulate groups of assets
  • Video Manipulation
    Some DAM systems may allow video assets to be converted or modified. If that is a potential requirement for you, specify those features which are likely to be needed. EDL = Edit Decision List and refers to providing in/out points when editing video footage.
  • Format conversion
  • Data Import/Export

    Importing Metadata
    Importing metadata is an important feature if you have either legacy assets or metadata is generated using some other tools (for example a spreadsheet). Not all systems offer this, but usually if the feature is not available, the vendor will be able to carry out batch importing for you via professional services (note: this will usually incur a cost, unlike a built-in capability).
  • Yes
  • Metadata Import Formats
    This question only applies if the vendor has features to import metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
  • CSV (or any delimited file)
  • XML
  • Metadata Import Notes
    Imports can also be done using the API.

    Exporting Metadata
    As well as importing metadata, sometimes it is important to be able to export sections of it to conduct further analysis in third party applications. Not all products support this, but usually it will be possible to request the vendor provides an export via professional services (although a fee may be charged).
  • Yes
  • Metadata Export Formats
    This question only applies if the vendor has features to export metadata. There are common formats like CSV, XML and Excel which DAM solutions may support. If this is a requirement you are likely to make frequent use of, it is essential to verify whether the product supports the formats you typically work with.
  • CSV (or other delimited file)
  • XML
  • Integration

    API
    API means Application Programming Interface and allows third party software to control a DAM system. If you intend to integrate your DAM with another existing solution then you need to choose the API protocol that is compatible with that.
  • REST
  • SOAP
  • Other
  • API Notes
    Also Event-based API using webhooks.

    Hooks
    Hooks are related to APIs but are initiated by the application rather than by an external application making the request. Hooks allow other actions to be initiated based on events, for example if a user downloads an asset, an action can be commenced to notify another application that this has taken place (along with the ID number of the asset, date/time etc).
  • Yes
  • Hooks Targets Supported
    In most DAM applications that support them, hooks are initiated as web requests, so the system will call a given external URL and provide some parameters. Some solutions also support initiating scripts or applications which can run on the server where the system is hosted.
  • Web hooks
  • Hooks Definition
    If the vendor claims support for hooks, check how they define them and see if their interpretation concurs with your own. A reasonably detailed explanation along with citations/links should be given here.
    Webhooks API WoodWing Assets also features a Webhooks API, which enables real-time event-driven integrations. It gives you more control and additional integration capabilities including: - Real-time enrichment of metadata by integrating an AI service like Clarifai or Google. - User notifications when a file has been changed or added, for example via email or Slack. - Live sync of WoodWing Assets with another system, for example, to push the latest product shots to a PIM.

    Storage Integration
    Many DAM solutions will now allow assets to be stored on the server of Cloud storage providers. This allows asset files to be distributed and/or integrated with other solutions. Some third party services use generic protocols like FTP, others are proprietary.
  • Amazon S3
  • Scripting & Plug-Ins

    Scripting Capabilities
    Some advanced DAM solutions have a scripting capability that allows users or third parties to add functionality which the vendor did not originally envisage. Usually programming skills will be required to use this, but some tools have visual interfaces also.
  • Yes
  • Plug-In Support
    In addition to scripting (or sometimes instead of), some DAM solutions will have a plug-in architecture that allows third party developers to extend the core platform.
  • Yes
  • Authentication

    Authentication Support
    If you need to integrate with an existing corporate authentication service then this option will be important for you.
  • Active Directory
  • LDAP
  • SAML
  • Multi-Lingual Options

    Multilingual Application Interface Support
    The interface means the controls to use the DAM system. This is different from the metadata support which is usually entered by end users when cataloguing assets.
  • English
  • Polish
  • Russian
  • Chinese (Mandarin)
  • Other
  • French
  • Spanish
  • Italian
  • German
  • Dutch
  • Norwegian
  • Swedish
  • Finnish
  • Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
  • Yes
  • Multilingual Support Notes
    We also support: - Chinese traditional - Chinese simplified - Japanese - Korean - Portugese

    Version Control

    File versioning
    File versioning refers to the digital media associated with an asset record. This is usually the minimum requirement for a DAM system to claim support for versioning assets. See also responses to the related question about metadata versioning below.
  • Yes
  • Metadata versioning
    Metadata versioning is separate from the files associated with assets. Many DAM solutions will track updated digital assets but only retain a single current version of the metadata. Since metadata is likely to be edited many more times than assets get replaced, this can be an important point to check.
  • No
  • Independent Metadata And File Versioning
    This questions assesses whether the solution allows versions of either the file or metadata to be reverted independently or if both are linked to a single shared version instance.
  • No
  • Product Screenshots

    Log in to view screenshots.

    Product Videos

    Log in to view videos.