Portal log in
Sign in to your AGAD Portal account
Book a walkthrough
Tell us a bit about you and we'll be in touch to find a time.
Home › Connectivity
Connecting at the edgeThis is the part most platforms skip over. Getting a reading off a twenty-year-old PLC, a flow meter on an RS485 loop or a supplier's cloud API is where projects stall — so it's the part we do ourselves, with our own hardware and our own software.
Method 01 — our own hardware
A DIN-rail industrial edge computer running our own software. It sits in the panel, talks to whatever is already there, buffers locally if the link drops, and pushes to the portal over an encrypted connection. Available as a Linux appliance or as a Windows service where a site already runs a data PC.
Method 02
Publish/subscribe messaging for anything already speaking the industrial IoT standard. We run a broker, or connect to yours.
Two-way — in from devices, out to your data lake
Method 03
A documented HTTP API for systems that would rather push than be polled — including other clouds you're already paying for.
Two-way — push in or pull out
Method 04
The standard almost every modern PLC and SCADA system already exposes. If you have an OPC server, you have a connection.
Inbound — we read your server
Method 05
For the equipment that will never speak a protocol. A lab instrument or legacy system that emails a daily CSV is still a data source.
Inbound — scheduled or ad hoc
Not sure what you've got? That's normal — most sites don't have a full list. Working out what can be connected, and what it would take, is what the first engineering days are for.
Talk to an engineerWe deploy the system with you in your factory, you use it with real data for six months, then you decide whether to continue. No upfront software commitment.
