EU Sovereign Intelligence

Strohmann orchestrates the layer underneath the answer. Data arrives in a hundred incompatible shapes and leaves as one graph that decision makers and autonomous AI systems both read.

BaseLayerDataOrchestration

The engine reads sources through connectors, resolves them into nodes and edges, and shapes them to the ontology of a tenant.

Analysts, models and agents downstream all stand on a data layer that somebody had to assemble. In most shops that somebody is the customer, doing it by hand, once per question. Strohmann is that layer, and orchestrating it is the product rather than the reports you can write on top of it.

Four named parts, one engine

Buhne

The engine

Reads every source we have connected and turns the mess into one graph.

  • Each source gets its own connector, and runs when the publisher publishes.
  • When two records turn out to be the same company, we keep the reason why.
  • Adding a type or a relationship is a config change.

Brücke

The workspace

Where the work happens. You search a name and follow what it connects to.

  • Search finds the entity, not four spellings of it.
  • Under every connection: where it came from, and when.
  • Dossiers export with their citations attached.

Werft

The control room

Someone has to watch the pipeline. This is where that happens.

  • What each run wrote, what it skipped, and why.
  • How stale each source is, our read against the publisher’s.
  • Bad merges surface here first.

Tintenfisch

The deployment

Gets the software onto the machine and keeps it on the right release.

  • One wanted state per box, signed.
  • Boxes pull their release and report back what happened.
  • A bad rollout stops before it spreads.

One engine. Many tenants.

A tenant is an ontology and a set of connectors pointed at the same engine. Politics is a tenant, and readers mistake it for the company more often than they mistake anything else about Strohmann.

Sovereign infrastructure, auditable answers

Two questions decide whether you can trust an AI system with evidence: where the data lives, and whether you can check an answer. This page answers both, and neither answer is a setting.

  • On German servers, out of reach of the US CLOUD Act

    All of our data sits on German servers, and no US-controlled provider sits anywhere in the path. Both halves matter: the US CLOUD Act reaches data a US provider holds wherever in the world it is stored, so where the servers stand answers only half the question and who holds them answers the rest.

  • We are impartial

    We do not campaign, we take no side, and we sell no conclusion. We sell the evidence and the citation under it, and that is the same product whoever is asking.

  • A partial result says it is partial

    If your access is missing a source, the response says so. A shortened result never passes as a complete one.

  • The record keeps its own history

    Sources overwrite themselves and archive nothing. The graph keeps what a source said and when, and states its vintage as “as of <date>”.

Bring a question we cannot rehearse

The demo is the graph answering a question you brought, live, rather than a recording of one we picked.

Book a demo