Pragmatos Platform and Trust

Runs where you choose. Answers to your IT.

Foundation, Fabric, Command and Mobile: the server, the links to your business systems, the administration and the phone app. On premise in your plant, in your own cloud, or both: you choose. Pragmatos only reads at the machine.

Illustration: an IT lead at a desk works through a long checklist, a server rack behind glass, and the moulding hall below the window
1
Where does it run?On premise in your plant, in your own cloud, or both: you choose.
2
Who signs in?Your staff, through your own sign-in.
3
Can it touch a control?No. It reads, people act.
The questions IT asks first. Before a plant system goes in, IT and automation want straight answers. The answers are below.
Illustration: a factory drawn as a cutaway, with lines from every machine running to a server room inside the building and none leaving it
1
Your data, your choiceReadings, decisions and records stay in your plant or your own cloud.
2
Nothing calls outInternet only for what you switch on.
Your data stays where you choose. One database per company, in your plant or your own cloud. Updates arrive as a bundle you install.
Illustration: a shift supervisor seen from behind checks a phone on the press floor, a group of colleagues in the distance
1
The plant in your pocketDecisions, stops and hand-overs on the phone.
2
Figures by groupGroups of five or more by default.
The plant in your pocket, figures by group. Push stays off until your administrator switches it on. Shift and crew figures appear only for groups of five or more by default.

The ground every step of the loop stands on

Pragmatos follows one loop: connect the machines, see them, analyze them, decide, act and prove it. Under every step sit four parts. Foundation is the server, the sign-in and the record. Fabric links Pragmatos to your ERP and to anyone who builds on it. Command is where IT runs every plant from one console. Mobile puts the decisions in the pocket of the person who acts on them.

  1. ConnectLoom
  2. SeePragmatos Live
  3. AnalyzePulse
  4. DecideOrbis
  5. ActFlow
  6. ProveDecisions
Foundationthe server and the rules
Fabricthe links to your systems
Commandthe console for IT
Mobilethe plant in your pocket

Foundation: your server, your sign-in, your rules

Foundation

Foundation is the common ground every module stands on: one model for machine signals, one for decisions, the roles, the record and the checks that every pack and connector passes before it installs. For you it means one installation that IT can size, back up and sign off, instead of a set of separate tools.

Illustration: a cross-section through a factory floor, with a lathe, a press, a compressor and a cabinet above and one shared band of layers running beneath all of them
What it shows: every machine on the floor standing on the same ground: one model, one record, one set of roles.
  • Where it runs.On premise in your plant, in your own cloud, or both: you choose. In a hybrid set-up, the edge computer in each plant reads the machines, buffers through a network drop and sends on only the data you choose.
  • One database per company.Backup, restore and upgrade run one company at a time, so an IT house can run several customers on one installation.
  • Sign-in through your own identity provider.Single sign-on by OpenID Connect, with your directory behind it. One sign-out ends every Pragmatos screen.
  • Nine roles, checked on every call.From operator to company admin. The server checks each right on every request, and a screen outside a role is refused.
  • The open-source core under Apache-2.0, modules under a commercial licence.Every release ships with a component list (SBOM) naming each part and its licence.

How big a server you need

One installation runs on one platform server, with a small edge computer per plant on top.

Server size for one installation, by number of devices connected
DevicesvCPUMemorySSD storage
up to 50416 GB250 GB
up to 300832 GB1 TB
up to 1,0001664 GB2 TB

Fabric: approved work lands in the systems you already run

Fabric

A decision is only worth something once it becomes work. Fabric sends approved work into your business systems and brings the completion back, so nobody types a work order twice. It also gives your developers and partners one published interface to build on.

  • SAP, incl. Business One
  • proALPHA
  • Dynamics 365 Business Central
  • Odoo
  • Other systems over REST or CSV

The ERP link is not needed to start. When you add it, it uses API users on the ERP side, under your ERP licence.

Illustration: a bridge woven from fine threads between a machining hall and an office, with blank cards travelling both ways
What it shows: the hall and the office joined: approved work goes out to the business systems, and completions come back.
Approved work goes into your ERP.Work orders, service calls, quality notifications and corrective actions go out. Completions come back.
Your developers and partners build on a published interface.API reference, keys, sample code and a sandbox plant, for your own team as much as for software partners.
Machine identity in the standard format.The plant model maps to the concepts of the Asset Administration Shell (IEC 63278) and exports the Digital Nameplate submodel.
A whole industry installs as one pack.Ten solution packs, from CNC machining to compressed air. Each brings its screens, rules and machine classes, and installs per plant.

Invoices and accounting run through Pragmatos Flow, with DATEV export and XRechnung or ZUGFeRD e-invoices.

Command: every plant, every connector, one console for IT

Command

Command is where whoever runs Pragmatos runs it: companies, plants, packs, licences, connector health, backups, audit queries and the works-council mode. One place for every installation, whether you run one plant or an IT house runs twenty customers.

Pragmatos screen: one row of the decision record with its type, machine, status, risk class, model reference and rationale
What it shows: one row of the decision record, with the model that proposed it, the risk class and the rationale beside it.
Illustration: three factories in different landscapes linked by thin lines to one wall screen, where a person stands looking at rows of coloured dots
What it shows: three plants on one console, each connector shown by its state.
Every connector, every plant, one screen.Up, without data, or failing, with the age of the last reading. You see a silent plant before anyone phones you.
Backups you can test.A nightly snapshot plus continuous log archiving, and a restore drill at every installation. An export is a data handover, not a backup.
Drift against the approved baseline.Each plant's configuration is compared with what was approved, field by field.
28 screen languages.Chosen per person. Decision texts and solution packs come in German and English.
Designed for the EU AI Act's human-oversight and logging requirements.For any period: which decisions a model influenced, which role approved them, and which packs and versions were active.
Monthly releases, offline.Security fixes ship in the monthly release, a critical fix ships on its own, and you can roll back to the previous release.

Mobile: the plant in your pocket, figures by group

Mobile

The Pragmatos app on phones and tablets carries the same roles, the same decisions and the same figures as the big screen, in the pocket of the person who has to act. A tap on a message opens the decision it is about.

It is built for the conversation with your works council: figures by group, not by person, and every switch that would change that on the record.

Pragmatos screen: the history of the works-council mode, each change with its date and a note
What it shows: the works-council mode history in Command. Every switch of person linkage is listed with its date and the works-agreement reference.
Illustration: five people seen from behind at a long table, facing a wall screen of grouped bars, with the machine hall through the window
What it shows: figures shown by group, not by person, in the works council's own view.
My decisions, in my pocket.The cards for my role: approve, reject with a reason, or defer. Two-person sign-off where the decision asks for it.
Scan a machine, see its state.State, age of the last reading, open faults and today's output. The phone opens the machine's Pragmatos screens, never its control.
Stop reasons and maintenance from the floor.The operator records why a machine stopped and the supervisor confirms. Maintenance is marked done with a photo.
Push stays off until you switch it on.Push to phones leaves the plant, so your company admin decides when it starts.
Figures by group.Shift and crew figures appear only for groups of five or more by default. No ranking of named people, and no report per person.
Offline on the floor.The last picture stays readable, and actions wait and send when the phone is back in range.

Trust and IT: what stays where, and who decides

Platform

Before IT says yes, it asks where the data goes, who signs in, what the software can touch, and what is written down. Here are the answers in one place.

Pragmatos reads, people act. Behind Loom AI and Orbis is a smart language model working with statistical and physical methods, and it learns from every confirmed decision. It proposes. A person with the right role decides, and the decision goes on the record.

Your data stays in your installation.The language model behind “Ask your plant” runs inside your installation. Questions and answers stay there.
Reads, never writes.Read-only at the machine, through a read-only account where the control offers one. People act on the machine.
Your sign-in, your roles.Your identity provider, nine roles, and rights checked on every call.
A tamper-evident record.Every decision is chained to the one before it. A verify screen walks the chain against the exported chain head, and a change made with higher rights shows.
A person with the right role decides.Orbis proposes and shows how it got there. Designed for the EU AI Act's human-oversight and logging requirements.
Supports your ISO 50001 energy management.Energy review, energy performance indicators and action records, kept as you work.
Fits your security design.Deploys into your IEC 62443 zones and conduits. OPC UA signed and encrypted, MQTT over TLS, a vulnerability address and a stated update period per release.
Remote service only when you allow it.Off until switched on. Each session reaches Pragmatos screens, never a control, with your consent, for a set time, on the record.

What Pragmatos is not

  • Not a safety function. It reports, and the machine's own safety circuit protects.
  • No ISO 27001 or TISAX certificate: Crius holds neither. Pragmatos deploys into your security design, aligned with your own controls.
  • Not a path into your controls. No role, no remote session and no pack can write to one.

One Monday at a company with three plants

One installation, three plants, an IT lead, a supervisor and the works council. Here is how the day runs.

  1. 06:40 A plant goes quiet.Command shows the connectors in Plant 2 without data since 05:52. The IT lead sees it on the overview before the early shift asks.
  2. 06:41 Nothing is lost.The edge computer in Plant 2 keeps every reading with its own timestamp while the link is down.
  3. 07:05 The link is back.A switch in the hall is replaced. The edge computer sends the buffered readings in order, and the Plant 2 figures fill in for the whole gap.
  4. 07:20 A decision on the phone.Orbis proposes a tool change on a lathe in Plant 1. The supervisor approves it on her phone, and the work order goes to the ERP.
  5. 10:00 The works council looks in.In its own view the works council checks the switch history: linking data to a person is still off, and no new report has gone in.
  6. 16:30 The quarter on the record.For the audit, the IT lead runs one query: every decision a model influenced this quarter and the role that approved it.
3plants on one installation
1database for the company, all plants in it
73minutes of readings buffered and sent
1query for the quarter's audit record

Who it's for

Platform

Open your role to see what changes for you.

If you run the servers, the network and the sign-in:

  • It runs where you choose, on premise or in your own cloud, sized from a table. No internet needed when it runs on premise, and updates come as an offline bundle.
  • Sign-in goes through your own identity provider, and nine roles are checked by the server on every call.
  • Command shows every connector and backup in one place, and the restore drill is part of every installation.

Bring your IT questions. We walk you through the platform on your network diagram.

The one-page sheet

Pragmatos on one page, to pass to your colleagues.

Download the sheet (PDF)

Readiness self-assessment

Where your plant stands before the first machine is connected.

Start the self-assessment

OEE reality check: the calculator

See how far a reported OEE can sit from one that counts micro-stops and speed loss.

Open the calculator

Your data stays in your installation, on premise or in your own cloud. Pragmatos reads, people act.

Book a walkthrough

The loop this platform carries

  • ConnectLoom AI reads the machines you already run.
  • SeeOne screen for the whole shop.
  • AnalyzeCondition and trends, machine by machine.
  • DecideOrbis proposes, a person approves.
  • ActApproved decisions become work.
  • ProveEvery decision on the record.

Back to the Pragmatos overview

Get new articles by email

One shop-floor problem at a time.

Questions IT and the works council ask

An alarm from a machine, shown on a phone
No. On premise in your plant, in your own cloud, or both: you choose. In a hybrid set-up, the edge computer in each plant reads the machines, buffers through a network drop and sends on only the data you choose. Updates arrive as an offline bundle. Three things use the internet, and each stays off until your admin switches it on: push messages to phones, a messenger channel for alarms, and a sign-in service hosted outside the plant.
No. Pragmatos reads at the machine and has no path to write to a control. Approved work goes to people and to your business systems, and people act on the machine.
SAP, including Business One, proALPHA, Dynamics 365 Business Central, Odoo, and other systems over REST or CSV. Work orders, service calls, quality notifications and corrective actions go out, and completions come back.
The works council has its own read-only view in Command: what person data exists, where it sits, who sees it, every switch that was changed and every report in use. Shift and crew figures appear only for groups of five or more by default, and linking data to a person stays off until it is switched on with a reference to your works agreement (Betriebsvereinbarung).
A person with the right role. Orbis proposes and shows how it arrived there, the person approves or rejects, and the decision goes on the record with the approver's role. Pragmatos is designed for the EU AI Act's human-oversight and logging requirements. Whether your use meets the Act is for you and your advisers to assess.
No. Pragmatos deploys into your own security design: your network zones, your sign-in, your monitoring. Every release ships with a list of its components and their licences, and a penetration test is available on request.
Yes. Each company gets its own database, and backup, restore and upgrade run one company at a time. Command shows every plant on one screen.
It stays yours. You can export everything per company at any time, the database schema is documented, and the open-source core of Pragmatos is published under the Apache-2.0 licence.