SCADA for pump stations and pipe networks, installed on your own server.
A modem or gateway on site reads drives, PLCs and RTUs over their own industrial protocol and sends the data to your Aradyn server. Aradyn decodes each device, keeps the history, raises alarms and runs analysis on the live data. Your operators use it in a browser under your own name.
Core and modules
Core is the platform every instance runs. Device types, modems, VPNs, alert providers and analysis engines are modules, installed from the catalogue as each site needs them. Protocols are modules as well, so support for a new protocol or device is added without changing Core. Modules only talk to Core, through its versioned module API, never to each other.
AratecLicensing and distribution
Aradyn CoreYour server
ModulesInstalled per instance
SiteGateway and equipment
The plant as it is piped
Each device type draws its station in flow order. A multi-drive station is a manifold: common suction, each drive on its own leg, shared discharge header. Tile colour gives running, fault or sensor fault.
- Live values, historical, alarms, traffic, remote HMI and configuration on tabs
- Multi-pump staging and lead/next pump from the drives
- The same layout on a phone, with the tiles stacked
Every channel, 1 hour to 12 months
- Several channels overlaid, split onto two axes by unit
- Zoom, and CSV export of the selected channels
- Telemetry in InfluxDB, or TimescaleDB with the module
Alarms that are acknowledged, escalated and accounted for
- Channel limits and device fault bits raise alarms
- Acknowledge in the portal, by SMS reply or from a push notification
- On-call rosters and escalation chains of up to six steps
- Shelving with a reason and an expiry
- Flood suppression and a 30-day alarm health report
- Customers notified when a site stops reporting
Analysis on the live data
Analysis modules run on your server every five minutes. Their findings are ordinary alarms, acknowledged and escalated like any other.
Pipe Network Analyser
Draw the network on a map: pipes, stations, valves and the sensors already on your devices. Aradyn checks the measured flows and pressures against it.
- Headloss per pipe against expected
- Flow balance across branches and the whole scheme
- Night-flow rise against the recent baseline, as a leak indicator
- Station checks: boost, suction and cavitation risk, tank level
- Pipe condition drift over weeks
- What-if: close a valve and see pressures change
Pump Performance
Assign each pump its model and impeller trim from the pump library. Aradyn reports how each pump is performing against its curve.
- Expected and measured head and power at the actual drive speed
- Drift from the commissioning baseline
- Wear %, available as a channel for maintenance
- Flow split across pumps sharing one station meter
Maintenance
Service schedules per pump or device.
- Due by run hours, starts, calendar date or pump wear
- Due dates projected from the last 30 days of use
- Reminders by email
Your own modules, on the same API as ours
Equipment or logic the library does not cover can be added by your own team as a custom module, built inside the portal. A custom module talks to Core through the same module API as every module we publish, and is installed, backed up and removed the same way.
- Decoder mapping: payload fields to typed channels, with units and alarm limits
- Dashboard Designer: number, gauge, chart and alarm widgets bound to your channels
- Flows: drag-and-drop logic for parsing, register maps, scaling, schedules, totals and HTTP integrations
- Test runs with sample data before the module is enabled
- Source kept in your own GitHub repository and synced to the server
- Your own device ID prefix, so your device types never collide with ours
AI help, with your own API key
An instance can connect to an AI provider using the instance owner's own API key. Nothing is sent anywhere until a super admin adds a key and switches a feature on, and your users need no AI account of their own.
Describe what a custom module should do in plain words, and get a draft flow to check and edit before anything runs.
Staff and customers ask questions in the portal and get answers drawn from the help pages for your instance.
Drafting sends names only: the description, channel and setting names. Never readings, sites, customers, people or secrets.
Usage is billed to your own provider account, and each feature can be switched off at any time.
Module library
Supported drives, protocols, modems, VPNs, alert providers and analysis modules, with models and connection details.
Installed on your server, under your licence
Aradyn is not an app your end users download. It is installed once, on a server you control, and your operators and customers sign in to it.
- Licence
Aratec issues a licence for your instance and the paid modules you need.
- Install
The installer sets up Aradyn Core and everything it runs on, on a clean server, with TLS for your domain.
- Modules
Device, protocol, alert and analysis modules are installed from the catalogue inside the portal.
- Sites
Each device gets a modem package built for it. Install it on the modem and the site appears on the dashboard.
- Updates
Core and module updates are signed releases pulled from Aratec and applied from the portal.
What you provide
One server per instance, on premises or in the cloud. Everything else is installed for you.
| Item | Requirement |
|---|---|
| Server | Dedicated virtual machine or physical server, x86-64 or ARM64 |
| Operating system | Clean install of Ubuntu Server 24.04 LTS |
| CPU | 2 vCPU minimum; 4 vCPU recommended |
| Memory | 8 GB minimum; 16 GB recommended for 50+ sites or long history |
| Storage | 80 GB SSD minimum; 200 GB+ for several years of telemetry |
| Domain | A DNS name pointing at the server, for the portal and its TLS certificate |
| Inbound | 443 portal (and 80 for certificate renewal); 8883 MQTT from site devices; the port of your chosen VPN module, e.g. WireGuard 51820/udp |
| Outbound | HTTPS to Aratec for licence checks and updates; to your email and SMS provider |
| Backups | Optional S3-compatible bucket (e.g. Cloudflare R2, AWS S3) for off-server encrypted backups |
Talk to us about your sites
Tell us what equipment you run and how many sites. We will tell you which modules you need.