How each platform builds operational context
Foundry agents
Rosetta, Loom, TicketMaster, Artist, Herald, Sculptor; MCP and A2A.
Collaboration
Natural language, dashboards, ChatOps, ITSM workflows, query-backed APIs.
Knowledge
Anomaly detection, correlation, causation, forecasting, knowledge graph.
Data Hypervisor
ML schema inference, enrichment, ELT raw preservation, routing.
Collection
Horizontal engines near the source; push and pull; independent scaling.
Sources
Any vendor’s devices, cloud, CMDB, IPAM, ITSM, tools, and files.
NetBrain
AI and automation
AI assistant; no-code Runbooks; intent-based automation.
Problem diagnosis
Automated diagnosis triggered by tickets, alerts, or users.
Dynamic maps
On-demand maps and path analysis.
Digital twin
Model built from configurations, CLI, and routing tables.
Discovery
Periodic discovery and benchmarking via CLI, SNMP, and APIs.
Sources
Multivendor network devices, SDN controllers, and cloud networks.
Where NetBrain falls short architecturally:
Snapshot-based model: NetBrain’s digital twin is built from periodic discovery and benchmarks, not continuous telemetry. Selector models live telemetry continuously.
Automation over monitoring: NetBrain diagnoses issues by running automation when triggered; it relies on other tools to detect them. Selector detects, correlates, and determines cause itself.
Intent and runbook maintenance: Diagnosis quality depends on authored intents and runbooks. Selector’s causation models need no authored logic.
Use case 1: Observability
Multivendor data collection
NetBrain gaps
Model built from periodic discovery rather than continuous telemetry.
Flow and log analytics not described.
BMP ingestion not described.
Selector value
Streaming telemetry, flow, routing, configuration, and context from any vendor in one pipeline.
Routing changes tied to the services they affect, from BMP and IGP state on the customer’s own devices.
Ingestion from files and streams for data with no API.
Use case 1: Observability
Data normalization and enrichment
NetBrain gaps
Data reflects the last discovery or benchmark, not live state.
Diagnosis depends on authored intents and runbooks.
Raw telemetry history not retained.
Selector value
Learned normalization: no parsing templates or rules to maintain.
Raw records retained with original timestamps for replay and re-analysis.
One enrichment layer applies topology, ownership, maintenance, and criticality to every signal.
Use case 1: Observability
AI-powered operational analytics
NetBrain gaps
Detection relies on other monitoring tools.
No per-series anomaly detection described.
Optical failure prediction not described.
Selector value
Per-series models retrained every 30 minutes detect anomalies no threshold would catch.
Automatic correlation across network, cloud, and application signals in one model.
Optical failure prediction and capacity forecasting before impact.
Use case 2: Event intelligence
Event correlation and root cause
Selector example
The Loom agent resolved 214 alerts across six tools to a single fiber cut on one long-haul span, labeled routing reconvergence and cloud failover as consequences, and flagged the secondary path at 78% utilization as the next risk.
How NetBrain engages
A ticket or alert triggers a NetBrain diagnosis that runs intents against the digital twin. The underlying alert flood and telemetry stay in the monitoring tools.
NetBrain gaps
NetBrain diagnoses triggered issues rather than correlating event streams.
Causation relies on authored intents.
Telemetry replay not described.
Selector value
Alert floods collapse into one incident with a named cause, consequences, and next risk.
Telemetry, logs, flow, and configuration correlated with alerts in one model.
Every finding is traceable and reproducible with Network DVR.
Use case 2: Event intelligence
Agents, ITSM, and governed action
NetBrain gaps
Runbook and intent authoring needed for automation.
Governed agents built from described playbooks not described.
An MCP server exposing NetBrain insights not described.
Selector value
Sculptor builds governed agents from the team’s own playbooks, acting only on verified findings.
MCP server shares insights and governed actions with other agent platforms.
Every Foundry agent is available now, in every deployment model.
Functionality gained with Selector
Capabilities a NetBrain customer adds with Selector, whether Selector runs alongside NetBrain or replaces it.
1. Continuous, not snapshot
2.Deterministic diagnosis
3. Detection beyond thresholds
4. Streaming and routing depth
5. Full-fidelity history
6. No templates to maintain
7. Your playbooks as agents
8. Governed action through MCP
9.Custom outcomes with engineers
10. No rip-and-replace
Selector patents driving innovation
Selector vs. NetBrain at a glance
The bottom line
NetBrain is a strong network automation and mapping platform with a configuration-based digital twin, dynamic maps, and intent-based diagnosis.
Selector is built for a different starting point. It models live telemetry continuously, detects and correlates issues itself, determines cause without authored intents, and puts governed agents on top, including agents built from your own playbooks.
30 min
Model retraining cycle
99.9%
Noise reduction
8x
Faster resolution per P1