Resources
Frequently Asked Questions
Common questions about how Velorona works, what it does and doesn't do, and how it's evaluated.
What is Velorona?
Velorona is a read-only, pre-escalation decision-intelligence layer for telecom network operations. It analyzes existing network telemetry to help identify early signs of service degradation — before conventional monitoring reaches an alarm or escalation threshold. Velorona is designed to support earlier investigation, not to replace network operations or existing monitoring systems.
How is Velorona different from traditional network monitoring and alarm systems?
Traditional monitoring and alarm systems are built to flag conditions that already cross a defined threshold. Velorona is designed to work earlier in that timeline — looking for degradation patterns in existing telemetry that stay below those thresholds, in the interval before a conventional alarm would fire. It does not replace alarm or monitoring infrastructure; it is intended to sit alongside it as an earlier decision-support layer.
Is Velorona read-only, and does it modify network traffic or configuration?
Yes, it is read-only. Velorona is out-of-band: it observes existing network telemetry and does not modify network traffic, configuration, or the forwarding or control plane of the network it monitors.
Does Velorona inspect subscriber traffic or use deep packet inspection (DPI)?
No. Velorona is designed to operate on network telemetry — performance and signal-quality data — rather than subscriber traffic payloads, and it does not perform deep packet inspection.
How is Velorona deployed in a telecom network?
Velorona is deployed as a read-only, out-of-band layer that uses an operator's existing network telemetry — it does not sit inline in the data path. Deployment scope and integration details are worked out individually with each operator.
Can Velorona be evaluated without changing the production network?
Yes — that's the intended evaluation path. Velorona is designed to be evaluated first through historical replay against an operator's own recorded telemetry, and can run in shadow mode alongside existing systems without any production change. As of now, no operator-network pilot has been completed yet — historical replay is the mechanism by which that evidence gets built.
What telemetry does Velorona use?
Velorona works from telemetry an operator already collects — network performance counters, signal and link-quality indicators, and comparable existing monitoring data. The exact telemetry set is scoped with each operator individually; specific detection signals and features are not published, in order to protect the underlying decision logic.
What does Velorona provide to network operations teams?
Velorona provides earlier indication that a network may be entering a degraded state, along with context around that signal — a basis for deciding whether it warrants investigation before it reaches a conventional alarm or escalation point. It is a decision-support input, not an automated response system.
Does Velorona replace our existing NMS, OSS, or monitoring systems?
No. Velorona is designed to work alongside existing NMS, OSS, and monitoring systems, not replace them — it adds an earlier decision-support layer on top of what's already in place.
How is Velorona different from adding more alarms or thresholds?
Adding more alarms or lowering thresholds tends to increase the number of alerts an operations team has to triage, without necessarily surfacing degradation earlier. Velorona is designed around a different approach — looking for degradation patterns in the data itself, in the period before a threshold-based alarm would trigger, rather than adding more threshold-based rules.