The tool is a news hub especially for publishers and media houses. BRIXWIRE collects stories and assets from various sources (e.g. press agencies, CMS, planning, and editorial systems), transforms the content, and integrates it, ready to publish, into target systems like CMS, editorial, or DAM systems.
BrixWire works as a content hub that stores its news-oriented data in a media-neutral format. It provides a flexible and extensible data structure for searching the stories and assets it contains. The internal news format is not standardized or fixed and can be modified according to customer requirements.
Instead of a network model for the content. This simplifies installation, maintenance, migrations and testing. When a new input/output channel is connected, all previous input/output channels are immediately available for use.
We follow a strict plugin concept for components that contribute to customer requirements. Almost everything found within BrixWire is a plugin. Thus, authentication and authorization, access to assets via a DAM, inputs and outputs are also implemented as plugins.
It is possible to extend BrixWire to include custom views and automations or to integrate the functionality with other products.
BrixWire can be run on Windows, Linux systems or inside a Docker. It can be hosted on a stand-alone server, or on managed servers in the cloud, including parallel execution and failover mechanisms.
The core of BrixWire is a transformation engine capable of processing JSON and XML. This supports script extensions to realize specific use cases.
Import news from different types of sources and publish them with a few clicks. Stories can be searched with different criteria and published to different output channels, such as editorial systems or CMS.
"Publish First" is what is relevant. For BrixWire, it doesn't matter if a print-first or online-first approach is desired. You can simply define input channels and output publication mappings as you need them.
Using a scheduler and customer APIs, we can offer headless and fully automated publishing, i.e. without user interaction.
Easily connect offsite workstations for editors, such as home offices. BrixWire also enables collaborative work for multi-site distributed teamwork.
BrixWire can be used to connect or synchronize multiple editorial systems. It can be used, for example, for migration scenarios when changing providers.
BrixWire is also suitable for the transformation of content coming from publishing remote systems. Examples include transformation of structured recipe data into web or print articles or integration of office formats into the workflow.
By centralizing the use, ownership, and exploitation of content.
Moves data with the right latency via high-performance data pipelining.
Works with a high volume of users and data without performance degradation.
Is able to adapt to different needs by supporting new technologies, data types and platforms.
Headless and fully automated publishing is possible.
Publish existing articles with just a few clicks, rule-based publishing.