Building Digital Infrastructure for Europe's Cultural Sector

Introduction

Europe's cultural sector is, by any conventional measure, an unlikely candidate for digital transformation leadership. Its organisations range from single-person production companies to centuries-old national institutions. Its workflows are bespoke, its funding structures complex, and its appetite for technology procurement historically cautious. Yet the sector is under mounting pressure to modernise its digital infrastructure — from funders demanding richer data, from audiences expecting seamless digital experiences, and from the operational reality that paper-based and siloed systems are no longer viable at the scale and speed that contemporary cultural activity demands.

The European Commission's Digital Decade policy programme sets ambitious targets for the digitisation of public services and the economy by 2030. While cultural organisations are not always explicitly named in this framework, they sit squarely within its scope — as recipients of public funding, employers of creative and administrative workers, and providers of cultural services to European citizens. The gap between the Digital Decade's ambitions and the current IT reality in much of the cultural sector is significant, and closing it will require both investment and better tools.

This article examines the specific infrastructure challenges facing European cultural organisations, the architectural principles that underpin effective responses, and what the emerging generation of purpose-built cultural technology platforms can and cannot accomplish.

The Legacy Problem

Legacy systems in the cultural sector come in several distinct forms, each presenting different migration challenges. The most pervasive is the accumulation of disconnected point solutions: a festival management system purchased a decade ago that does not export usable data; a grants management tool that predates API-based integration; a ticketing platform that holds valuable audience data behind a proprietary interface with no standard export. None of these systems is technically "broken" — which is precisely why they persist. The business case for migration requires demonstrating not just that a new system is better, but that the migration itself is worth the disruption, cost, and risk.

A second category is the custom-built internal system: the Access database or bespoke PHP application developed years ago by a staff member who has since left the organisation, now maintained by institutional inertia and the fear that replacing it will surface hidden dependencies. These systems often contain genuinely valuable data structures that reflect accumulated operational knowledge — but they are impossible to integrate with modern tools without significant reverse-engineering effort.

Third, and particularly common in broadcasting and archival contexts, are platform-specific formats: proprietary media asset management systems, broadcast automation platforms with closed data models, and archival management tools that use standards from previous decades. European public broadcasters and national archives sit on enormous digital collections that are, in practice, inaccessible for analytical or distribution purposes because the systems that hold them cannot communicate with modern data infrastructure.

The consequences of this fragmentation extend beyond operational inconvenience. When a funded organisation cannot easily aggregate data across its own systems — ticketing, CRM, social, project management, financial — it cannot demonstrate impact to funders, cannot serve its audiences with the personalised experiences they expect from digital media, and cannot make evidence-based programming decisions. Legacy infrastructure is thus both a symptom and a cause of the cultural sector's persistent underinvestment in digital capability.

Interoperability & Data Standards

The cultural sector has, over several decades, produced a reasonable set of data standards for specific domains. MARC and BIBFRAME for bibliographic data, EBUCore and PBCore for broadcast media, Dublin Core for general metadata, and more recently the International Image Interoperability Framework (IIIF) for digitised cultural assets. These standards exist precisely because interoperability problems were identified and addressed by communities of practice.

The problem is adoption. In practice, even organisations that nominally use these standards implement them inconsistently — using custom fields, non-standard vocabulary terms, or partial implementations that pass validation but fail to interoperate in practice. The result is that two European film funds using the same metadata standard for their project databases may still be unable to exchange data automatically, because their implementations diverge at the level of controlled vocabulary, date formats, or identifier schemes.

The European Commission's Cultural Heritage Cloud initiative and the ongoing work of Europeana on aggregation and metadata harmonisation represent the most sustained European-level effort to address this. But these initiatives focus primarily on the heritage and memory institution sector. The performing arts, film, and contemporary cultural sectors have less developed interoperability infrastructure, and the commercial pressures on organisations in these sectors create weaker incentives to invest in standards compliance.

For technology providers building in this space, the practical implication is that any platform claiming to integrate with existing cultural sector infrastructure must be prepared to handle significant data heterogeneity. This means building flexible ingestion pipelines, investing in data mapping and transformation tooling, and designing data models that can accommodate the full variance of real-world cultural sector data rather than assuming clean, standards-compliant inputs.

Cloud-First Architecture

The case for cloud infrastructure in the cultural sector rests on several pillars that are now well-established: lower capital expenditure, automatic scaling for peak-load events like festival submission deadlines or broadcast of major cultural events, geographic redundancy for disaster recovery, and access to managed services for AI, storage, and search that would be prohibitively expensive to operate independently.

However, "cloud-first" in the cultural sector context requires careful qualification. Data residency requirements vary by member state, and some categories of cultural data — particularly personal data of artists and applicants processed under public mandate — may face constraints on transfer outside the EU. This makes multi-region European cloud deployment not merely a performance optimisation but a compliance requirement. Major cloud providers have substantially expanded their European region footprint in recent years, which has reduced but not eliminated the complexity here.

A modular SaaS architecture offers particular advantages for cultural organisations with limited IT staff. Rather than deploying monolithic platforms that require significant configuration and ongoing maintenance expertise, modular systems allow organisations to adopt the components they need — submission management, programme planning, distribution tracking, financial reporting — independently, and to integrate them through well-documented APIs. This incremental adoption model also reduces the risk of any single implementation failure disrupting the entire organisation's operations.

Bergman Coding's product suite is built on this principle. Festival AI, for example, can be deployed as a complete festival management platform or as individual modules — submission intake, jury management, programme scheduling, accreditation — that integrate with a festival's existing systems. FC Distribution similarly operates as both a standalone distribution management platform and as an API-accessible service that can connect to existing rights management or theatrical booking systems.

Security & GDPR

Cultural organisations process significant quantities of personal data: audience members, subscribers, applicants, artists, grant recipients, accredited professionals. For organisations that have historically operated with limited IT governance, the GDPR compliance obligations introduced in 2018 — and increasingly enforced as the initial grace period has ended — represent a genuine operational challenge.

The cultural sector's data protection challenges are in some respects more complex than those of commercial organisations. Film festivals process passport and payment data for hundreds of accredited professionals. Cultural funds hold sensitive financial and organisational data about applicant organisations and their principals. Public broadcasters hold archives of personal data about artists, contributors, and audience members stretching back decades, predating any coherent data governance framework.

Effective data architecture for cultural organisations must embed privacy-by-design principles at the system level rather than treating compliance as a documentation exercise. This means data minimisation in collection forms, automated retention and deletion workflows, clear data processor agreements for all third-party integrations, and access controls that enforce the principle of least privilege. It also means building systems that can respond to data subject access requests without requiring manual database queries — a capability that many legacy systems simply do not have.

The NIS2 Directive, which expanded the scope of cybersecurity obligations across the EU and took effect from October 2024, adds another layer of consideration for larger cultural institutions. National museums, major broadcasters, and significant cultural infrastructure providers may fall within NIS2's scope depending on their classification and size thresholds. The directive's requirements around incident reporting, business continuity planning, and supply chain security are new obligations for many cultural sector IT teams.

Case Studies: Festival AI and FC Distribution

Festival AI addresses one of the most operationally complex recurring challenges in the cultural sector: running a film festival. The submission-to-screen workflow involves hundreds or thousands of inbound films, multiple rounds of selection, a jury management process, a programme scheduling and publication task, accreditation management for press and industry, and post-festival reporting — all compressed into a cycle that repeats annually with a small permanent team.

The infrastructure challenge here is not primarily about scale — most European festivals are not processing millions of records — but about integration and workflow coherence. Data entered at submission needs to flow through to selection tracking, then to programme scheduling, then to catalogue publication, without being re-entered at each stage. Jury members need secure, accessible interfaces that work on mobile devices and do not require them to install software. Press and industry accreditation needs to connect to access control systems at the venue.

Festival AI approaches this by modelling the complete festival workflow as a connected data system from the outset, rather than treating each function as a separate application. The result is that information captured once — at submission, at registration, at selection — is available throughout the system without manual transfer, and the audit trail that reporting requires is built into the process rather than reconstructed after the fact.

FC Distribution addresses the distribution side of the film value chain: how rights holders and distributors manage the movement of film and television content across platforms, territories, and formats. This is a domain with acute interoperability challenges — every major streaming platform, broadcaster, and theatrical distributor uses different technical specifications, delivery formats, and metadata schemas. Managing a catalogue of European films across a dozen platforms simultaneously requires either a dedicated technical team or a platform that abstracts this complexity.

The infrastructure task here is partly about format and metadata transformation, but also about contractual and rights data management. Distribution agreements are complex documents with territory, format, exclusivity, and window provisions that must be tracked precisely to avoid rights conflicts. FC Distribution models these contractual structures alongside the technical delivery workflow, creating a single source of truth for both what a rights holder is permitted to do and what they have actually done.

The Road Ahead

Several trends will define digital infrastructure development in the European cultural sector over the coming three to five years. The continued expansion of streaming and digital distribution channels will increase the data volumes and integration complexity that distribution-facing tools must handle. The growth of hybrid physical-digital events — accelerated by the COVID period and now a permanent feature of the festival and performing arts landscape — creates new infrastructure requirements around live streaming, digital access ticketing, and remote participation management.

The EU's Data Governance Act and the proposed Data Act create a policy framework that could, if implemented effectively, improve the availability of data from public cultural institutions for research and secondary use. This would benefit tools that aggregate and analyse cultural data across organisations — but only if the underlying systems can support the access and exchange mechanisms that the legislation envisages.

Perhaps most significantly, the consolidation of the cultural tech market is likely to accelerate. The current landscape is characterised by many small, specialised tools with limited integration between them. Pressure from funders for richer data, from GDPR for proper data governance, and from organisations themselves for reduced operational complexity will favour platforms that offer broader functionality with genuine interoperability over point solutions that address single workflow problems in isolation.

For cultural organisations navigating this landscape, the strategic priority is clear: avoid vendor lock-in, insist on open APIs and standard data formats, and invest in the data governance infrastructure — policies, roles, and processes — that makes technical systems usable and compliant. The technology is increasingly capable. The limiting factor, in most cases, is organisational readiness to use it well.