Solution

News Agency Infrastructure

An agency’s product is the copy itself. The stack’s job is to produce it on time, archive it and deliver it cleanly to the other side.

A news agency differs from a news site in two ways. First, distribution: the copy appears not only on its own site but inside subscribers’ systems. Second, copyright: unauthorised use of that copy is a direct loss of revenue.

So two things come to the fore in the build: the software’s REST API and webhook interface, which lets the feed go out, and keeping the archive and publication timestamps on the record. The second is your most concrete evidence in an unauthorised republication claim.

Who It Is For

Organisations that supply the copy they produce to other publications.

Subscription-based agencies

Agencies that supply subscriber publications under contract.

Regional and thematic agencies

Outfits focused on one region or field, producing narrowly but regularly.

Photo and video agencies

Organisations producing and licensing stills and video, where copyright dominates.

In-house newsrooms

Structures feeding several publications inside a group from one central desk.

What the Build Includes

Production, distribution and archiving are three separate needs, and the build covers all three.

Who Carries Which Duty?

On the agency side the weight falls on copyright and attribution. The infrastructure produces evidence; it does not defend the right.

DutyWhat the infrastructure providesWhat stays with the organisation
Proving publication timePublication records, action history and timestamps carried in backups.Using those records as evidence and pursuing the matter legally.
Pursuing unauthorised republicationAccess for archive comparison and a record of the publication date.Establishing the breach, sending notice and running the case.
Subscription contractsNothing. The feed is delivered technically; the scope of the right is set in the contract.Defining and policing the terms of use in the contract.
AttributionA source field in the story that travels with the feed.Setting the attribution policy and following it up with subscribers.
Editorial payroll and press cardsNothing. Staffing is an employment matter.Written contracts under Law 5953 and the quota application.
Protecting sourcesRole-based access and limits on unauthorised viewing.Deciding who may know the source, and the legal position taken.

This table is not legal advice. Work with your legal adviser on the copyright and contract side.

Further Reading on the Regulatory Side

Copyright and attribution are the heart of agency work. These articles look straight at it.

Frequently Asked Questions

How is the feed delivered to subscribers?
Through the software’s REST API and webhook interface. Which subscriber receives which content and in what format is configured during setup. We do not promise an off-the-shelf subscriber portal; we listen to what you need and decide together what gets built.
How do I prove my copy was used without permission?
Publication records, action history and backups show the moment of first publication. That is the technical evidence; establishing the breach, sending notice and litigating sit on the legal side. The articles above cover it.
Will an agency have a press card quota?
The quota depends on the organisation’s characteristics and its payroll, and varies by publication type. Our calculator shows where you stand, but making the application and meeting the staffing conditions is down to the organisation.
Can we run it on our own server?
On the Enterprise plan, yes. On the other plans the software runs managed on KEYDAL infrastructure.
Is there room for our photo and video archive?
On the image side there is WebP and AVIF conversion with automatic resizing; for video and large archives we plan disk on the cloud server side. Talking through the archive size up front is the safest route.

Let Us Build Your Feed Together

Let us talk about how many subscribers you supply, in what format and how often, and plan the build around it.