We publish. We build.
Same people, same week.
Most companies pick one. Agencies build for publishers without ever having published. Publishers hire out the engineering and hope it fits.
We think that split is why so much media software is bad.
So we run both sides. We make editorial and film work. We build the platforms it lives on. We write the language technology that makes Arabic findable. And we publish products of our own, on the same stack we sell.
Five practices
Take one. Take all five. Advisory comes first either way, and sometimes it's the whole job.
ADVISORY
Most media problems aren't technical.
They're decisions nobody made. Two desks doing the same work. A platform someone is selling you hard. A budget approved before the problem was defined.
We read the workflow, not the org chart. We talk to the people inside it. Then we write down what we'd do, with the alternatives, so you have something to argue with.
Technology audits · platform selection · editorial and product strategy · audience definition · workflow and org design · AI governance · transformation roadmaps
Sometimes the recommendation is don't.
EDITORIAL
We're journalists before we're anything else.
Reporting, editing, investigations, long-form, data journalism. That part is straightforward.
The part people skip is the standards. Style, sourcing, corrections, transliteration, how dates get written, what a format actually is. Boring work. It's the difference between a newsroom that runs and one that runs on whoever's awake.
A format isn't a template. It's an agreement about length, structure, sources and what "finished" means. Get it right and a new writer is useful on day one.
PRODUCTION
Made once. Used for years.
Documentary, video series, podcasts, live coverage, interactive stories, publications.
Everything ships with transcripts, timecodes, structured metadata and source assets in order. Not because it's tidy. Because a film nobody can cut, translate or find again is a film you paid for once and own briefly.
ENGINEERING
Your team should work inside the system, not around it.
If your editors coordinate on WhatsApp because the CMS is slower than talking, the CMS lost.
Arabic is built in rather than bolted on, which shows up in the places it usually breaks: search, fonts, diacritics, dates, numerals.
News sites · CMS builds and migrations · design systems · internal tools · integrations · data pipelines · subscriptions, membership and local payment
We document it. You should be able to fire us.
APPLIED AI
Arabic is a separate market in the eyes of a machine.
Answer engines don't translate. They retrieve and rank per language. Ask the same question in Arabic and in English and you get different sources, different rankings, different companies. Most Arabic publishers appear in neither.
That's not a translation problem. It's a different index, and it's being built right now.
We work on getting material into it. Structured data and entity layers. Unified transliteration, so one person isn't five people to a machine. Search that normalises hamza, taa marbuta, yaa and alif maqsura, handles diacritics and prefixes, and understands broken plurals.
Speech-to-text and diarisation · knowledge graphs · recommendation · archive OCR on Arabic script · AI policy and training
WE PUBLISH TOO
Our proof isn't a client list.
We build and run our own media products. Same architecture, same tools, same language technology we sell.
It means we've already made the mistakes, on our own money, in production. It means we know what a thing costs to run and not just to build. That second number is where most media projects die.
Working with us
Same practice, wildly different sizes. An archive job might be a three-week inventory, an eight-month platform, or a team processing five thousand items a month for a year.
We work with newsrooms, broadcasters, institutions and independent publishers, in Arabic and English.
Send us the problem, not the brief.