Report Vendor Profile

<< Back to Vendors

  All profile information has been provided by the vendors themselves and they are responsible for both its accuracy and validity.


Profile Index

    The DAM Playbook

    This vendor appears in the in the DAM Playbook.

    DAM 10 Core Accreditation

    This vendor is 10 Core accredited.

    Vendor Details

    Contact Name
    Robert Hickey
    Company Profile
    About Bynder:

    Bynder goes far beyond managing digital assets. The digital asset management platform enables teams to conquer the chaos of proliferating content, touchpoints, and relationships in order to thrive. With powerful and intuitive solutions that embrace the way people want to work and a richly integrated ecosystem, Bynder is the brand ally that unifies and transforms the creation and sharing of assets, inspiring teams, delighting customers, and elevating businesses.

    Bynder’s 500+ employees, known as ‘Byndies’; together constitute the world’s most extensive pool of digital asset management expertise. Bynder enables more than 1.7M users across 4000 organizations, including Spotify, Puma, Five Guys, and Icelandair. Founded in 2013, Bynder has eight offices around the globe, including the Netherlands, the United States, Spain, UK, Australia, and UAE.

    Contact Telephone
    +1 857 496 6646
    Contact Email
    Company Website
    Years Trading
    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.
    • $100m - $1bn
    Company Turnover
    This is the actual turnover of the vendor in US Dollars.
    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.
    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.
    Office Locations
    • Amsterdam, The Netherlands
    • Boston, United States
    • San Carlos, United States
    • London, United Kingdom
    • Melbourne, Australia
    • Rotterdam, The Netherlands
    • Barcelona, Spain
    • Dubai, UAE
    Product Name
    Documentation URL
    User group URL
    Online trial link
    Source code link
    Company RSS Feed URL
    Company LinkedIn URL
    Company Facebook URL
    Clients & Customers
    • Five Guys
    • Puma
    • Canon
    • Spotify
    • Clio
    • THG
    • Golfbreaks
    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
    We place a high value on partnering with other industry and market leaders to ensure we are actively involved in creating the best overall environment for our customers. Currently we have 40+ partners.


    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
    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


    Software Delivery Methods
    • Cloud/SaaS


    Client refers to the type of hardware or software device that can be used to access or control the DAM system.
    • Web client
    • iOS mobile app
    • Android mobile app
    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.
    • Not applicable
    Server Operating System Notes
    The choice of server operating system can vary and may be subject to updates or changes by the platform

    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
    The choice of web server technology can vary and may be subject to updates or changes by the platform

    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
    • .NET
    • Node.js
    • PHP
    • Python
    • Perl
    • CFML
    • C++
    • Other
    Server Technology Notes
    The choice of software development technologies can vary and may be subject to updates or changes by the platform

    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.
    • MySQL
    • Postgres
    • Proprietary
    • NoSQL
    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).
    • Solr
    • Custom (developed in-house)
    Search Technologies Notes
    We use SOLR search technology so search results are shown instantly. The SOLR features include full-text search, faceted search, real-time indexing, dynamic clustering, database integration, NoSQL features and rich document handling. Bynder also has custom (developed in-house) AI search technologies.

    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.
    • Yes
    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.
    Bynder's SOA approach involves breaking down its software and modules into discrete, independent services that communicate through well-defined APIs. This architecture allows Bynder to efficiently manage various aspects of its platform, such as asset storage, metadata management, user authentication, and workflow automation, as distinct services that can be developed, deployed, and maintained independently.

    Unique SOA Services
    If the vendor uses a Service Oriented Architecture, they should be able to identify a number of unique services that are isolated from each other. Note there is overlap between with question and the one about scalable asset processing. Some vendors do not have an SOA but do offer large scale asset processing capabilities.
    • Storage
    • Asset Media Processing
    • Metadata
    • Metadata Extraction
    • User Management
    • User Authentication
    • Permissions (Access Control)
    • Instance Management
    • Workflow
    • Search
    • Collections (lightboxes and arbitrary selections)
    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.
    • Yes
    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.
    Bynder employs a microservices architecture in conjunction with Kubernetes, a container orchestration platform, to power its digital asset management services. Kubernetes streamlines the deployment, scaling, and management of Bynder's microservices, ensuring high availability and resource optimization. Kubernetes automates the provisioning and scaling of containers, allowing Bynder to efficiently manage the diverse set of microservices that constitute its platform. This combination of microservi

    Unique Microservices
    If the vendor uses microservices, they should be able to identify a number of unique services that are isolated from each other. Note there is overlap between with question and the one about scalable asset processing. Some vendors do not have microservices but do offer large scale asset processing capabilities via an alternative method.
    • Storage
    • Asset Media Processing
    • Metadata
    • Metadata Extraction
    • User Management
    • User Authentication
    • Permissions (Access Control)
    • Instance Management
    • Workflow
    • Search
    • Collections (lightboxes and arbitrary selections)


    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
    Search Notes
    Duplicate Clean-up - Collections - Categories and additional AI search capabilities

    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
    Visual Search
    Visual Search allows your DAM to search and identify digital assets based solely on their visual qualities, as opposed to relying on metadata and keywords. This is often achieved using a combination of natural language processing, artificial intelligence, and image recognition.
    • Yes
    Visual Search Notes
    Similarity Search, Search by Image


    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
    • XMP
    • EXIF
    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.
    • XMP
    Embedded metadata support notes

    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
    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.
    • Text field
    • Text area (narrative)
    • Radio
    • Drop down menu
    • Combo-box (multi-item selection)
    • Checkbox
    • Date
    • File attachment
    • Numbers
    • Other

    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?".
    • Most popular assets by download
    • Most active users by uploads
    • Most active users by downloads
    • Average number of search results returned over a given period
    • Asset search to download ratio
    • Download activity over a given period
    • Login activity over a given period
    • Popular search terms

    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
    Dynamic Asset Transformation is fully integrated into your Bynder DAM making sure you don't need to rely on external systems for derivative generation.

    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
    • Change colorspace
    • Effects & filters
    • Batch manipulate groups of assets
    Image Manipulation Notes
    Focus point

    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
    • Timeline metadata
    • Batch operations on multiple video assets
    Video Manipulation Notes

    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
    • Excel (XLS or XLSX)
    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
    • Excel (XLS or XLSX)


    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
    API Notes
    Bynder's DAM API enables developers to build their bynder-powered applications based on a large set of functionalities provided to them. This is accessible via an HTTP RESTful interface. For more API information:

    API-First Architecture
    API-First means that anything the user can do via the graphical interface is possible via the API. If a DAM has an API-First architecture it is far more likely to be easier to integrate with other solutions than one that does not.
    • Yes
    API-First Notes
    If the vendor claims an API-First architecture then they should be able to provide a definition of it. In addition, documentation which describes their support for it will typically be available. Implementing API-First is a complex undertaking so vendor development teams will definitely know whether they have this attribute or do not.
    By prioritizing the development and accessibility of well-defined and robust APIs, Bynder empowers its users to seamlessly integrate, extend, and customize the platform's capabilities. This API-first strategy enables businesses to connect their existing systems and applications with Bynder, facilitating efficient data exchange and workflow automation.

    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.
    • Other
    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.
    Bynder uses the Amazon Simple Notification Service (AWS SNS) to monitor changes in your brand portal and to push these events to other systems. Instead of having to continuously check our API for changes, an external system can be notified automatically via SNS in the event of a change. These notifications can be sent via email or SMS. Also it is possible to send them to AWS Lambda, Amazon SQS and a HTTP/S or API endpoint.

    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
    • Amazon Glacier
    • Box
    • Dropbox
    • Google Drive
    • SFTP/SSH
    Storage Integration Notes
    With the Bynder API, developers can build and customize storage integrations that seamlessly connect the platform to various storage solutions, whether cloud-based or on-premises. Additionally, Bynder provides pre-built integrations with popular cloud storage providers

    AI Component Integration
    A number of DAMs integrate with multiple third party AI image recognition components. This question allows you to see which ones they use.
    • Amazon Rekognition
    AI Notes
    This question seek to find out how vendors have implemented their support for AI image recognition components. A number of vendors may have also developed custom-built AI solutions entirely in-house and this question gives them an opportunity to present those.
    Bynder also actively develops an in-house AI Component to streamline content management, improve asset discoverability, enhance user experiences, and increase overall operational efficiency.

    Content Delivery Networks (CDN) Integration
    Content Delivery Networks allow digital assets to be distributed across a wide geographic area to improve performance and reduce the pressure on the DAM system for in-demand assets.
    • Akamai
    • Amazon Cloudfront
    • Cloudflare
    Content Management Systems (CMS) Integration
    Many DAM solutions now provide specific integration modules that allow users to select assets from their Content Management System of choice without leaving the CMS application in order to do so.
    • Adobe Experience Manager
    • Contentful
    • Contently
    • Contentstack
    • Drupal
    • Episerver
    • HubSpot CMS
    • Kentico
    • Magnolia
    • SiteCore
    • WordPress
    CMS Integration Notes
    By leveraging the Bynder API, developers can design tailored CMS connectors that seamlessly link their preferred CMS with the Bynder digital asset management solution. Alternatively, Bynder provides out-of-the-box integrations with several popular CMS platforms listed above or described here:, Bloomreach, Optimizely, Storyblok, Tridion Sites,, Crownpeak, Hygraph, Progress Sitefinity, Publitas, eGo CMS, Veriflies, Stackbit Agility CMS and ButterCMS

    Creative Tools Integration
    Some DAMs will integrate directly with specific creative tools so designers and creatives do not need to leave them in order to use assets from the DAM.
    • Adobe Creative Cloud
    Creative Tools Integration Notes
    With the Bynder API, users have the flexibility to craft customized integrations for creative tools or take advantage of the platform's existing, readily available creative tool integrations. Other creative tools integrations are: CI Hub, Marq, empower Suite, Templafy, Canva, Microsoft Office 356, Figma and Stensul

    E-commerce Integration
    A number of DAMs integrate with e-commerce systems so that product catalogues can be updated automatically from the DAM. There might also be features like tracking of asset usage and conversion ratios for product images etc.
    • Adobe Commerce (Magento)
    • SAP Commerce
    • Shopify
    E-commerce Integration Notes
    Connecting Bynder to E-commerce platforms enables the sync of brand-approved product and web assets across all e-commerce experiences. Through the Bynder API, users can create customized e-commerce integrations or leverage the platform's existing e-commerce integrations. Other E-commerce Integration(s): Salesforce Commerce Cloud

    Enterprise Content Management (ECM) Integration
    • Adobe Experience Manager (CMS)
    • Box
    • SharePoint
    ECM Integration Notes
    By leveraging the Bynder API, developers can design connectors tailored to their specific ECM software, enabling the seamless transfer of digital assets between the Bynder digital asset management solution and their ECM ecosystems.

    Integration Platform as a Service (iPaaS)
    • Workato
    iPaaS Integration Notes
    Whether through customized iPaaS integrations built on the Bynder API or Bynder's established options like, Adobe Workfront Fusion and Workato, users can achieve seamless connectivity and data flow, optimizing their digital asset management processes

    Marketing Operations & Project Management Integration
    • CreativeForce
    • Jira
    • Trello
    • Workfront
    • Wrike
    Marketing Operations & Project Management Integration Notes
    The Bynder API serves as a crucial connector that allows for seamless integration and data exchange between Bynder and a variety of related tools such as Actito, Marketo and Microsoft Dynamics 365 Marketing. You can build your own integration or leverage one of our pre-built integrations.

    Master Data Management (MDM) Integration
    • None
    MDM Integration Notes
    While both DAM and MDM systems deal with data and digital assets, they serve different purposes. By leveraging the API, developers can establish seamless connections between Bynder's digital asset management platform and their MDM solution.

    Mobile Apps Integration
    • Android
    • iOS
    Office & Productivity Integration
    • Digideck
    • Office 365
    • Slack
    Product Information Management (PIM) Integration
    • Akeneo
    • inRiver
    • SAP Commerce Cloud
    • Salsify
    • Stibo
    PIM Integration Notes
    Bynder provides pre-built PIM integrations, often supported by iPaaS platforms like, simplifying the process of connecting PIM and DAM systems like DDP-Suite and Contentserv.

    Rights Management Integration
    • None
    Rights Management Integration Notes
    Bynder has an integrated Rights Management solution

    Sales & Marketing Integration
    • Actito
    • HubSpot
    • Highspot
    • Marketo
    • SalesForce
    Sales & Marketing Integration Notes
    Whether through customized integrations or Bynder's established options, users can foster a more efficient and cohesive workflow, aligning their marketing and sales efforts for greater impact and productivity.

    Social Media Integration
    • Hootsuite
    Social Media Integration Notes
    Whether through customized integrations or Bynder's established options, users can foster a more efficient and cohesive social media workflow, improving efficiency in social media operations with tools like Hootsuite and Brandwatch.

    Stock Media Providers Integration
    • AdobeStock
    • Getty Images
    • iStock
    • Shutterstock
    • Unsplash
    Templating & Print On-Demand Integration
    • Gelato
    • Templafy
    Video Integration
    • None
    Web Analytics Integration
    • Google Analytics

    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.
    • No
    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.
    • No


    Authentication Support
    If you need to integrate with an existing corporate authentication service then this option will be important for you.
    • Active Directory
    • Azure Active Directory
    • Google SSO
    • LDAP
    • Okta
    • OpenID
    • 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)
    • Arabic
    • Other
    • French
    • Spanish
    • Italian
    • German
    • Dutch
    Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
    • Yes

    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.
    • Yes
    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.
    • Yes

    Product Screenshots

    • Guidelines
    • Login Brand Portal
    • Brand Store
    • Workflow
    • Home Page

    Profile Last Updated: 17/04/2024

    << Back to Vendors

      All profile information has been provided by the vendors themselves and they are responsible for both its accuracy and validity.