01
Network context
Bring network observations and the operator’s decision boundary into the same view.
Built for ISP operations
One clear picture.
A coordinated response.
Cortex is being built to connect network context, customer impact, and your team’s next steps—with AI operations teammates that keep people in control.
Product preview · Illustrative scenario
An illustrative operations moment
Signals become a shared response.
- Network
- Related observations
- Field
- Evidence from the work
- Customer care
- Context for a clear update
Operator review required
AI-generated illustrative scenes
Cortex is designed to turn fragmented operational signals into a shared, evidence-backed view of the work—so the team can move together without giving up control.
The operator’s reality
Your tools have the signals.
Your team needs the whole picture.
Alerts, tickets, network views, and field updates often tell separate parts of the same story. Cortex is being built to help ISP teams connect that context and keep the response moving.
02
Field evidence
Link field findings to the investigation while the work is still moving.
03
Customer coordination
Give customer care the same incident context to prepare a clear update.
An illustrative workflow
From scattered signals to a shared response.
Select a step to see how Cortex is intended to support the team. This example prepares work for people to review; it does not perform a network change.
01 · Understand
See the evidence and what is still uncertain.
Cortex is designed to bring network observations and customer reports into one view. The evidence stays distinct from the interpretation, and uncertainty remains visible.
Example status: investigation forming
Shared evidenceIllustrative
Network
Related reachability changesObserved across several access points
Observed
Care
Reports share a service areaImpact pattern under review
Correlated
Still unknownFault domain and restoration path need operator investigation.
02 · Prepare
Give specialists one situation to work from.
Named teammates assemble investigation context, suggested next steps, and a customer-update draft. Each contribution stays attached to the shared incident and its evidence.
Example status: response package in draft
Response packageNot yet approved
OC
Operations CommanderAlign investigation owner and next checks
NA
Network AnalystOutline likely fault domains and missing evidence
CC
Customer Care LeadPrepare a clear customer update for review
03 · Review
Review the proposed work before anything consequential.
The operator reviews the evidence, proposed next steps, and communication draft. Actual system changes remain subject to the ISP’s local policy and authorization.
Example status: operator decision required
Operator reviewDecision boundary
- Evidence
- Linked and available for inspection
- Customer update
- Draft only · not sent
- Network change
- No change proposed in this example
Human approval remains requiredPermissions and local policy govern what may happen next.
Understand step selected.
Cortex in the field
Crew Attendance, in use at HVGTEC.
HVGTEC is already using and field-testing the Crew Attendance module of Cortex v2 in its ISP operations. Watch the presentation to see the field workflow behind it.
Operations teammates
Specialist help.
Shared context.
Each teammate contributes a distinct perspective to the same operator-owned situation. They prepare and analyze work within defined roles; they do not grant themselves permissions.
01 Coordination
Operations Commander
Keeps the investigation aligned, tracks ownership, and assembles a concise decision package.
02 Network
Network Analyst
Interprets topology, telemetry, provenance, and the likely fault domains behind the service issue.
03 Customer care
Customer Care Lead
Connects the network situation to customer impact and prepares clear communication drafts.
Control and integration approach
Your operation.
Your rules.
Cortex is designed to work alongside the systems an ISP already uses. It coordinates context and work without asking the team to abandon its operational tools.
The Cloud is designed to support shared analysis and coordination. Cortex Edge is designed to keep source credentials and execution control at the ISP, where local policy can be applied.
Cloud coordinationContext · analysis · shared work
Proposed work
Operator policyPermissions · approvals · decisions
Authorized intent
Cortex EdgeCredentials · local revalidation · execution control
Designed to connect context from
- Network monitoring
- Customer systems
- Field work
Common questions
What operators should know.
Who is Cortex for?
Cortex is being designed for small and mid-sized ISP teams that need a clearer way to coordinate network, customer, and field operations.
Does it replace my existing tools?
The product direction is to work alongside existing network and customer systems, bringing their operational context into coordinated work rather than replacing every source tool.
What do operations teammates do?
They are named specialist roles designed to analyze evidence, coordinate investigation context, prepare suggested next steps, and draft communications within defined permissions.
Can AI change my network?
Models do not decide what may execute. Consequential work is intended to pass through deterministic policy, required human approval or pre-authorization, and independent local revalidation by Cortex Edge.
Is Cortex available today?
Cortex is in development. HVGTEC is already using and field-testing its Crew Attendance module. Wider availability and other supported integrations will be confirmed separately.
Contact
Let’s talk about Cortex.
Hiel Gagarin
CEO, HVGTEC