Fingerprinting
Our fingerprinting solutions are designed to give you full control over your environment, infrastructure, and processing workflows - while maintaining strict compliance with licensing requirements. In order to use the fingerprinting solution you will require access to the metadata and assets via a Catalogue Feed.
We offer three choices for how you may Fingerprint on our system;
- We can host VMs in our environment > low costs asset access and managed services; or
- If your fingerprint applications are in AWS, use DirectConnect > lowest cost asset access; or
- Use your environment and access assets via our APIs > minimal changes required to your workflow

Deployment models:
Hosted
A fast, VM-based solution for immediate integration.
Hosted provides simplicity.
DirectConnect
A fully integrated model for advanced workflows, control, and cost efficiency.
DirectConnect provides control, scale, and efficiency.
Hosted (Managed VMs)
The Hosted model provides a managed virtual machine environment for running fingerprinting workloads. Hosted environments are provisioned ready for use and designed to integrate directly into your existing applications and workflows.
Infrastructure
We provision EC2-based virtual machines within a managed environment.
You can:
- Select instance types aligned to your workload requirements, including CPU or GPU-based compute
- Choose from standard configurations, including:
Standard | 2 | 8 GB | — | SSD or Standard |
Medium | 4 | 16 GB | — | SSD or Standard |
Performance | 8 | 32 GB | — | SSD or Standard |
High Performance | 16 | 64 GB | — | SSD or Standard |
Large Scale | 32 | 128 GB | — | SSD or Standard |
GPU Small | 4 | 16 GB | 1× NVIDIA GPU | SSD or Standard |
GPU Medium | 8 | 32 GB | 1× NVIDIA GPU | SSD or Standard |
GPU Large | 16 | 64 GB | 1–4× NVIDIA GPU | SSD or Standard |
- Configure storage options including SSD or standard disk
- Scale the number of instances within your allocated limits
Instances are securely accessible over the public internet and can be configured to support your fingerprinting workflows.
Audio access
Audio is accessed via controlled service endpoints configured directly on your provisioned instances.
Requests are made using:
- Track identifiers
- Format selection
- Partner credentials
These endpoints can be called from any application or service, enabling straightforward integration into your fingerprinting workflows.
Example request
GET /audio/track/{trackId}/format/{format}
Authorization: Bearer <token>Audio is delivered directly to the requesting application based on your access permissions, allowing immediate use within processing pipelines.
Security & rights enforcement
Access to content is governed by:
- Partner-level authentication
- Source access controls
- Catalogue and label-level permissions
Only content you are licensed to use is made available.
Formats
Audio is available in formats suitable for fingerprinting workflows, ranging from high-efficiency AAC encodings through to higher bitrate AAC formats, with availability optimised for broad catalogue coverage.
Cost efficiency
The Hosted model provides predictable, usage-based costs aligned to compute and request volumes.
As audio is delivered per request, costs scale with:
- Processing activity
- Data transfer volumes
- Format selection and delivery
This model is efficient for moderate workloads and standardised processing pipelines.
Benefits
Hosted is best suited for:
- Fast onboarding with minimal setup
- Standard fingerprinting workflows
- Teams without dedicated cloud infrastructure
- Use cases where simplicity and speed of deployment are prioritised
DirectConnect (Your AWS - connected)
DirectConnect enables you to run fingerprinting workflows entirely within your own AWS environment. DirectConnect is designed to integrate directly into existing cloud architectures, allowing audio access to become a native part of your processing pipelines.
Infrastructure
You provision and manage your infrastructure, including:
- Compute (CPU or GPU)
- Instance types and scaling
- Storage and lifecycle policies
- Supporting services and tooling
This ensures complete sovereignty over your code, processes, and resulting intellectual property.
Audio access
Audio access is enabled via our Catalogue Feed APIs.
These APIs provide:
- Track and catalogue identifiers
- Metadata required for processing
- Product availability based on your licensed rights
Using this data, your systems can directly resolve and access audio within your environment for fingerprinting - without requiring external delivery or intermediary APIs.
This enables tightly integrated, code-level access to audio as part of your processing workflows, whether via direct file paths or service-based requests.
Example access pattern
audio_path = resolve_audio(track_id, format)
process(audio_path)Audio is accessed natively within your environment, allowing it to be incorporated directly into high-performance processing pipelines.
Audio is made available in a range of formats suitable for fingerprinting workflows, from high-efficiency AAC encodings (such as AAC-HEv2-48) through to higher bitrate AAC-LC-256 formats, and up to high-fidelity, lossless audio where required.
Default formats are optimised for availability and processing efficiency, with higher fidelity options accessible based on your requirements and licensing.
Audio access & processing models
You can choose the processing model that best fits your compliance and infrastructure requirements:
- Stream-and-process - in-memory processing without storing files
- Download-and-delete - batch processing with controlled lifecycle
We work with you to align implementation with licensor requirements.
Security & rights enforcement
All access is governed by rights configured at the catalogue and partner level.
This ensures:
- Only licensed content is accessible
- Access aligns with contractual obligations
- Processing remains within approved environments
Cost efficiency
DirectConnect minimises data movement by enabling audio access directly within your environment.
This results in:
- Significantly lower access costs compared to hosted or external delivery models
- Reduced data transfer and storage overhead
- More efficient processing at scale
Benefits
DirectConnect is best suited for:
- Large-scale or continuous processing workloads
- Advanced workflows (GPU, serverless, hybrid compute)
- Cost-sensitive environments requiring optimisation
- Teams requiring full control over infrastructure and processing
APIs (In your environment)
Where the two solutions detailed above are not ideal, you can maintain your current environment and utilise our APIs to request assets. Asset request is a cost effective solution that requires minimal changes for your environment, often providing the fastest execution. Where using this process you will need to complete technical due dilegence in the handling and destruction of assets once fingerprinted.
Comparison Overview
Deployment model | Managed VM environment | Runs in your AWS environment | Runs in your current environment |
Setup speed | Ready for immediate integration | Designed for direct integration into existing workflows | Minimal setup - integrate our APIs |
Infrastructure control | Limited | Full control | Your infrastructure |
Compute flexibility | VM-based (CPU/GPU selection) | VM, GPU, serverless, custom workflows | Your infrastructure |
Audio access method | Instance-level endpoints callable from any application | Direct, code-level access within your environment | API, tokenised requests |
Data flow | Audio delivered per request | Audio accessed natively within your environment | Audio delivered per API request |
Storage model | Managed externally | Fully controlled (stream, temp, or persist) | Access Audio, Fingerprint, destroy audio |
Security model | Endpoint-based access control | Integrated rights enforcement within environment | Tokenised API requests |
Scalability | Limited to provisioned VMs | Native AWS scaling | Your infrastructure |
Performance | Dependent on request throughput | High - no external bottlenecks | Your infrastructure |
Cost Efficiency | Usage-based, scales with requests and data transfer | Significantly lower due to minimal data movement | Good but less efficient than the first 2 methods but less changes to any systems |
IP ownership | Processing in managed environment | Full ownership of code, workflows, outputs | Your infrastructure |
Best for | Quick start, simple pipelines | Advanced workflows, scale, optimisation | Minimal changes to your environment, full control |
On this page
- Fingerprinting