<< back to results



Amplifi.io


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

Profile Navigator

Vendor Details

Contact Name
Jesse Knight, Enterprise Sales Director
Company Profile
Our content hub enables brands to quickly and efficiently organize and share marketing media & product information across all go-to-market people, partners, and programs.

This product works best for enterprise or SMB marketers and digital content teams in charge of delivering tons of brand and product specific marketing content to a wide-range of partners, retailers, sales teams, etc.

We thought you’d appreciate some ideas on how to leverage digital asset management to beat out your competitors.

Are you facing these issues?

  1. Assets are spread across multiple silos
  2. Employees and partners can’t find the right content
  3. Management, conversion, and sharing processes are inefficient
  4. Copyright, brand accuracy, or content mistakes are common
  5. Business is hurt by loss, accidental duplication, slowness, and other go-to-market, sales content and media related bottlenecks

Amplifi.io helps solve all these issues by offering a single, easy-to-use solution to manage assets and product marketing information. Centralizing content increases accessibility, speeds content to market for higher ROI, and reduces waste and bottlenecks.

Amplifi.io is DIFFERENT in that we can also accept and manage PIM (product information) data right in the system. Unlike most DAM systems that only manage digital files, Amplifi.io offers unique technology to easily import and manage relevant data from your other business systems and use it to accelerate the organization of your content and deliver the data along with the digital assets for a more successful digital supply chain and better sales results.

Our turnkey commerce-focused DAM solution is an easy, centralized way to handle all your marketing media. (And fuel growth...and make you a hero). 

CALL TO ACTION:  Fill in the form on amplifi.io or call for a free expert needs analysis. If our software is a good fit then great!  If not, then our helpful experts can point you in the right direction.  (866) 452-5258

Contact Telephone
949 705-6900
Contact Email
jesse@amplifi.io
Company Website
https://amplifi.io
Years Trading
7
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.
  • $2m - $5m
  • Company Turnover
    This is the actual turnover of the vendor in US Dollars.
    5000000
    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.
    35
    Office Locations
  • Irvine, California USA
  • Product Name
    Amplifi.io
    Latest Version Number
    3.0.0
    Date Of Last Release
    15/05/2019
    Documentation URL
    https://apidoc.amplifi.io
    User group URL
    https://support.amplifi.io
    Online trial link
    https://amplifi.io/see-demo/
    Company LinkedIn URL
    https://www.linkedin.com/company/6398161/
    Clients & Customers
  • Toshiba
  • 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
    Network of globally diverse independent DAM consultants and implementation service providers.

    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
    Cloud Saas with customization modules possible.

    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.
  • No open source components used
  • 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
  • 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
  • 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
  • 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.
  • 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
  • NoSQL
  • Custom (developed in-house)
  • 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.
    We use an overall SOA approach in our architecture to separate functions into compartmentalized sub-services all accessed by API.

    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)
  • Other
  • Service Oriented Architecture Notes
    Separate services for maintenance and updating of system technology components.

    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.
  • 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.
    Components use an API to communicate with the main application via various controls. For example, thumbnail creation is separate server running that specific service, indexing of metadata is a separate server for that service, search, media transcoding, user authentication, etc. etc. most everything is available via API.

    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
  • 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
  • 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
  • Dublin Core
  • 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
  • Dublin Core
  • 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
  • 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
  • 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.
  • Format conversion
  • Change colorspace
  • Batch manipulate groups of assets
  • Other (please specify in notes below)
  • Image Manipulation Notes
    Use image in some custom templates.

    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
  • Batch operations on multiple video assets
  • Other (please specify in notes below)
  • Video Manipulation Notes
    Streaming links and/or playlists and easy publishing of videos to social sites like YouTube.

    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)
  • Metadata Export Notes
    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

    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).
  • No
  • 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.
  • N/A (hooks not supported)
  • 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.
    NA

    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
  • FTP
  • Google Cloud Storage
  • SFTP/SSH
  • 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

    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
  • Other
  • Authentication Notes
    Custom via API is also provided for.

    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
  • Chinese (Mandarin)
  • French
  • Spanish
  • Italian
  • German
  • Multilingual Metadata Support
    See previous question. Most DAM systems with multi-lingual support will provide it for metadata.
  • Yes
  • Multilingual Support Notes
    Content including both structured and un-structured data can be multi-lingual - robust tools to manage are included.

    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
  • Version Control Notes
    Any file in Amplifi.io can be quickly updated with a replacement version while keeping the original version/s in archive and maintaining usage assignments and URL links. rnTo replace a file/s with a new version, simply upload the new file/s using the same name as the original file. rnVERSIONING: STEP 1rnOpen Media Uploader, drag and drop or click to select the replacement files to add to the uploader. rnrnVERSIONING: STEP 2rnAny matching files names for files that already exist in Amplifi.io ar

    Product Screenshots

    Log in to view screenshots.