Security and deployment
Built for sites that cannot go down.
Where Klorad runs, how it changes, how it is secured and what it connects to. The material your tender and your security team ask for.
Runs where your data has to live.
The same platform as a managed cloud, a dedicated environment in the region you choose, or on your own network, air gapped if needed.
Changes only when you approve them.
Every component is versioned with its own changelog. Sites choose the release channel that fits their risk.
Stable
A dated release train that pins a tested set of components.
Long term support
One train a year, security and critical fixes only, for 24 months.
Your approval
On premise sites run long term support, so no untested change reaches them.
Critical commands take two people.
Lockdown or door release can require a second authorised operator, and every approval is recorded.
- 14:02:11 Requested
Security by design.
Single sign on
OpenID Connect and SAML, with your identity provider.
Encryption
In transit and at rest, everywhere the platform runs.
Append only audit log
Every event, command, approval and change, kept for review.
Secure development
Aligned with IEC 62443-4-1: threat model, SBOM and signed images per release.
Backup and restore
Documented procedures with stated recovery objectives.
Your obligations
Documentation that supports your NIS2 and critical entity duties.
Each organisation, its own data.
Data is isolated per organisation, with a dedicated database when you need it. Systems owned by another party can share status only, through a separate gate.
Open standards, no lock in.
- Data and control
- MQTT and Sparkplug B, webhooks, REST, OPC UA, BACnet, Modbus, OGC SensorThings, ETSI NGSI-LD, ONVIF
- Geometry
- IFC (ISO 16739), CityGML, CityJSON, glTF, OGC 3D Tiles, GeoJSON
- Identity
- OpenID Connect, SAML
Bring us your requirements.
Send us the security and deployment section of your tender. We will answer it point by point.