Core infrastructure · Layer 2Äther

The semantic layer above your IT.

Äther does not replace systems. Äther understands what you already have — and turns it into a harmonised, explainable and sovereign data foundation. Data stays where it originates. What changes: it is connected, semantically understood and usable with an audit trail.

TypePlatform layer — carries all modules (Atlas, Socius, Chronos, Custom)
Building blocksConnectors, ontology, Cortex, pipelines, audit, sovereignty
FoundationOpen-source stack, EU-sovereign, aligned with BSI C5 & EU AI Act
02 — CORE PRINCIPLE

Data stays where it originates. Äther places a semantic layer above it — and turns distributed systems into a shared truth.

03 — THE 6 BUILDING BLOCKS

Six components, one layer.

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

/ 01 — CONNECTORS

Connect instead of replicate

Standardised adapters to GIS, ERP, logs, sensors, OSINT, public-authority APIs. Data is referenced, not copied — source and target systems keep their sovereignty.

/ 02 — ONTOLOGY

Shared language

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

/ 03 — CORTEX

Inference & models

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

/ 04 — PIPELINES

Flux — orchestrated data flows

Declarative pipelines tie sources, models and outputs together. Versionable, testable, repeatable — from pilot to regular operation without a break.

/ 05 — AUDIT TRAIL

Every statement traceable

Per inference: which source, which model, which confidence, which point in time. Aligned 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 stay yours. No telemetry, no US-cloud dependency, no black-box vendor lock-in.

SCHEMATIC · ARCHITECTURE
LAYER 1 · MODULES
Atlas
Socius
Chronos
Custom
LAYER 2 · ÄTHER · 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
Sensors
OSINT
Authority API

Layer diagram: source systems stay in your control, Äther connects and understands, modules deliver use cases. Schematic — the actual topology depends on your environment.

04 — IN USE

The building blocks, as you operate them.

Two examples from the live instance: the ontology module, in which data classes, properties and relationships are modelled without code — and the Flux dashboard, which makes every pipeline run, every source and every status traceable.

ONTOLOGY · A-BOX BUILDERPRODUCT VIEW
Äther — ontology editor with class hierarchy and properties
Class hierarchy, properties, relationships — model instead of program.Ontology
FLUX · ORCHESTRATORPRODUCT VIEW
Äther — Flux dashboard with pipeline runs, status and sources
Every pipeline run with status, duration and source — auditable in detail.Flux
04 — Security & sovereignty

Sovereignty is not a feature. It is the basic assumption.

  • LocationDevelopment, operation and hosting in Germany.
  • HostingOn-premise, private cloud or European PaaS — your choice.
  • ComplianceAligned with BSI C5, EU AI Act, ISO 27001 auditing.
  • Open sourceCore infrastructure on an open basis — no black-box lock-in.
  • TelemetryDisabled by default. No data leaves your perimeter.

A semantic layer above your IT — in 6 weeks.

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