AEDDIX Systems GmbH — Wattens, Tirol, Austria
Agentic layer for physical operations
The problems you don't see are the expensive ones. Many systems. One picture of the operation. Machines report. Agents triage. People act.
AEDDIX builds a working model of your operation from the sensors and systems you already have, then watches it for the things a simple alarm misses. Nothing touches a machine unless one of your people says so.
One room, five industries
Read-only
01 · Each system on its own
- SmartSensecargo temperature4.6 °CNo alarm
- SamsaraGPS · battery12.2 VNo alarm
- Cooling unitcompressor · run timerunning 71 %No alarm
- OptimoRoutetomorrow's routes06:00 · 14 stopsNo alarm
02 · Context fusion
Van 07 · cargo box · battery · route
- Trend
- The cooling unit runs longer at every stop
- Cause
- The battery sags as it works harder
- Impact
- 06:00 route, 14 refrigerated stops
03 · Actionable insight
Van 07 is likely to lose cooling on tomorrow's 06:00 run.
→ Swap Van 07 before the 06:00 run
DispatcherTonight 21:00
Examples. Live today: SmartSense, Samsara, Tive and AEDDIX devices, plus email and SMS. Business-system imports and hand-off to your own tools are in development.
Three problems no threshold alarm would have raised
- 01The fridge that stayed in range all weekend, on a trend that would break it by Monday.
- 02The fermenter that drifted off profile a tenth of a degree an hour, from two in the morning.
- 03The van whose battery had been fading all week before the six o'clock run.
Running today at
Customers with live devices and open tasks.
Programs and support
Connect what you run. We model the rest.
Your sensors and vendor accounts stay where they are. We read them, work out what is there and how it fits together, and you approve the result.
Four steps, two of them yours
- SmartSense••••••READ-ONLY✓ CONNECTEDSamsaraVENDOR ACCOUNTTiveVENDOR ACCOUNTAEDDIX devicesVENDOR ACCOUNT
- YOU
- Pick a source and paste a read-only key.
- WE
- Check the connection.
- 12devices38sensors96signals
- FRIDGE-03temperature · door
- FRIDGE-04temperature · door
- COLD-ROOM-01temperature · humidity
- COMPRESSOR-Acurrent · run state
- YOU
- Nothing.
- WE
- Find every device, sensor and signal it reports.
- YOU
- One click.
- WE
- Propose the machines, groups, processes and rules that fit what we found.
- ✓Machines4 accepted
- ✓Sensor groups6 accepted
- ✓Processes2 accepted
- ✓Rules9 accepted
FIRST TASKDUE 18:00Cold Room 01 drifting toward 8 °C
Owner: pharmacy lead
RESOLVE IN AEDDIX · OR IN YOUR TOOLS
- YOU
- Accept, edit or reject each item.
- WE
- Put it live. Every problem it finds arrives with an owner, to resolve in AEDDIX or in your own tools.
Shown as an example. Every item in the draft comes from something we actually found.
Many sources. One model. Someone responsible for what it finds.
Most losses start as a slow drift that no single alarm is set to catch. The model sees the trend across your sources, and whatever it finds lands with a named person, reasoning attached.
Pick an operation and watch one problem travel from your systems to a closed task.
- 01
Your systems
Read through a read-only key. They keep running exactly as they are.
- SmartSenseLive
Cold Room 01 · 6.9 °C · in range
- AEDDIX door sensorLive
14 openings since 06:00 · usual 5
- Compressor controllerIn development
running 92 % of the last hour
- Stock systemIn development
€38k of vaccines inside
- 02
Context fusion
Every reading is joined to the fridge, batch or van it belongs to, with its history.
Cold Room 01 · vaccine storage · 2–8 °C
14 months of history
4 sources → 1 model
- 03
Intelligence
Finds the slow drift or odd combination, says why, and shows the readings behind it.
Still in range, but not for long: about 40 minutes to 8 °C. The door is the cause, not the compressor.
Because
- ↳ door 14× against a usual 5
- ↳ compressor at 92 %
- ↳ +0.3 °C every 10 minutes
Not sure? It goes to a person as “needs review”, never out as an alarm.
- 04
Your rules, your person
Your rules decide who hears about it. One named person approves, edits or refuses.
Rule v14 · stock over €10k goes to a person
Pharmacy leadby 18:00Check the door seal and move the stock
- 05
Resolved
Closed in AEDDIX, or handed to the tools your team already works in.
Closed 17:48 · seal replaced · back to 4.8 °C
Resolved where your team works
- In AEDDIXLive
- By email or SMSLive
- In your own toolsIn development
Fig. 01 · How a problem travels
Example events
It reads. Your people decide.
The questions we hear first
- How do you stop the AI from making things up?
- Your rules decide the clear cases, not the AI. It looks only at the unclear ones, reads only your own data, and shows the readings behind every suggestion. When it is unsure, a person sees it as “needs review”. It never acts on its own.
- Where does our data go?
- It stays in your own space, kept apart from every other customer. It runs in your cloud account, on site, or close to the equipment, and you can export all of it from day one.
- Can it change anything on our machines?
- No. We read through read-only keys and never write to a controller or a machine. Tasks reach your own tools only through a hand-off you switch on.
- Who answers for a decision?
- One named person, every time. We keep who saw what, what was suggested and decided, and which version of your rules applied. Later edits do not rewrite the past.
Compliance
Compliance, deployment by deployment.
Each deployment is mapped to the privacy, security and residency rules that apply to it. We claim no certification today. A US healthcare deployment gets the required safeguards and a Business Associate Agreement.
- ISO/IEC 27001:2022Information securityPRIMARY TARGET
- SOC 2 Type IIService assuranceROADMAP
- HIPAAUnited States · health informationPER DEPLOYMENT
- Québec Law 25Québec · privacyPER DEPLOYMENT
- PIPEDACanada · privacyPER DEPLOYMENT
- ISO 28000 / 28001Supply-chain securityALIGNMENT
What is live and what is not
Plans, not promises.
- LiveTODAY
Connecting sources, the model, AI triage, your rules, tasks resolved in AEDDIX, and email and SMS.
- In development6 TO 12 MONTHS
Hand-off into your own tools, and testing a change on a copy before it goes live.
- Planned12 TO 18 MONTHS
An on-site runner that keeps working when the connection drops.
- Planned18 TO 24 MONTHS
Approved actions back to a machine. Only after a person signs off, and only after a test on a copy.
Running today, in places where a missed problem costs real money.
“Two years in, and AEDDIX systems have become integral to our success, helping ensure the quality, consistency, and reliability of our operations. Over 16 fermenters and our taproom, the platform has proven simple to use and highly effective in supporting our team day to day.”
- industry sectors in production
- 5
- live devices
- 275
- countries
- 3
- source connectors live today
- 4
Logistics · Pharmacy · Brewing · Hospitality · Healthcare
Production figures as of 2 September 2026.
“From infrastructure migrations and custom application development to cold chain monitoring and operational digitization, the team has consistently supported our vision every step of the way.”
“With telematic GPS fleet monitoring and custom cold chain management devices, we now benefit from stronger traceability, better operational control, and greater confidence in our logistics environment.”
“Over the years, the platform has delivered real value through stronger customer engagement, better data transparency, and reliable operational support.”
05 — Start here
Bring the problem that keeps coming back.
In 30 minutes we look at what you run, what AEDDIX can read today, and the first problem worth catching across it. Nothing gets replaced in a first conversation.
- Read-only keys
- Nothing replaced
- You approve before go-live
What happens next
- 01A 30-minute callA list of vendors, a photo of the alarm screen or a walk through the building is enough to start.
- 02One source, read-onlyYou paste one read-only key. We find every device and signal it reports.
- 03Your approvalWe draft the model. Nothing goes live until you have accepted, edited or rejected each item.
Which sounds like you?
I already have sensors
SmartSense, Samsara, Tive, PLCs, meters. They stay. We read them.
Talk it through (opens in a new tab)My alarms live in several systems
The problem between the vendor portal, the building system and the inbox is the first one we draw.
Talk it through (opens in a new tab)My IoT cloud is being retired
If Azure IoT Central or another platform is shutting down, your devices can land here without new hardware.
Talk it through (opens in a new tab)