Skip to content

Architecture

Target architecture

This is the architecture Axiom Logic is being built to. It is a target, shown whole, with the state of every part. A part marked Built and live is running today. Every other part says how far it has got. Nothing here is a claim that a part is finished unless its mark says so.

As of 15 October 2026 · revision 17

Opens the document register for this mark

Each part is counted once, at its current mark. Percentages show shares of all parts, not completion.

L0 to L7 are this architecture's own layer numbers, counted from the plant upwards. They are not the levels of the Purdue reference model used for plant networks; the second diagram shows how the two line up.

Mark

The architecture, layer by layer

Data flows upwards.

L7 People and interfaces

where a person sees it, on site and away from it

On a screen at the site and anywhere else, through axiomlogic.ai.

read-only views · no control of plant from any screen

5 out of 5 started

  • Specified3
  • Being built2

the same figures on every surface, each with its basis

L6 Delivery

every surface shows its basis

In the cloud. Reference level 5.

11 out of 11 started

  • Specified7
  • Being built3
  • Built and live1

surfaces show statements, never a guess

L5 Proof

checkable without trusting us

In the cloud. Reference level 5.

4 out of 4 started

  • Specified3
  • Built and live1

every result or refusal becomes a statement

L4 Truth engines

one governed answer per question

In the cloud. Reference level 5.

7 out of 7 started

  • Specified5
  • Being built2

raw readings 90 days · rollups are the 7-year record

L3 System of record

append-only, nothing overwritten

In the cloud. Reference level 5.

5 out of 5 started

  • Being built5

strict format or a declared profile · receipt per message · held until declared · each day's receipts sealed and chained

L2 Ingest

fail closed, a receipt for every envelope

In the cloud. Reference level 5.

8 out of 8 started

  • Specified2
  • Being built3
  • Built and live3

site gateways relay over HTTPS today · signed envelopes over mutual TLS is the target

L1 Edge

collect once, never control

At the site boundary. Reference level 3.5, the industrial DMZ where a site has one.

5 out of 5 started

  • Specified3
  • Built and live2

one-way · read-only

L0 Field

where readings come from

The site's own plant and systems, as sources. Reference levels 0 to 3.

5 out of 5 started

  • Specified5

Beside every layer

Trust & tenancy · 5 out of 5 started

  • Specified2
  • Being built3

Operate & recover · 8 out of 8 started

  • Specified5
  • Being built3

Beside the control system already on site

Most sites already run a control system. Axiom Logic does not replace it and never writes to it. It reads beside it, through one declared one-way path, and takes the readings out of the site.

Kinds of path

  • The site's own path
  • Axiom reads, never writes
  • Outbound from the site to the cloud
  • A person views
  • Axiom sends figures to a system the client owns
  • Blocked

Level 5

Cloud

Axiom Logic

  • Being builtAxiom Logic cloudIngest, system of record, truth engines, proof and delivery: L2 to L6 of the first diagram.

    reads from

    • Site gateways and broker relay · outbound only · HTTPS · one credential per connection
    • Protocol gateway · outbound only
    • Edge agent · outbound only · signed

    sends to

    • Remote portal · axiomlogic.ai · the portal
    • On-site screens · the same portal, over the site's internet link
    • Enterprise connector · verified figures, each with its statement

Blocked

No write path. No setpoint, no command, no change to the control system.

Axiom Logic cloud → PLCs, DCS controllers, RTUs, drives and protection relays

Level 4

Enterprise

The client's head office

  • The site's ownERP and corporate systemsFor example SAP: finance, logistics, maintenance. They stay as they are.

    reads from

    • Enterprise connector · energy cost, demand and savings per cost centre

Level 3.5

Site boundary · industrial DMZ

The site's network, with Axiom's read-only collectors

Level 3

Site operations

The site

  • The site's ownHistorian, MES and engineering stationsStay as they are.

    reads from

    • SCADA, HMI and DCS operator stations · the site's own history

Level 2

Supervisory control

The site

  • The site's ownSCADA, HMI and DCS operator stationsFor example Ignition, WinCC or FactoryTalk View. Operators keep running the plant from here.

    reads from

    • PLCs, DCS controllers, RTUs, drives and protection relays · the site's own control network

    sends to

    • Historian, MES and engineering stations · the site's own history
    • Protocol gateway · OPC UA, read-only
    • Site gateways and broker relay · MQTT the site already publishes

Level 1

Basic control

The site

  • The site's ownPLCs, DCS controllers, RTUs, drives and protection relaysControl stays here.

    reads from

    • Sensors, meters, actuators and the plant itself · signals

    sends to

    • SCADA, HMI and DCS operator stations · the site's own control network
    • Protocol gateway · Modbus read, where the site allows a direct read

Level 0

Process

The site

  • The site's ownSensors, meters, actuators and the plant itself

    sends to

    • PLCs, DCS controllers, RTUs, drives and protection relays · signals
    • Edge agent · meter pulses and registers

Notes

  • Control stays with the site's own system. If Axiom Logic or the link to it is down, the plant runs exactly as before.
  • Every connection from the site to Axiom Logic is opened from inside the site, outwards. Nothing reaches in.
  • Where a site has no industrial DMZ, the collector sits on a network segment the site chooses, and that choice is declared at onboarding.
  • Ignition, WinCC, FactoryTalk View and SAP are named as examples of systems commonly found at a site or its head office. The names belong to their owners. No connector for a named product is claimed here: a path is available only when its block is marked Built and live.

Levels 0 to 5 are those of the Purdue reference model, as used in ISA-95 and IEC 62443.

How the two line up

  • L0 Field

    Reference level: Levels 0 to 3

    The site's own plant and systems, as sources

  • L1 Edge

    Reference level: Level 3.5

    Read-only collectors at the site boundary

  • L2 to L6

    Reference level: Level 5

    Axiom Logic in the cloud

  • L6 Enterprise connector

    Reference level: Level 4

    Verified figures sent to the client's ERP

  • L7 People and interfaces

    Reference level: At the site and away from it

    Screens that show and never control

What a SCADA is for, and what Axiom Logic adds

A SCADA system runs a plant. Axiom Logic does not. It reads beside the SCADA and turns what many plants report into the few figures the people above the control room need to decide.

  • Ignition

    Inductive Automation

    How it is built
    A server called a Gateway holds the tags, the screens and the history. Gateways can be linked across sites, with a central one for a group.
    What Axiom Logic reads
    The Gateway's own OPC UA server, which can expose its tags to an outside client. Read-only.
    SpecifiedPathProtocol gateway
  • WinCC

    Siemens

    How it is built
    A server with operator clients, from a single station up to a distributed system of several servers.
    What Axiom Logic reads
    WinCC's OPC UA server, which offers values, history and alarms. Read-only.
    SpecifiedPathProtocol gateway
  • FactoryTalk View

    Rockwell Automation

    How it is built
    HMI servers and data servers under one directory, from one computer up to a distributed application.
    What Axiom Logic reads
    The OPC UA server of FactoryTalk Linx Gateway, which gives outside software access to control information. Read-only.
    SpecifiedPathProtocol gateway

None of these has been tested against, and no connector is claimed. Each path goes through the protocol gateway, which is specified and not built. The names belong to their owners.

  • A SCADA system
    Runs one plant, second by second, from a control room
    Axiom Logic
    Lets a group decide across many plants, month by month
  • A SCADA system
    Reads and writes: an operator changes a setpoint
    Axiom Logic
    Reads only. No write path exists
  • A SCADA system
    One maker's system at each site
    Axiom Logic
    Any mix of systems, read the same way through the OPC UA server each already has
  • A SCADA system
    Tags, screens and alarms for operators
    Axiom Logic
    Cost, throughput and coming shutdowns for managers, executives and a board
  • A SCADA system
    Values as the plant reported them
    Axiom Logic
    Every figure with its source, its coverage and a statement another party can check
  • A SCADA system
    Lives inside the control network
    Axiom Logic
    Stays out of it: collects at the site boundary and shows in the cloud

Each of these systems can be linked across sites by its own maker's means. Axiom Logic does not replace that. It is for a group whose sites do not all run the same system, and for the people who do not sit in a control room.

Qualities

  • Security

    Being built
    Target
    Two-step sign-in for staff, owners and admins (in service), a check that a person is using the sign-in page and public forms (Cloudflare Turnstile, in service since 8 October), a credential per device, secrets never sent to the browser, security headers, the site behind the operator's own Cloudflare zone with managed firewall rules (since 8 October), and an independent penetration test before a second tenant.
    What will prove it
    Penetration test report; the refusal tests in the repository
  • Tenancy

    Being built
    Target
    Isolation in the database by forced row-level security; cross-tenant access tested, not assumed.
    What will prove it
    A refusal test for every table, run on every change
  • Integrity

    Being built
    Target
    Append-only store, hashed statements, daily commitments chained to the day before, and a verifier anyone can run.
    What will prove it
    125 conformance vectors run on every change; a statement verified from its own page
  • Resilience

    Specified
    Target
    Store-and-forward at the edge, retries at the relay, an off-site backup and a timed restore.
    What will prove it
    A restore to an empty database, timed and passed
  • Observability

    Being built
    Target
    Health of every connection and scheduled job visible to the operator, and a public status page with measured availability.
    What will prove it
    Operator pages showing each job's last run
  • Compliance

    Being built
    Target
    POPIA and PAIA from launch, with a signed consent or agreement behind every site's readings; certificates named only when earned.
    What will prove it
    The privacy notice, PAIA manual and transfer register published on this site, each issued with a receipt
  • Interoperability

    Being built
    Target
    HTTPS and the gateway profile in service; a native MQTT endpoint with a credential per device, a public API, webhooks, an HTTP client and file import to come; PLC and SCADA through an edge agent; WhatsApp alerts and verifiable exports out.
    What will prove it
    An acceptance check for each kind of connection
  • Scale

    Specified
    Target
    Daily and monthly partitions, raw readings kept 90 days, rollups at 15 minutes, 1 hour and 1 day kept 7 years, a load test on a separate copy, and storage beyond the confirmed 8 GB, with cost per tenant measured.
    What will prove it
    A measured cost to serve, and storage by table on the operator page

Each part is moved from one mark to the next only when there is evidence for it.

See it for yourself

Walk through your site with us.

Tell us what you run and what you already measure. We’ll show you where the evidence is strong, where the gaps are, and what it would take to close them.