How BAVIS works: architecture, requirements, redundancy and tests
BAVIS is a web SCADA. A single server reads data from devices, processes it and shows it in the browser on a PC, tablet or phone – with nothing to install on the clients.
ArchitectureRequirementsMeasured performanceRedundancyDrivers and SDKDevelopmentTestingSecurity
Architecture
From the device to the browser
- Server runs as a Windows or Linux service (systemd), on Linux also in Docker (Linux and Docker from version 4.0). It is written in Python (FastAPI), the interface in React and TypeScript. The client is just a browser; it can also be installed as an app (PWA) on phones and tablets.
- Drivers (communication modules) read and write devices. Each connection runs in its own thread – an outage of one device does not affect the others.
- Engine converts raw values to engineering units (scaling, correction, decimals, dead band) and watches validity: when a connection drops, values become invalid, not “frozen” – operators never see an old value as current.
- On top of tags work alarms (per ISA-18.2 / EEMUA 191), history, logic and calculations, time schedules and modules (energy, OEE, maintenance, recipes, reports, sequencer, traceability…).
- Live data to the browser go over WebSocket. The browser subscribes only to the values currently on screen – in large projects this cuts traffic to the client roughly 40× (measured).
- BAVIS as a data source: OPC UA server, Modbus TCP/RTU, BACnet/IP, a built-in MQTT broker (UNS, Sparkplug B), REST API, MES outputs (MQTT, HTTP, SQL), a data source for Grafana. From 4.1 also an IEC 60870-5-104 server for dispatch centres.
- Database: SQLite in the default installation (nothing extra to install); from version 4.0 also PostgreSQL as the main database with SQLite ↔ PostgreSQL conversion.
- Project (connections, tags, screens, alarms) is edited right in the browser. Saving activates it immediately without restarting the service; every saved version is a revision you can go back to. From 4.0 the project can also live in Git.
- BAVIS Central is a separate server for multiple installations: site overview, status, updates, licences, backups and service without VPN (tunnel only with the operator's consent). We are preparing (4.x) Central as a combined historian for several installations.
- Extensions without touching the core: drivers, servers, object templates, faceplates, symbols and screen elements are separate modules. An error in one module is isolated – the other modules and the application keep running.
- Simulation: every installation can run in simulation (built-in device simulators, sample projects). A simulated instance may connect only to this computer – it never controls a real device.
Connection processes (in preparation for version 4.2)
In large projects, reading connections and processing values can run in several processes so the server uses more cores. The main process keeps serving the web, alarms and history; a crash of a connection process does not take down the web or other connections – the process restarts itself. Off by default. (Drivers: Modbus TCP, S7, Beckhoff ADS, EtherNet/IP, Omron FINS, MELSEC, PCCC, SNMP, simulation.)
System requirements
What BAVIS runs on
| Requirement | From version | |
|---|---|---|
| Windows | 64-bit Windows 10 / 11 or Windows Server 2016 and later (the installer refuses other systems) | released |
| Linux | Debian 12 / 13, Ubuntu 24.04 LTS (22.04 with Python 3.11), x64 and ARM64; .tar.gz or .deb package, systemd service | production use from 4.0 |
| Raspberry Pi | Raspberry Pi 4 / 5 / CM4 / CM5, 2 GB RAM or more, Raspberry Pi OS 64-bit; for production use we recommend an SSD instead of an SD card | from 4.0 |
| Docker | image for amd64 and arm64 | from 4.0 |
| Home Assistant OS | BAVIS add-on with its interface in the Home Assistant sidebar | from 4.0 |
| Client | current Chrome, Edge, Firefox or Safari on a PC, tablet or phone; nothing to install | released |
| Installation | the installer contains everything needed (including Python) – no internet connection required | released |
| Network | one HTTPS port (default 8443) and optionally a redirect from HTTP (8080); OPC UA / Modbus / BACnet servers only if you enable them | released |
| Database | nothing extra (SQLite); optionally PostgreSQL | PostgreSQL from 4.0 |
We do not support 32-bit systems. On Linux there is no OPC Classic DA (Windows only) and NI DAQmx cards are not supported yet. The Linux and Raspberry Pi code passes automated tests; we support them officially from version 4.0.
Sizing – how much one installation handles
- Up to 10,000 tags and dozens of browsers one installation is enough with plenty of headroom.
- Around 50,000 tags changing every second are handled by one installation with ordinary screens; the limit is set by the performance of a single CPU core, not the number of cores.
- Up to 100,000 tags with connection processes (in preparation for 4.2) on a 4-core computer.
- More than about 100,000 tags → several installations and combined data in BAVIS Central (combined history in preparation, 4.x).
Disk space for history
History in “store everything” mode with a 1 s period takes 0.25–0.4 MB per tag per day (measured): 1,000 tags ≈ 250–400 MB of raw data a day. Retention (how long to keep data) and per-tag compression (dead band, swinging door) reduce this substantially. On a Raspberry Pi writing to the SD card switches to batches by itself: measured 22.4 MB/h → 2.8 MB/h (50 tags, 1 s period).
Measured performance
How we measured
Always the worst case: every tag changes in every cycle (1 s). In real operation only some values change, so the same number of tags loads the server less. The load test tool is part of BAVIS and can also run next to a live installation at the customer's site.
| Project | Browsers | Result | Server memory | Measured |
|---|---|---|---|---|
| 10,000 tags, 1,000 with history | 10 / 50 | everything delivered, CPU 11% / 29% of one core (average) | 175 MB | Linux, 4 cores, 30 Oct 2026 |
| 50,000 tags, 2,500–5,000 with history | 20 | reading and history keep up with the 1 s period (SQLite and PostgreSQL); history never fell behind | 420–445 MB | Linux, 4 cores, version 4.0, 1 Nov 2026 |
| 50,000 tags, a screen with 20 values | 20 | CPU 29% of one core, 36 kB/s per client instead of 1.4 MB/s | 328 MB | version 4.0 |
| 100,000 tags, 3,031 with history, connection processes (4.2) | 20 | main process 37% of one core, change in the browser within 0.6 s (p95) | 549 MB + connection processes | Linux, 4 cores, 7 Nov 2026 |
- API response: system status 3–17 ms, history of 4 tags × 10 min 4–9 ms.
- Project activation (saving): 2.6 s (10,000 tags), 15–46 s (50,000 tags, depending on the number of tags with history and the database).
- PostgreSQL writes history 3–5× slower than SQLite (p95 88–140 ms vs 23–29 ms) – still far below the 1 s period.
- Above the limit: 200,000 tags on one installation – reading keeps up, but distribution to browsers does not. That is why we recommend several installations and BAVIS Central.
Redundancy and backups
Hot-standby redundancy
Two BAVIS servers, one active, one standby. Both read the devices and both store history – switching over leaves no gap in the trends. Redundancy is a released feature of the Standard licence.
- Only the active server controls: it writes to devices, evaluates logic and schedules, sends notifications, reports and MES outputs. Every 10 s the standby server takes over users, recipes, settings, alarm, maintenance, energy and OEE state, the operations log and the project from the active one – after taking over control it continues with the same data.
- Automatic takeover: when the active server does not respond for longer than the set time (default 10 s), the standby takes over.
- Protection against “two actives” (split-brain): the standby server takes over only if it can also see a witness (e.g. a PLC). So when the network between the servers splits, they do not both become active. When the connection returns, the servers agree and the preferred one stays active.
- History backfill: a server that was off (a minute up to 14 days) downloads the missing part of the history from the other server.
- Operators: a browser on the standby server shows a bar linking to the active one; if a server fails, the browser switches to the other by itself. Redundancy settings and a test of the second server are in the application (administrators only, with an electronic signature).
- Security: every request between the servers is signed with a shared key (HMAC-SHA256) with replay protection, and the data transferred is encrypted (AES-GCM) – neither passwords nor the project cross the network in readable form.
- Licence: the standby server costs 50% of the main server's licence price with the same edition and tag limit.
Free test installation
With every Standard licence, one test installation with the same edition – for trying out the project, training and checking updates, without controlling or monitoring real equipment.
Several installations and BAVIS Central
For large or distributed sites: several BAVIS installations (say one per hall or site) with BAVIS Central on top. For version 4.x we are preparing copying of history from installations to Central: one chart across several sites, tag search, CSV export, a data source for Grafana, retention and storage quota set on Central.
Backups and restore
Automatic backups to a network share (SMB), S3, FTP/FTPS or a local disk, with encryption; backups also via BAVIS Central. Restore from a backup, going back to an earlier project revision and automatic rollback of an update when the new version keeps crashing.
Drivers and SDK
How drivers work
- A driver is a module for one protocol or one device. BAVIS starts its own thread for each connection: it connects, reads all tags of the connection cyclically, on error disconnects, marks the values invalid and reconnects after 2 s. The connection shows its status, the number of reads, errors and reconnects and the cycle time.
- Events (MQTT, KNX, wM-Bus…) are passed on by the driver as they arrive, without cyclic reading.
- A driver returns raw values. Scaling, dead band, alarms and history are done by the core – the same for all protocols.
- Writes always go through the core: role and permission checks, limits, unit conversion and an audit entry. Only then does the driver write to the device. Writes to flash memory (e.g. PV inverter control) are protected against writing too often.
- The connection form, connection test, address browsing and network device discovery are described by the driver itself – a new driver appears in the application without changing the core.
- We take register maps and protocols only from the manufacturer's documentation or a standard, never by guessing. We do not use unofficial cloud APIs without an explicit decision.
- From version 4.0 the application shows for every driver whether it has run on a real device (“Verified on a real device”) or so far only against a simulator and in tests (“beta”).
Driver types in the core
| Version | Driver types |
|---|---|
| 3.0 | 27 |
| 3.1 (released) | 43 |
| 4.0 (planned 2027) | 79 |
| 4.1 (planned 2027) | 92 |
Simulation and calculation are included (capability catalogue, 7 Nov 2026). So far 10 core drivers have run on a real device: Modbus TCP, Siemens S7, NI DAQmx card, MQTT, ESPHome, local Tuya, WLED, Midea air conditioners, LG ThinQ and a car (manufacturer cloud, some values so far). The others are verified against a simulator or in automated tests – “beta” does not mean “broken”. We will gladly test a driver with you.
SDK – your own drivers
- SDK API 1.0 came out with BAVIS 3.1: a stable public Python interface for drivers outside the core – for the community, integrators and custom drivers.
- From version 4.0 every installation (Windows, Linux, Docker) has the bavis sdk command: new, test, check and build. You do not need the core source code – the free Lite or Maker edition is enough.
- A driver is tested against a fake device on a port chosen by the system; tests run in parallel and without hardware.
- A package that uses only bavis.sdk keeps loading after the next major core version (3.x → 4.x). A new major SDK version comes only with a new major core version, and the previous one stays supported for at least one LTS release.
- The public BAVIS-SDK repository (Apache-2.0): guides in Czech and English, 9 sample drivers, contribution rules, a code of conduct and discussions. We try to answer every contribution within two weeks.
How drivers are delivered and signed
| Type | How it is delivered | Signature | From version |
|---|---|---|---|
| Core drivers | part of the installer and updates | updates are signed (Ed25519); the application verifies the signature before installing | released |
| Our packages and drivers we have tested | .bavispkg package | signed, with a “verified by Benešl Automation” badge in the application | from 4.0 |
| Community drivers (SDK) | .bavispkg package | may be unsigned: the application warns “at your own risk”, the administrator must confirm the installation and it is written to the audit log | from 4.0 |
Package code runs in the BAVIS process with the same rights as the core – hence the signature, the warning and the audit entry.
Development
How we develop
- Version plan: maintenance releases and two lines – LTS (12 months of fixes only) and versions with new features. Every LTS fix has a regression test.
- Every change is made on its own branch with a description and a security assessment (what data and interfaces it adds, who has access, what happens if it is misused). A new interface (API, protocol, server, network access) also updates the threat model and is approved by the head of development.
- Secure by default: a new feature is off or read-only after installation; protocol servers, simulation, Central, OIDC and LDAP are off until the administrator enables them. No default password.
- Into a released version a change gets in only after green tests and a review; only the head of development makes releases.
- Capability catalogue: for every feature and driver we keep the version and verification status (real device / simulator / test). An automated test makes sure nothing is missing from the catalogue.
- Third-party libraries: locked versions, a software bill of materials (SBOM, CycloneDX) with every Windows release, a check for known vulnerabilities on every build. The core has no GPL-only libraries; the optional Cameras add-on on Windows contains FFmpeg under GPL v3.
- IEC 62443: we develop the product with IEC 62443-4-2 in mind (a self-assessment of the requirements is part of the documentation) and run the development process with IEC 62443-4-1 in mind.
Testing
How we test
- Automated tests on every change: almost 5,000 core tests (version 4.2 suite, 7 Nov 2026), project tests, type checks and interface builds, a check of translations into all languages, a check that no private key is in the code or history, static code analysis and a library vulnerability check. The full suite runs on our own test servers.
- Browser tests (E2E): every menu and settings page is opened in Chromium as administrator, operator, anonymous user and on mobile – without errors, without a module failing to show, without overflowing the screen.
- Device simulators: BAVIS ships with simulators (inverters, Shelly, Hue, Victron, cameras, 3D printers, Jablotron, 2N intercom, Domat/SSCP, AMiT, EEBUS…). Every driver is tested against a fake device: reading, writing, connection loss and recovery.
- Installer test on clean Windows before every release (Windows Sandbox): silent installation, services, administrator password without a default “admin/admin”, file permissions, no private key in the installation, service restart after a crash, update over a running version keeping data and settings, a wrong parameter causing no change at all, and uninstall keeping the measured data. Updates are also tried from an older version.
- Linux and Docker: package build, installation, start, sign-in, update and uninstall automatically on Linux (x64, ARM64 in emulation); the Docker image including restart and a new container with the same data.
- Load tests – a small run automatically, the full one manually before release.
- On real devices: we record the result of every hardware test against the driver (the “verified” label). We test on real devices in an occupied flat. The core runs in operation at a construction products test lab (version 3.0 LTS).
Security
Security and updates
- HTTPS in the default installation (your own or a company certificate), firewall configured by the installer (local subnet only recommended).
- Users, roles, areas and screen permissions; two-factor sign-in, AD/LDAP, OIDC; an operations log with a SHA-256 hash chain and electronic signatures.
- Updates signed with Ed25519 and verified before installation; the update key is separate from the licence key and can be revoked. An SBOM (for Windows releases) and checksums with every release.
Versions, support and vulnerability reporting Security in version 4.0 BAVIS licence agreement Editions and prices How to verify a download
Need a specific project assessed?
Send us the number of tags, devices and availability requirements. We will propose sizing, redundancy and the edition.
Siemens, SIMATIC, S7 and TIA Portal are trademarks of Siemens AG. Other manufacturer and product names are trademarks of their respective owners.