5 minute read Written for iT directors, plant engineering and operations leadership

The short answer

ProAlert™ is built on current Microsoft technology: a .NET 9 web server, a SQL Server database, real-time push to every screen over SignalR, mobile apps for Android, iOS and Windows from one .NET MAUI (Multi-platform App UI) codebase, and a documented REST API (Application Programming Interface) of 474 operations. The version numbers are not the point. What a plant gets is screens that update on the event, one database instead of several, connections to other systems without middleware, security built into the foundation, and a system that keeps evolving instead of being replaced.

01Plant terms

Architecture choices, translated into plant terms

What each design choice means on the floor
Design choiceWhat it means for the plant
Push, not pollingThe server sends each event to the right screens the moment it happens, designed for delivery in under a second. Nobody refreshes a page to find out a line is down.
One database, one data-access layerA machine is one record that every discipline references. The audit trail is written automatically on every auditable record, and records are soft-deleted, so history is never lost.
A documented REST API474 operations across 47 controller groups for connecting ProAlert to an existing ERP (Enterprise Resource Planning), MES (Manufacturing Execution System) or BI (Business Intelligence) stack without a middleware vendor.
One mobile codebaseThe same behavior on Android, iOS and Windows, with a local database so a technician keeps working where the Wi-Fi does not reach.
A stateless web tierCapacity grows by adding servers behind a load balancer, with a Redis backplane carrying real-time messages between them.
A self-contained front endEvery library is served from the ProAlert server, with no content delivery network, so boards and kiosks run on an isolated plant network.
Built for safe upgradesSecrets live outside the deployment folder, a pending database migration is reported at startup, and unhandled errors are written to a queryable table. Updates reach your installation as they ship.
02Security

Security in the foundation, not on the screens

  • Encrypted and authenticated. TLS (Transport Layer Security) 1.2 or higher on all traffic, JWT (JSON Web Token) authentication, passwords and PINs hashed with BCrypt, and account lockout after repeated failed logins.
  • Role-based and assignment-based. RBAC (Role-Based Access Control) with more than twenty operational and administrative roles, plus data visibility limited to the assets and areas each person is assigned to.
  • No open door. Accounts arrive by invitation only, with no self-registration and no shipped default administrator password.
  • Defended inputs. Parameterized database queries, validated input, encoded output and API rate limiting.

Single sign-on is not available today. Authentication is ProAlert’s own identity system, with trusted-device approval for tablets and kiosks.

03Years ahead

Why it matters for a system you will run for years

Plant software is not replaced often, so what it can become matters as much as what it does on day one. Because every discipline in ProAlert sits on the same database, a plant that licenses another module turns on new capability against the records it already has, rather than adding a system and an integration. Because updates are delivered continuously to each installation, the plant runs the current platform rather than a version frozen at go-live.

How this is deployed inside the plant is covered on On-Premises Plant-Floor Software, and the machine-connectivity layer on Edge Devices and LAN Architecture.

04FAQ

Questions buyers ask next

What technology is ProAlert built on?

ProAlert is built on Microsoft technology: a .NET 9 web server, a SQL Server database, SignalR for real-time push to screens and devices, mobile apps for Android, iOS and Windows built with .NET MAUI, and EdgeSense edge devices on Raspberry Pi hardware at the machine.

Does ProAlert have an API for connecting other systems?

Yes. ProAlert exposes a documented REST API of 474 operations across 47 controller groups, used to connect it to an existing ERP, MES or BI stack without a middleware product.

Does ProAlert support single sign-on?

Not today. Authentication uses ProAlert's own identity system with JWT tokens, BCrypt-hashed passwords and PINs, invitation-only accounts and trusted-device approval for tablets and kiosks.

Can ProAlert scale across many users and plants?

Yes. The web tier is stateless and can be load balanced across several servers, with a Redis backplane for real-time messages, and the organizational model supports multi-site and multi-legal-entity operations. As a planning guide, 1,000 concurrent users typically need about 2 CPU cores and 4 GB of RAM for the web server and 4 CPU cores and 16 GB of RAM for the database.

Bring the systems you run today

We will walk your current stack against this page on a 30-minute call and tell you plainly what ProAlert covers and what it does not.

Schedule a Demo Edge Devices and LAN Architecture REST API All Resources