balu
Knowledge graph

Reliable answers start with reliable data.

CoreX holds locations, brands, products, services and contacts as linked objects, the verified source that publishers, local pages, posts and AI systems draw their information from.

Objects instead of form fieldsRelationships instead of duplicatesAvailable to publishers, pages and AI

Schematic excerpt of the field model, the product includes further fields.

A slowly rotating sphere of the field names CoreX tracks for a location, from address and opening hours through categories and services to reviews and sync status.
Benefits

What CoreX changes day to day

One model, many channels

What is maintained once is available everywhere, without copies that drift apart unnoticed.

Verified, not just collected

Required fields, value ranges and approvals make sure only verified details go out.

Reusable content

Service descriptions, images and text blocks exist once and are used per location.

Open interfaces

API, webhooks and exports make the records usable for your own systems, outside Balu too.

Reuse

Maintained once, used in many places.

One record in CoreX becomes the location page, the post and the publisher profile. The information is not copied but used, which is why it cannot drift apart.

From record to postDone
Workflow stepsStep 5/5
CoreXLocation, service and media are verified and ready
DraftAssistant suggests text and image per location
ApprovalHead office reviews, the location adds local detail
PublishingSocial channels and publisher profiles
AnalysisReach and reactions per location in Measure
Total steps5
Completed5done
Remaining0
Process with sample content, approval paths are configurable per account.
Features

In detail

Objects and relationships

Brand, location, service, product, review, contact, linked, versioned and with valid-from dates.

Field control

Which fields are set centrally and which the location may maintain itself.

Media library

Images assigned to brand, location or service; formats for each publisher.

Structured output

Schema.org-compliant data for local pages and machine-readable sources for AI systems.

How it runs

How the module goes live

  1. 01

    Define the model

    Which objects and fields your organisation keeps, standard or extended.

  2. 02

    Take over the records

    Import from existing systems, merging of duplicates.

  3. 03

    Set the rules

    Required fields, approvals and ownership per level.

  4. 04

    Distribute

    Modules and interfaces read the same records.

How it fits together

Works with the rest of the platform

CoreX draws its data from the same source as every other module, and returns its results there.

  • Discover: Distributes the objects to the publisher network.
  • Connect: Uses services and media for posts.
  • Your own systems: API, webhooks and exports.
1Source for all locationskeine parallelen Listen mehr
7Objekttypen im Standardmodellextendable per organisation
APIAccess for your own systemsread and write

See CoreX on your own example

In the demo we work with one of your locations, including a check of its current data.