Discovery
Map supported devices and their physical and logical relationships across the infrastructure estate.
Menu
iFabric
Understand the infrastructure
behind every operation.
iFabric™ is Invences’ Autonomous Infrastructure Fabric, designed to bring discovery, observability, digital-twin evaluation and agentic operations into a shared infrastructure context.
Explore iFabric Enter the interactive tour See architectureAutonomous Infrastructure Fabric
iFabric / In focus
Understand your estate.
Automate its operations.
iFabric connects telemetry and topology across vendors to give agentic AI the operational context it needs. Its four modules link infrastructure discovery and observability with change simulation and governed remediation.
Inside iFabric / Interactive walkthrough
Follow the signal.
Find the next step.
Explore the estate. Investigate an issue. Review a governed response.
Enter the walkthroughCapabilities
Observability
Correlate telemetry, logs and KPIs across networks, GPUs, compute, storage, applications and Physical AI to detect anomalies and investigate causes.
Digital twin
Evaluate supported firmware, configuration and workload changes against a configured infrastructure model before production.
Agentic AI
Use operational context to investigate incidents, propose supported responses and carry out permitted actions through configured workflows.
iFabric / How it works
From signals to governed action.
Discovery, observability, digital twins and agentic operations. One shared context.
Find the estate. Reveal its dependencies.
Infrastructure evidenceReasoning / evaluationAuthorized actionOperator review
Illustrative flows. Model coverage, integrations and permitted actions depend on the deployment.
Infrastructure inventory and operational signals feed discovery, observability and shared topology/event context. Operators can see the estate in Command Center without running a change or an action. A proposed change can be evaluated in the digital twin. nLLM supports agentic reasoning; configured actions require authorization, and fresh observations return to operators for outcome review.
Architecture & operating boundaries
Infrastructure inventory and operational signals feed discovery, observability and shared topology/event context. Operators can see the estate in Command Center without running a change or an action. A proposed change can be evaluated in the digital twin. nLLM supports agentic reasoning; configured actions require authorization, and fresh observations return to operators for outcome review.
- Infrastructure. Supported infrastructure supplies inventory, telemetry, logs and API events through the configured ingestion integrations.
- Discovery. Discover physical and logical relationships and enrich the shared infrastructure topology.
- Observability. Correlate infrastructure signals against the known estate to expose service health and anomalies.
- Shared context. Normalized events and topology give the operating modules a common infrastructure context.
- Digital twin. Evaluate supported firmware, configuration or workload changes against the model; send results for review before any deployment authorization.
- nLLM reasoning. Ground an agentic investigation and proposed response in operational evidence and relevant knowledge.
- Authorization. Check explicit policy and action authority. An unsupported or unauthorized proposal does not proceed to execution.
- Configured tools. Execute the permitted workflow against a supported infrastructure target within the approved scope.
- Fresh evidence. Collect post-action observations for verification and follow-up; a completed tool call is not proof of a recovered service.
- Command Center. Give operators topology, health, evaluation results and outcome evidence with their operational context.
This is a functional product architecture, not live telemetry or a physical deployment map. Discovery and observability enrich shared context; they are not exclusive alternatives or a compulsory serial pipeline. The twin evaluates supported proposed changes and is not a required hop for normal observation or every incident. The approved-response view illustrates the authorized path only. Missing evidence or denied authority stops execution for review. Authorization can use configured policy and approval integrations, including gFabric where deployed; nLLM advice does not grant permission. Tools act only on supported targets within scope. Fresh evidence establishes the observed result, including unresolved issues; the diagram does not assume successful recovery. Command Center presents topology, events, findings and outcome evidence. Timing is illustrative; repetition restarts the explanation.
Views
Discovery. Inventory and relationships enrich shared topology and become visible to operators. Discovery does not require a twin evaluation or a remediation action.
Observability. Infrastructure signals become contextual health and anomaly evidence for operators. Shared discovery context informs observation; the view highlights the signal path.
Digital twin. A proposed change uses shared infrastructure context and supported model coverage. Evaluation results return to operators; the model does not itself authorize production deployment.
Approved response. This view illustrates an approved agentic response: operational evidence grounds nLLM reasoning, authorization limits the action, configured tools execute it, and fresh signals return to Command Center for outcome review.