<< back to results



The DAM Software Company, Inc.


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

Profile Navigator

Vendor Details

Contact Name
Erika Nortemann
Company Profile
The DAM Software Company, Inc. is a Los Angeles-based SaaS company that builds--no surprises here--digital asset management software solutions. Our latest product, MediaGraph is focused on improving the DAM lives of all departments, not just marketing.

Contact Telephone
(805) 557-8407
Contact Email
DAMinfo@mediagraph.io
Company Website
https://www.mediagraph.io/
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.
  • Up to $500k
  • 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.
    100
    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.
    3
    Office Locations
  • 340 S Lemon Ave #2280, Walnut, CA 91789
  • Product Name
    MediaGraph
    Online trial link
    https://mediagraph.io/sign-up
    Company LinkedIn URL
    https://www.linkedin.com/company/tandem-vault/
    Company Facebook URL
    https://www.facebook.com/mediagraphdam
    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.
  • No
  • 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
  • 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
  • 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.
    We have separate, independently-scalable servers that handle web traffic, the asset processing pipeline, search, database, and queue handling but they don?t talk to each other over a proprietary protocol.

    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.
    We have separate, independently-scalable servers that handle web traffic, the asset processing pipeline, search, database, and queue handling but they don?t talk to each other over a proprietary protocol.

    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
  • 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
  • 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.
  • IPTC
  • IPTC Core
  • XMP
  • EXIF
  • 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
  • Checkbox
  • Date
  • File attachment
  • Numbers
  • 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
  • Download activity over a given period
  • Login activity over a given period
  • 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
  • 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
  • Effects & filters
  • 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.
  • Timeline metadata
  • Batch operations on multiple video assets
  • 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)
  • 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)
  • Metadata Export Notes
    We also support JSON.

    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
  • API Notes

    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.
    API-first means that we've designed MediaGraph around an API from the ground up, rather than building the product and adding an API later (like many of our competitors have done).

    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.
    Set a Storage Folder, Collection, or Lightbox as a ?source?, and specify a target URL. Any assets that are added to the source will trigger a webhook with details in the payload.

    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 Cloud Storage
  • 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.
  • 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.
  • WordPress
  • CMS Integration Notes
    via CI-Hub

    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
    via CI-Hub

    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
  • Box
  • Integration Platform as a Service (iPaaS)
  • None
  • Marketing Operations & Project Management Integration
  • None
  • Master Data Management (MDM) Integration
  • None
  • Mobile Apps Integration
  • None
  • Office & Productivity Integration
  • Google Apps
  • Office 365
  • Product Information Management (PIM) Integration
  • None
  • Rights Management Integration
  • None
  • Sales & Marketing Integration
  • None
  • Social Media Integration
  • None
  • Stock Media Providers Integration
  • None
  • Templating & Print On-Demand Integration
  • None
  • Video Integration
  • None
  • Web Analytics Integration
  • None
  • 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
  • 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
  • Okta
  • 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
  • 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

    Log in to view screenshots.

    Product Videos

    Log in to view videos.