Known Limits
Current boundaries of the GA product. It keeps evaluations honest and sets the preconditions for the 7‑day export promise.
Last updated: 2026-11-02
Capacity and Scope
7-Day Export Preconditions
Strict preconditions apply to the 7-day export promise.
- Up to 100 sites in scope (phased above 100)
- Agent installed on a host that can reach the EU endpoint over HTTPS (443)
- Outbound egress permitted to EU endpoints (TLS 443)
- Baseline configuration delivered on Day 0
Optional mappings (including NIS2) do not change the underlying evidence. See Known Limits and the acceptance checklist.
- Evaluation fit is strongest at 20–100 sites; < 5 sites are typically disqualified.
Protocols and Integrations
- Today: host health of the agent computer (CPU, memory, disk, uptime, load) every 30 seconds, buffered through outages. Planned (1.3.0): SNMP v2c/v3. Switches over SNMP are tested on one real device (a MikroTik hEX), UPS only on a simulator, power strips not tested yet. Redfish is planned. Not planned yet: IPMI, HTTPS checks, syslog.
- Not supported today: BACnet/Modbus building systems (post‑pilot roadmap), remote control actions (two‑person rule planned), broad SCIM user provisioning (limited support; roadmap)
- An API is available. There is no connector catalog.
Data and Residency
- The agent sends technical readings only. By default the agent ID is the host name, so pick an ID that does not identify a person.
- EU‑only hosting with named providers; no cross‑border transfer unless explicitly configured by the customer for external backups.
- Evidence exports include control mapping, lineage, and a reproducible hash.
Offline Behavior and Continuity
- Default offline buffer is ≥ 24 hours per agent; Tested on our own test environment at 30/60/120-minute outage windows, using an earlier development build of the agent (June and September 2026), with backfill after reconnect.
- Extremely long outages beyond local storage capacity will not retain full‑fidelity metrics.
- Continuity log is hash‑chained and tamper‑evident; if local system clocks drift heavily, continuity ranges may display skew until NTP resync.
Security Model
- SSO included at all paid tiers (OIDC/SAML). Broad SCIM/Just‑in‑Time auto‑provisioning is limited today.
- Audit log is hash‑chained and tamper‑evident: if a record changes, it shows; administrative deletes are not supported by design.
- The agent runs as an unprivileged service user and reads host health only.
- The agent signs in to the API with a per-organisation API key over HTTPS. Agents do not use client certificates (mTLS) today. A stolen key works until it is revoked.
Performance Budgets
- Measured on a test machine, host health only (CPU, memory, disk, uptime, load): CPU under 1% average, RAM under 50 MB, disk buffer about 0.3 MB for a 24-hour outage, egress about 2 MB per day. These figures will change when device collectors are added.
Device and OS Support
- The agent is packaged as a .deb for Ubuntu LTS and Debian stable.
- Windows hosts: no packaged agent in this release.
- Pilot proof needs at least one host that can run the agent and reach the EU endpoint.
Reliability and SLA Notes
- Product is designed for monitoring and compliance evidence; it is not a real‑time control system.
- Ingest lag SLO is measured as P95 over a rolling window; transient spikes can occur during backfill after outages.
- The 7‑day export promise is void if preconditions are not met; once rectified, the promise applies to the remaining scope.
Browser and Network Requirements
- Supported browsers: current Chrome, Edge, Firefox, Safari
- TLS 1.2+ outbound required to EU endpoints
- Accurate NTP time sync required on monitored hosts and collectors
- Proxy environments must allow websockets or HTTP/2 for live views; fallback polling increases lag
Roadmap Items (post‑GA)
- Additional adapters: BACnet/Modbus for building systems
- Alert rules and anomaly detection (planned)
- Remote actions (reboot/outlet/setpoints) with a two‑person rule
- Expanded SCIM and granular SSO mappings
- Carbon‑aware scheduling and energy orchestration
Known Vendor Quirks
- NAT hairpinning can block local dashboards; prefer direct outbound patterns from the agent.
Related Resources
Cross-reference with our acceptance checklist and documentation for complete evaluation criteria: