Genix News

We don’t publish release notes. We publish milestones.

630product changes
9changes in what a newsroom can do

We could show you a changelog of several hundred items: new fields, integrations, steps, models, settings.

But a product does not grow by entries in a changelog.

It grows in moments — when a newsroom can suddenly do something it could not do yesterday.

Turn a news item into a finished piece in one run. See the News Day board before editors sort through topics by hand. Send one story to the site, Telegram and social at once. Produce voice-over and video without a separate production unit. Plug in a live broadcast as a source. See what every run actually costs.

That is how Genix grew from a first AI pipeline into a production system for the newsroom.

These are the nine milestones of that road.

News came in. A finished piece came out.
Before this, AI helped the editor in separate pieces. Here, for the first time, there was a whole route.
Genix takes a source, turns it into a piece, checks the facts, writes the headline and carries the result through to publication.
Not five tools. Not five prompts. One run.
What became possible:
- automatic rewrite to the newsroom’s own standard;
- fact-checking inside the process;
- a headline and a finished piece with no manual copying between services.
Pipeline:
1. Source
2. Rewrite
3. Fact-check
4. Headline
5. CMS
This is where Genix stopped being a set of AI features and became a production route.
The newsroom no longer starts its day from a blank screen.
The next question was obvious: if Genix can already process a news item, why should an editor have to search by hand for where to begin?
The News Day board appeared.
The system gathers the feed, groups events, scores the material and puts in front of the newsroom what deserves attention.
Now the work can start not from dozens of tabs, but from a ready board.
What became possible:
- gather news in one workspace;
- score and prioritise topics;
- launch the right pipeline straight from the News Day board.
Pipeline:
1. News feed
2. Analysis
3. Priority
4. Editor’s pick
5. Production
One story. Every channel.
Publishing a piece on the site is only half the job.
Then come Telegram, social networks, other platforms, other formats — and a few more minutes of manual work on every piece.
So delivery became part of the pipeline itself.
One story can travel all the way to the audience with no copy-paste between systems.
What became possible:
- publishing directly to the CMS;
- automatic preparation of versions for different channels;
- delivery of content to Telegram and social platforms.
Pipeline:
1. Piece
2. CMS
3. Telegram
4. Social
The studio moved into the pipeline.
Text stopped being the end point.
Genix learned to turn the same piece into a cover, a voice-over and a video.
No new brief. No handing the piece over to another team. No starting from scratch.
One editorial story became raw material for several formats at once.
What became possible:
- generate covers;
- create a voice-over of the piece;
- assemble a video format from finished text.
Pipeline:
1. Story
2. ArticleCoverAudioVideo
AI stops where the editor begins.
Full automation sounds beautiful in presentations.
In a newsroom it often sounds frightening.
So Genix got something more important: controlled automation.
The newsroom itself decides where the pipeline runs on its own — and where it must stop, show the result to a person and wait for a decision.
What became possible:
- place approval points anywhere on the route;
- edit the AI result before the next step;
- pass a decision or extra data from the editor into the pipeline.
Pipeline:
1. AI
2. AI
3. Editor
4. AI
5. Publish
Not editor out of the loop. Editor exactly where it matters.
A new pipeline no longer starts with a ticket for a developer.
As soon as newsrooms started building more routes, one thing became clear: they cannot be programmed by hand every time.
That is how the builder appeared.
On an open canvas you assemble the production process from steps, conditions and sub-pipelines — much the way a newsroom would draw it on a whiteboard.
Except this process then actually runs.
What became possible:
- build routes visually;
- add conditions and branches;
- reuse ready-made sub-pipelines inside more complex processes.
Pipeline:
1. Source
2. Condition
3. Route ARoute B
4. Delivery
The broadcast ended. The content has only begun.
Text, RSS or a web page are far from all of a newsroom’s sources.
An enormous amount of content is born live.
So live came into the Genix pipeline.
A broadcast turns into a transcript, the transcript into a structured piece — and from there the same routes the newsroom already uses for ordinary sources take over.
What became possible:
- work with live broadcasts;
- get a transcript automatically;
- launch articles, short formats and other editorial scenarios from it.
Pipeline:
1. Live
2. Transcript
3. Editorial AI
4. Publish
Every run got a price.
AI looks cheap while you use it one request at a time.
At newsroom scale the bill is already made of tokens, images, voice-over characters, video seconds and hundreds of runs.
So Genix started counting more than content.
It started counting production.
What became possible:
- see the AI spend for every run;
- set quotas;
- analyse the volume and cost of individual routes.
Pipeline:
1. Run
2. AI services
3. Cost
4. Statistics
And for the first time the question “what does this process cost us?” can be answered with a number.
Genix stopped being a place you enter alone.
When a large share of the newsroom’s work passes through the system, one list of runs is no longer enough.
You need a space where the team sees the topic, the material, the statuses, the AI and each other’s decisions.
That is how the next level appeared: shared production work around a topic.
What became possible:
- gather the work around one topic;
- work alongside an editorial AI chat;
- see the team’s statuses, runs and results in one place.
And this is where individual pipelines start to come together into the newsroom’s system of work.

This is not a roadmap. It is the road already travelled.

630 product changes could be shown as a table.

We chose to show them differently: how one route became nine new things a newsroom can do — and how, step by step, Genix is turning into the production layer between the source and the audience.

The next milestone will appear here not when we change a version number.

It will appear when a newsroom can do something it cannot do today.

Want to see what route could be built for your newsroom?

Book a call

Genix News

News came in. A finished piece came out.

The newsroom no longer starts its day from a blank screen.

One story. Every channel.

The studio moved into the pipeline.

AI stops where the editor begins.

A new pipeline no longer starts with a ticket for a developer.

The broadcast ended. The content has only begun.

Every run got a price.

Genix stopped being a place you enter alone.