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.

Frontify
https://www.frontify.com/en/

Profile Index

    The DAM Playbook

    This vendor does not appear in the in the DAM Playbook.

    DAM 10 Core Accreditation

    This vendor is not 10 Core accredited.

    Vendor Details

    Contact Name
    Roger Dudler
    Company Profile
    Frontify is a brand building platform where visionaries and brand builders create, organize, and collaborate on magnetic brands. Combining a user-friendly DAM and customized portals, Frontify serves global brands including Uber, Microsoft and Kia.

    Established in 2013, Frontify is headquartered in St. Gallen, Switzerland, and has offices in New York City, USA, and London, UK and employs more than 300 employees.

    Contact Email
    support@frontify.com
    Company Website
    https://www.frontify.com/en/
    Years Trading
    11
    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.
    • $50m - $100m
    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.
    30
    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.
    300
    Office Locations
    • St. Gallen, Switzerland
    • London, United Kingdom
    • New York, United States
    Product Name
    Frontify
    Online trial link
    https://www.frontify.com/en/signup/
    Company LinkedIn URL
    https://www.linkedin.com/company/frontify
    Company Facebook URL
    https://www.facebook.com/Frontify/
    Clients & Customers
    • Uber
    • Kia
    • Lufthansa
    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

    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
    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 are documented in an internal inventory, which is updated upon any change, and at the very least on a yearly basis.

    Hosting

    Software Delivery Methods
    • Cloud/SaaS

    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
    Frontify is mainly browser-based, which makes it compatible with most systems. The main requirement is an HTML5-capable browser.

    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
    Frontify is a cloud-based solution hosted with Amazon Web Services. Our application servers run Amazon Linux 2.

    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
    Frontify uses nginx.

    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.
    • Node.js
    • PHP
    • C++
    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
    • 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).
    • 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.
    NA

    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
    • Folders
    • Filters
    • Faceted Search
    Search Notes
    Other: AI-assisted 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.
    • No
    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.
    • No

    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
    Embedded metadata support notes
    We only read and make available certain fields. Tags, Description, Author

    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.
    • No
    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)
    • Drop down menu
    • Checkbox
    • Date
    • File attachment
    • Numbers
    • Other
    Cataloguing Interface Notes
    Verify how the vendor has implemented a given cataloguing interface control. It is preferable if they can demonstrate with examples of how they have implemented interface options for cataloguing and metadata entry.
    Other: URL

    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
    • Average number of search results returned over a given period
    • Download 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
    It’s a completely separate service that processes and creates Derivates JIT with a caching layer in front of it.

    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
    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.
    • No video manipulation features

    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).
    • No, via professional services
    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)
    • Excel (XLS or XLSX)
    Metadata Import Notes
    Frontify offers professional services (charges apply) for migrations/bulk imports of assets from previous systems. This includes assets together with metadata, the metadata needs to be provided as a CSV (or other delimited file).

    Such an import can also be performed free of charge by the customer at any point via Frontify’s GraphQL 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).
    • No, via professional services
    Metadata Export Notes
    Any embedded metadata that is contained in a file will stay available after uploading to and downloading from Frontify. Export of any metadata values that are applied and managed inside of Frontify is possible via Frontify’s GraphQL API.

    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.
    • Other
    API Notes
    We use GraphQL

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

    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.
    Every time an event occurs in Frontify, we notify registered webhooks. This is done through a queue and a separate service that actually notifies the receiver. We use batching of the same event/actor to not overwhelm the receiver on bulk cases in our application.

    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
    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
    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.
    • Amazon Cloudfront
    Content Delivery Networks (CDN) Integration Notes
    We use CloudFront as a Caching layer for JIT image transformation and the delivery of all previews/renditions of our assets.

    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
    • Contentstack
    • Drupal
    • HubSpot CMS
    • Magnolia
    • SiteCore
    • WordPress
    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.
    • None
    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.
    • None
    Enterprise Content Management (ECM) Integration
    • Adobe Experience Manager (CMS)
    Integration Platform as a Service (iPaaS)
    • Tray.io
    • Zapier
    Marketing Operations & Project Management Integration
    • Jira
    • Monday.com
    • Wrike
    Master Data Management (MDM) Integration
    • None
    Mobile Apps Integration
    • Android
    • iOS
    Office & Productivity Integration
    • Microsoft Office
    • Slack
    Office & Productivity Integration Notes
    Microsoft Office: A native plugin for Microsoft apps, which enables direct searching, opening, placing of assets stored in Frontify, as well as uploading documents, sheets and presentations to Frontify from within Word, Excel and Powerpoint. It works on both desktop versions and Office 365 versions. The plugin is powered by LinkrUI (https://santacruzsoftware.com/linkrui/).

    Slack: Asset uploads, new annotations, and status changes of assets in the libraries or projects create notification mess

    Product Information Management (PIM) Integration
    • None
    Rights Management Integration
    • None
    Sales & Marketing Integration
    • HubSpot
    • Highspot
    • SalesForce
    Social Media Integration
    • Facebook
    • Instagram
    Social Media Integration Notes
    Our social media integrations are "light" integrations. This means posts from social media platforms can be displayed on Frontify platform, simply by embedding it.

    Stock Media Providers Integration
    • Getty Images
    • Shutterstock
    Templating & Print On-Demand Integration
    • Templafy
    Video Integration
    • Vimeo
    • YouTube
    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.
    • Yes
    Plug-In Capability Notes
    Platform apps/Blocks/Themes using the Brand SDK

    Authentication

    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
    • IBM Cloud Identity Connect
    • LDAP
    • Okta
    • OneLogin
    • OpenID
    • SAML
    Authentication Notes
    Frontify fully supports SSO as long as it provides SAML 2.0 or OpenID Connect.

    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
    • Norwegian
    • Swedish
    • Finnish
    Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
    • No
    Multilingual Support Notes
    While our portals can be configured into multilingual set-ups, the metadata of the assets cannot.

    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.
    • Yes
    Version Control Notes
    The asset revisions feature allows for unlimited versions of an asset. It is possible to roll-back to an earlier version of the asset at any time. The metadata of the asset is stored separately from the asset itself. Any changes to metadata take immediate effect and cannot be rolled back.

    Product Screenshots

    • Frontify DAM
    • Frontify DAM
    • Frontify DAM
    • Frontify DAM
    • Frontify DAM Desktop App


    Profile Last Updated: 09/04/2024
    Top

    << Back to Vendors



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