Client Integration Hub where client systems connect to the platform

Very few clients arrive with nothing. There is usually an archive, a scheduling system, a set of feeds and a workflow the whole organisation depends on. Replacing all of it at once is rarely realistic, and rarely necessary.

The problem is narrower than that: the data inside those systems is often incomplete, inconsistent or ageing, and the workflow around it is hard to change. What most teams actually need is a way to enrich and correct what they already hold, and to keep their existing tools fed, without a rebuild.

The Client Integration Hub exists for exactly that. It is the layer that connects your infrastructure to the platform, so our data and technology meet you where you are instead of asking you to move to us.

Integration runs as a round trip, not a one-way import:

1. 01
   Connect We set up secure connectivity to your sources and archives, with the credentials and connectors each system needs.
2. 02
   Bring your data in Your catalogues and records enter the platform and are normalised into one consistent structure, the same way any other source is.
3. 03
   Standardise and enrich Inside the platform, your records are matched to master titles, given permanent IDs, and enriched with cast, synopses, genres, ratings and images through Harmonization & Enrichment and the Media & Image Hub.
4. 04
   Send it back The result returns to your systems in your format, through Metadata & Media Delivery, ready to feed the tools you already use.

Under the surface, the Hub reuses the platform's own ingest, enrichment and delivery capabilities. What makes it a module in its own right is the direction of travel: it is built around your data and your systems, not ours.

You should not have to re-engineer your systems to read our output. Data comes back in the shape your tools expect:

• custom XML or JSON structures mapped to your customer-native format
• your own vocabulary and code lists, translated to the terms your systems already use
• delivery over the channel you already run: SFTP, SCP or FTP, Amazon S3, Azure Blob Storage, SharePoint, a REST or SOAP endpoint, email, or a Kafka topic

Every integration runs with separate test and production environments and can be rolled out in stages, so you validate against real data before anything touches your live systems. When something needs correcting, the fix is re-delivered through the same path.

Connecting a system is a defined process, run with you rather than handed over:

1. 01
   Technical analysis of your source and format
2. 02
   Connectivity setup
3. 03
   Connector and mapping development
4. 04
   Editorial linking and enrichment initialisation
5. 05
   Activation to production

How long each step takes depends on how complex your setup is: a familiar format on an established feed moves quickly, a new data model that needs editorial linking takes more time. What stays constant is the path itself. It is one we have run many times, so the work is structured and predictable rather than exploratory, and you get a named point of contact and full visibility into progress from first analysis through to activation.