TVR
MOLDOVA
TVR MOLDOVA is the Republic of Moldova channel of the Romanian Television Society — one site in the national broadcaster's network. We engineered its entire digital platform end to end: DevOps, architecture, backend and frontend. Everything here is ours — the only piece we don't run is the live TV signal itself, which is fed from Bucharest.
Problem
& Solution
A public broadcaster's site is several products under one logo: a newsroom that never sleeps, an archive of shows like Telejurnal and Europa Azi, and a live channel — all expected to be instant on a phone. And it never stands alone: TVR MOLDOVA is one node in the Romanian Television Society's network, next to TVR 1, TVR 2, TVR 3, TVRi, the regional studios and Știrile TVR.
We engineered the whole thing end to end — DevOps, architecture, backend and frontend. A headless newsroom CMS (Superdesk) feeds an API-first delivery layer we built, so every article and show is just data, served the same way to the website and the apps. The single piece that isn't ours is the live TV signal, which Bucharest provides — we built the platform that wraps around it.
Heavy media — images, posters, galleries — lives on S3-compatible object storage behind a CDN, so a reader on a weak rural connection gets the same instant page as the capital. We own the pipeline from deploy to delivery; the newsroom publishes once and the platform does the rest.
News and television share one stage: the same grid carries a breaking story, on-demand episodes and the live channel. The live signal comes from Bucharest — we built the player and the experience around it, with shows available on demand.
TVR MOLDOVA is part of a wider family, so the top bar links out to its sibling channels — TVR 1, TVR 2, TVR 3, TVRi, the regional studios, Știrile TVR and TVR PLUS. Every block is event-driven and cache-friendly, so a spike around a live broadcast is a non-event for the infrastructure.
Live
& On Demand
Mobile First
Most of the audience arrives on a phone, so the phone got designed first. The reading experience, the live player and the show pages are built for thumbs and one-handed scrolling, then scaled up to the desktop — never the other way around.
Because the front end only ever talks to the API, the same content powers the website and the apps without a second editorial effort. One newsroom, every screen.