BAVIS versions and support: how long, what and how fast
Which BAVIS versions receive fixes and for how long, how we release new versions and how to report a security issue. The licence is perpetual and works without support too.
Two version lines
Stability or new features
LTS – long-term support
12 months of fixes only: no new features, no changes to the project format, database or API. For operations that want peace and quiet. Every fix has a regression test.
New features
Released continuously (3.1, 4.0, 4.1…); fixes always go into the latest version.
Support table
| Version | Release | Support | Note |
|---|---|---|---|
| 3.0 LTS | November 2026 | until November 2027 | 3.0.x maintenance releases |
| 3.1 | November 2026 | until 4.0 is released | current version with new features |
| 4.0 | planned 2027 | until 4.1 is released | Linux, Raspberry Pi, Docker, PostgreSQL What BAVIS 4.0 brings |
| 4.2 LTS | planned 2027 | 12 months from release | next LTS; upgrade from 3.0 directly to 4.2 |
We are planning the 4.x releases for 2027; we are not promising exact dates yet.
Security
Vulnerability reporting and response times
- Reporting: confidentially by e-mail to benesl@benesl-automation.cz with the subject “BAVIS – bezpečnost”.
- Response times: acknowledgement within 5 working days, assessment within 14 days, a fix for a critical or high vulnerability targeted within 30 days and coordinated disclosure after the fix is released.
- Fixes and updates: security fixes are free for everyone, update packages are signed and every Windows release comes with an SBOM (CycloneDX).
- Standards: We develop BAVIS with IEC 62443-4-2 (self-assessment) and the EU Cyber Resilience Act (CRA) in mind.
Security in the upcoming version 4.0
In November 2026 we put BAVIS through an internal security audit and the new parts of version 4.0 went through a code review. The fixes are part of version 4.0. We develop security with IEC 62443-4-2 in mind.
- Encrypted device passwords. Passwords and tokens for PLCs, cameras and other devices are encrypted (AES-GCM) in the project and in older revisions. Anyone who gets only the project file cannot read them.
- Stronger user passwords. Passwords are stored with PBKDF2-SHA256 and 600,000 iterations. They are re-hashed automatically at the first sign-in.
- Sign-in never in the address. The session token never appears in the URL, so it cannot leak into browser history, proxy logs or a shared link. Images, downloads and live data use short-lived tokens.
- Limits for unauthenticated requests. Without sign-in the server accepts at most 512 kB per request and 120 writes per minute from one address.
- Permissions on every API route. Every interface route checks permissions, and an automated test enforces this for every new one too.
Support and services
Support is optional
The licence is perpetual and works without support too. Prices excl. VAT.
Without support
- maintenance releases of the purchased version (e.g. 3.1.x)
- security fixes – free for everyone
Support: 20% of the licence price a year, at least CZK 3,000
- upgrades to new versions (4.0, 4.1…) at no extra cost
- questions by e-mail about operation and settings
- priority fixing of reported bugs
- basic tasks: help with updates, restoring from a backup, licence check
Connection to the Benešl Automation Central: CZK 400 a month per installation
- remote monitoring: status, alarms, versions, backups
- remote help through Central
- can be ordered without support too
- We always reply within 3 working days.
- Project work (screens, connecting devices, logic) is not part of support – we prepare it to measure, priced by complexity.
- When resuming interrupted support, the missed years are paid, or a new version is bought.
A question about versions or support?
Tell us which version you have and what you need. Send a security issue with the subject “BAVIS – bezpečnost”.