Core infrastructure · Layer 2 Aether

The semantic layer above your IT.

Aether doesn’t replace systems. Aether understands what you already have — and turns it into a harmonized, explainable, sovereign data foundation. Data stays where it is created. What changes: it becomes connected, semantically understood, and usable with an audit trail.

Type

Platform layer — carries all modules (Atlas, Socius, Chronos, Custom)

Building blocks

Connectors, ontology, Cortex, pipelines, audit, sovereignty

Foundation

Open-source stack, EU-sovereign, compatible with BSI C5 & EU AI Act

02 — CORE PRINCIPLE

Data stays where it is created. Aether lays a semantic layer on top — and turns distributed systems into a shared truth.

03 — THE 6 BUILDING BLOCKS

Six components, one layer.

Each building block can be used in isolation — but together they form the backbone that Atlas, Socius, Chronos and your own applications run on.

/ 01 — CONNECTORS Connect instead of replicate

Connect instead of replicate Standardized adapters to GIS, ERP, logs, sensors, OSINT, government APIs. Data is referenced, not copied — source and target systems retain control.

/ 02 — ONTOLOGY A shared language

A domain-sharp world of terms (actor, place, event, time) translates between source systems. Without ontology, every analysis remains just an Excel list.

/ 03 — CORTEX Inference & models

ML and rule engines with model registry and confidence tracking. Inferences run on your infrastructure — no data leaves your scope.

/ 04 — PIPELINES Flux — orchestrated data flows

Declarative pipelines bind sources, models and outputs together. Versioned, testable, repeatable — from pilot to operations without a break.

/ 05 — AUDIT TRAIL Every statement traceable

Per inference: which source, which model, which confidence, which timestamp. Compatible with the EU AI Act, BSI C5 and internal compliance requirements.

/ 06 — SOVEREIGNTY You remain the owner

On-premise, private cloud or European PaaS. Data, models and audit logs remain yours. No telemetry, no US-cloud dependency, no black-box vendor lock-in.

SCHEMATIC · ARCHITECTURE
LAYER 1 · MODULES
Atlas
Socius
Chronos
Custom
LAYER 2 · AETHER · SEMANTIC BACKBONE
/ 01
Connectors
/ 02
Ontology
/ 03
Cortex
/ 04
Flux
/ 05
Audit trail
/ 06
Sovereignty
SOURCE SYSTEMS · STAY WHERE THEY ARE
GIS / Maps
ERP / Master data
Sensors
OSINT
Government API

Layer diagram: source systems remain under your control, Aether connects and understands, modules deliver use cases. Schematic — the actual topology depends on your environment.

04 — IN PRACTICE

The building blocks, how you operate them.

Two examples from the running instance: the ontology module where data classes, properties and relationships are modeled without code — and the Flux dashboard that makes every pipeline run, every source and every status traceable.

ONTOLOGY · A-BOX BUILDER PRODUCT VIEW
Class hierarchy, properties, relationships — model instead of code. Ontology
FLUX · ORCHESTRATOR PRODUCT VIEW
Every pipeline run with status, duration and source — auditable in detail. Flux
04 — Security & sovereignty

Sovereignty isn’t a feature. It’s the baseline assumption.

Makor is built in Germany and runs where you need it — on your own hardware, in a private cloud or on European PaaS. Every component is built so that data, models and audit logs remain within your scope.

  • Location Development, operations and hosting in Germany.
  • Hosting On-premise, private cloud or European PaaS — your choice.
  • Compliance Compatible with BSI C5, EU AI Act, ISO 27001 auditing.
  • Open source Core infrastructure on an open foundation — no black-box lock-in.
  • Telemetry Disabled by default. No data leaves your perimeter.

A semantic layer above your IT — in 6 weeks.

We start with two or three sources and a clearly defined use case. You keep data, models and audit logs.