Content delivery
From your newsroom
to your readers
We deliver news, images and digital editions through our own servers and content delivery network. We build the software your readers use and run the infrastructure behind it.
Talk to usKeep publishing.
We’ll keep it moving
Our delivery network has had no service outages since its launch in 2020.
We use multiple data centres, internet connections and storage locations. If one component fails, the service keeps running.
Traffic is rerouted automatically
Automated checks monitor our delivery servers. If a server stops responding correctly, we withdraw its route and anycast routing directs requests to other servers. The address readers use stays the same.
Three copies of your content
Our object storage keeps three copies of your content on servers in Helsinki and Stockholm. Your content stays safe if a machine or disk fails.
Ready when
the big story breaks
When a big story breaks or a new issue goes live, readers arrive together. Our network has the bandwidth to deliver your content and the capacity to handle the surge in requests.
We cache content close to readers. A popular photograph can be served again and again without fetching it from the original storage each time.
We run our own routers and connections to other networks. Our team in Finland manages the service, with servers across Europe and North America.
- Hundreds of gigabits per second
- The combined capacity of our transit and peering connections.
- Hundreds of thousands of requests per second
- The combined request capacity of our edge servers. Opening a single news page can generate several image requests.
Transit and peering
Peering connects two networks directly. Transit provides routes to the wider internet.
From storage to screen
Some servers store content; others deliver cached copies close to readers. Our image service creates the crops and sizes each layout needs, and the network delivers them to the reader’s app or browser.
In practice · Richie Editions
Start reading while
the rest downloads
Readers can open the first pages while the rest of an issue downloads. Once downloaded in the app, the issue is available offline.
Our servers in Finland receive and process your PDFs. The reader’s device uses the processed content to draw each page.
How a finished issue reaches the reader
- 1 · SourceFinished pages.
The publisher’s PDFs arrive for processing.
- 2 · PreparationReady for the screen.
Text, images and graphics are prepared for reading.
- 3 · DeliveryDelivered through our network.
Servers and caches deliver the issue to readers.
- 4 · ReadingThe first pages open.
Reading starts while the download continues.
One team can follow the whole journey
If a reader has to wait, we can trace the delay through content processing, the delivery network and the app. We develop all three and control where and how our servers run.