The challenge: same language, shared repertoire… different systems

🎯 The challenge: same language, shared repertoire… different systems

The collective management organizations (CMOs) of Ibero-America — such as SGAE (Spain), APDAYC (Peru), SAYCO (Colombia), SCD (Chile), AGADU (Uruguay), SADAIC (Argentina), among others — manage a repertoire that, in practice, crosses borders every single day.

Spanish-language music does not recognize geographical boundaries. A work created in Chile may be performed in Spain, Argentina or Colombia. A Uruguayan author may have digital exploitation across multiple Spanish-speaking territories. The repertoire is shared, the language connects, and consumption is transnational.

However, historically each society has managed its works data within its own internal systems, using its own data models, processes and update cycles.

The result?

• Complex synchronizations

• Periodic information exchanges that are not always fully consistent

• Difficulty in maintaining a shared, unified view of the repertoire

• Bilateral integrations that are hard to maintain

• And, in some cases, regulatory or technical governance frictions

The issue is not purely technological. It is organizational, operational and, ultimately, strategic.

🚀 The solution: a distributed master–node model

To address this challenge, we built Global Connector, a distributed software platform deployed within each of the societies participating in LatinNet, the network managed by LatinAutor to enable the sharing of musical works information across Ibero-America.

The idea was clear: not to replace local systems, but to connect them intelligently.

Master–node architecture

The model we adopted is a master–node synchronization system:

• Each society operates a local node (Global Connector Node) installed within its own infrastructure.

• This node acts as both a collector and publisher of works data from its internal system.

• At the center, a global engine operates as a master hub where the repertoire of all participating societies is consolidated.

• The central engine acts as an interconnection bridge between all parties.

This approach has several important technical implications:

• 🔁 Controlled and fully traceable synchronization between nodes and master

• 🧩 Data normalization and validation at a common consolidation point

• 🌍 Access to a shared repertoire without requiring multiple bilateral integrations

• 🔐 Preservation of data sovereignty for each individual society

Instead of having N integrations between N societies, the classic exponential growth problem, the model reduces complexity to a far more governable hub-and-spoke architecture.

Beyond technology: business impact

From a business perspective, the impact is even more significant.

1. Shared, accessible repertoire
   Societies can consult and cross-check information about works that are already being exploited in their territories. This reduces uncertainty, accelerates operational processes and improves the overall quality of rights management.

2. Integration with external systems
   The central engine becomes a single integration point toward third parties: digital platforms, international systems, regulatory tools or reporting workflows.

3. Shared regulatory validation and control
   Certain validation rules or compliance checks can be centralized, ensuring consistency in the application of technical or regulatory criteria.

4. Technical governance aligned with institutional governance
   LatinNet is not just a technological project; it is a regional collaboration network. The architecture had to respect that governance structure and actively support it.

Building something like this is not simply about deploying APIs. It requires a deep understanding of:

• How works lifecycle processes operate within each CMO

• What it truly means to “publish” a work

• How ownership conflicts are handled

• What level of latency is operationally acceptable

• And which regulatory risks simply cannot be assumed.

💡 What we learned (and why the CMO world fascinates us)

From our perspective, projects like Global Connector are especially compelling because they force you to move beyond purely technological thinking.

It is not enough to understand microservices, event queues or data replication (although all of that matters). You must understand the CMO business model itself:

• The sensitivity surrounding repertoire data

• The importance of trust between societies

• The weight of local and international regulation

• The need for traceability and auditability

• The delicate balance between autonomy and cooperation

Working within an environment like LatinNet has allowed us to deepen our understanding of how societies manage shared repertoire, and how technology can become a true enabler of collaboration rather than a source of friction.

It has also reinforced a strong conviction: in the field of collective management, technical architecture is a strategic decision. It defines how information flows, how trust is built, and how international cooperation scales.

When the repertoire is shared, the language connects and consumption is global, having an infrastructure that reflects that reality stops being optional… and becomes essential.