Common questions

Yes. InfraVero is a consolidation layer, not a replacement. MQTT and RTSP are shipped today; additional connectors are scoped per pilot, so we do not claim protocols we have not delivered.

It answers questions in plain language with the sensor readings and time windows behind every answer, explains why any alert fired using that same evidence, and proposes changes, acknowledging an alert or adjusting an alert rule, that it never applies until you confirm. Anomaly detection cross-checks several independent signals and alerts only when they agree, and it also catches patterns that have never occurred before, not just threshold breaches. Short-horizon forecasts with a calibrated confidence range, and alerting that tunes itself to each asset’s own normal, are built and roll out per deployment.

InfraVero Intelligence runs entirely inside your deployment. Your questions, documents, and telemetry are processed on-site and stay there. Connecting an external AI provider for a specific use case is possible, but it is an explicit choice you make, never a default.

No. InfraVero Intelligence runs inside your deployment and is not adapted to your data. Your telemetry, uploaded documents, and questions are not sent anywhere for training.

The core platform runs on-site. Dashboards, ingestion, alerting, and InfraVero Intelligence keep working. When connectivity returns, remote browser access resumes automatically.

No. All telemetry stays on-site, in your environment. We provide the appliance, platform, updates, and support, but your operational data never leaves your deployment unless you explicitly configure an external integration.

None of your own. NTALabs specs, supplies, and installs the sensors, cameras, and the appliance that runs InfraVero, sized to your site. It stays on your premises for the contract term and NTALabs maintains it. A pilot fits on a compact appliance, so there is no server room or procurement cycle to start. The deployment calculator gives you a rough size before a call.

You can have live data within a day of setup. A focused pilot, landing a dozen sensors and one dashboard your team opens daily, typically runs two to four weeks before the value is obvious.

No. InfraVero is proprietary software, available through an early adopter pilot at no cost, with commercial tiers for production deployments. It runs on-site on an appliance NTALabs supplies and maintains, and NTALabs provides deployment, updates, and custom integrations.

InfraVero routes alerts through approved notification workflows chosen during the pilot. The goal is simple: critical context reaches the right role quickly, operators can acknowledge what happened, and the deployment avoids opening unnecessary inbound access.

Yes, when the pilot includes an approved interaction workflow. Operators can acknowledge alerts, ask follow-up questions, or ask InfraVero Intelligence to adjust an alert rule, which it proposes for confirmation rather than applying directly. Every answer stays tied to the evidence behind it.