Nexus Intelligence
Also known as: Nexus Industrial, getnexus.ai
Self-improving operations platform for factories: it builds a live model of the plant from PLC, SCADA, historian, MES and UNS data, watches the line continuously for bottlenecks and OEE losses, dispatches swarms of long-horizon agents to trace each loss to its root cause, and brings findings and recommended actions to the team for approval, with every action compounding into a context graph of the plant.
Nexus Intelligence sells an AI platform for factory operations. Its pitch is that a plant loses output in a thousand small ways that nobody has time to chase, and that agents can chase all of them at once.
The platform works in five stages. It builds a live model of the factory (equipment, sources, sinks and material flow), mapped to the plant's inventory of PLCs and low-level equipment. It then watches the line continuously, surfacing bottlenecks, work-in-progress build-up and OEE losses as they emerge, and runs what-if simulations against the live model to size each opportunity so a team knows what to tackle first.
Swarms of agents are dispatched to wherever the plant is underperforming, in the way process and manufacturing engineers move around a plant today, each agent holding a long-horizon task across equipment, process or quality. An agent will trace an hourly throughput miss down to the sticky valve that caused it, whether that takes minutes or hours.
What the agents cannot do is act on their own. Findings and recommended actions go to the team, and a person approves before anything takes effect. Agents start read-only and their boundaries widen only when the customer approves them; as they earn trust they can handle small things proactively with permission, such as filing a preventive work order on a wearing part before it causes downtime. Every action and every piece of data compounds into a context graph of the plant (equipment, recipes, work orders, maintenance, downtime and people), which the company describes as institutional knowledge that never walks out the door.
Connecting to a factory is the hard part of this market, and the company's answer is a library of data connectors covering the whole stack: proprietary control system file formats and SDKs, PLC and DCS, SCADA, historians, MES, and unified namespace. Most deployments are said to go live in under two weeks, with forward deployed engineers working alongside the plant's own process experts to build the system around that site.
The platform runs in the cloud, in an enterprise VPC or on-premise, with the customer's choice of model through bring-your-own-key. It is SOC 2 Type II certified, and audit logs, agent-level observability and approval controls come as standard, so a team can see what each agent did, what it can reach, and which actions require sign-off. Pricing is not published; the only route in is a demo.
Nexus Intelligence, Inc. sells to manufacturers, system integrators and equipment OEMs.
Vendor details
Canonical URL
https://getnexus.ai
Category
Enterprise operations agent
Company status
independent
Use cases & customers
In practice
A quality drift starts on the line and nobody catches it until scrap piles up. Nexus watches the line continuously, dispatches agents the moment the drift appears, and brings the finding and a recommended action, with its reasoning, to the team for approval.
Your best process engineer is the only one who knows why the line keeps slowing down. As agents investigate and act, Nexus adds each finding to a context graph of the plant, so that knowledge stays when people leave.
Incidents on the floor get a ticket but no context. Nexus triages the incident, generates the ticket with an explainable reason, and keeps every action governed and auditable.
Sources & related URLs
Related / legacy domains
Research sources
Agentic Index coverage score
10.0 / 14 capabilities · 71%
| Integrations & Tool Calling | Full |
|---|---|
|
Nexus reads every layer of the factory stack through a library of connectors and writes back into the customer's maintenance system by filing work orders. Agents can file a preventive work order on a wear item before it ever causes downtime. A work order is a record created in the customer's maintenance management system, and the platform's own interface shows the completed action, a preventative work order submitted with an identifier. So Nexus takes authenticated action in a system it does not own. The read side is unusually deep. The connectors integrate natively with all layers of the factory stack, from proprietary control system file formats and SDKs to UNS. The named layers are PLC/DCS, SCADA, historian, MES and UNS, and the earlier site also named ERP and CMMS. Control systems are proprietary, versioned and specific to each vendor, which is the work that makes industrial integration expensive, and the claim of going live in under two weeks is a claim about that work. There is no published connector catalog, named CMMS or MES product, or authentication model. Sourcegetnexus.ai section, stage 04, architecture diagramread 2026-09-14 |
|
| Workflow Orchestration | Full |
|
Swarms of specialized agents go wherever the plant is losing output, each running a long investigation. They work as a team, the way process and manufacturing engineers do today, and each agent focuses on a long-horizon task across equipment, process and quality to augment and enable the customer's team. They are specialists working together on one problem, sent to wherever the loss is. One investigation runs many steps. An agent can trace an hourly throughput miss all the way down to the sticky valve that caused it, whether that takes minutes or hours, following a chain of inference across equipment, process and quality data with no fixed script. The interface shows an agent investigating cap torque drift, correlating reject spikes to filler valve lag and pulling thirty-day OEE history as concurrent threads. The whole product is a five stage pipeline, Map, Instrument, Dispatch, Act and Learn, with dispatch and action as separate stages, so coordination is part of the platform's design, not a feature of one agent. No orchestration runtime or workflow graph is named, and there is no customer authoring surface or versioning. Sourcegetnexus.ai stages 01 to 05, hero and interface sectionsread 2026-09-14 |
|
| Knowledge Grounding & RAG | Full |
|
A live model of the plant keeps growing as a context graph, so new knowledge enters through data and actions, not retraining. Stage one builds a live model of the factory (equipment, sources, sinks and material flow), mapped to the asset inventory of PLCs and low-level equipment. Stage five maintains it, as all actions and data compound into a context graph of the plant, institutional knowledge that never walks out the door. Nothing is retrained to admit a new asset, recipe or work order. The sources are indexed, refreshed continuously and permissioned. The data fabric spans PLC/DCS, SCADA, historians, MES and UNS, and agents start read-only and expand only when the customer approves the boundaries. Agents query the structure. An agent traces an hourly throughput miss down to the sticky valve that caused it, which is a traversal of the graph, not a model remembering a fact. The graph holds equipment, process and quality data, recipes, work orders and maintenance, and people and downtime, so its subject is this plant's own expertise. Agents generate tickets and notifications with clear explainable rationales, and the interface shows the working thread behind a recommendation. That shows which evidence shaped an output, though less precisely than citing documents would. Sourcegetnexus.ai stages 01, 02 and 05, trust-and-security section, architecture diagramread 2026-09-14 |
|
| Human Oversight & Guardrails | Full |
|
Every agent finding and recommended action comes to the team for approval before it takes effect, and agents start read-only. Approval is stage four of five, named Act, where the customer approves and the actions stick. When agents finish an investigation, they bring findings and recommended actions straight to the customer's team. A person stands between the agent's conclusion and its effect, as a published step in the workflow. Agents monitor the line, trace every loss to its root cause, and act with the team's approval. The customer controls how far permissions go. Agents start read-only and expand only when the customer approves the boundaries, and the team sees what each agent does, what it can access, and which actions need human approval. Access is denied by default and widened only with the customer's approval, and the customer sets which actions need sign off, so review comes before the action, not after it. Autonomy widens in one place, and there it is scoped and still needs permission. As agents learn over time, they can begin to resolve small problems proactively, with permission, such as filing a preventive work order on a wear item before it ever causes downtime. No approval queue interface, escalation matrix or configurable threshold is shown. Sourcegetnexus.ai hero, stage 04 and trust-and-security sectionsread 2026-09-14 |
|
| Security, Identity & Governance | Full |
|
The customer controls each agent's access boundary, which starts read-only, and the platform is SOC 2 Type II certified. Security and control start at the plant floor. Type II tests how controls operate over a period, not only their design at one point. The team sees what each agent does, what it can access, and which actions need human approval. Agents start read-only and expand only when the customer approves the boundaries, so nothing widens without the customer's say. The earlier site also described permissions managed by project and by user. An unrelated platform also called Nexus publishes different certifications, which do not apply to Nexus Intelligence, Inc. The home page has a Trust and Security section, but there is no trust center or separate security page and no report offered on request. The certificate's number, auditor and period are not given, and neither single sign on nor SAML is mentioned. The footer carries only Terms of Use and Privacy Policy. Sourcegetnexus.ai trust-and-security section and footer, read in fullread 2026-09-14 |
|
| Observability & Auditability | Full |
|
Audit logs, observability and approval controls come out of the box, at the level of each agent, not each machine. The team sees what each agent does, what it can access, and which actions need human approval. Each run can be followed in the product. The interface shows an agent's working thread, such as investigating cap torque drift and correlating reject spikes to filler valve lag, next to the recommendation it produced, its severity and where it was sent. Intermediate steps are displayed and the output is attributed, so a run can be reconstructed. The outputs carry their reasoning too, since agents generate tickets and notifications with clear explainable rationales. Separately, continuous monitoring of controllers, historians and maintenance data watches the customer's factory, not the agents. There is no published retention period, export path, log schema or SIEM integration. Sourcegetnexus.ai trust-and-security section, stages 03 and 04, interface detailread 2026-09-14 |
|
| Memory & State Persistence | Partial |
|
Agents hold state across investigations lasting minutes or hours, but nothing stores what an agent concluded on one run for it to consult on the next. Nexus sells long-horizon AI agents, and an investigation can take minutes or hours. The interface shows a persisted agent in a working state with a named standing task. That state is held within a task, by an agent through a long investigation or by a watchdog between events. Agents write into the context graph, where all actions and data compound into institutional knowledge that never walks out the door. But the graph holds domain knowledge about the factory, from equipment and recipes to work orders and people, whoever contributed it, and it is not an agent's own memory. No memory scope, lifetime or purge path is described, and nothing stores an agent's prior conclusions apart from the plant graph. The line that every fix makes the next one faster describes learning absorbed into the product. Agents that begin to resolve small problems proactively are being given wider permission, not keeping more state. Sourcegetnexus.ai hero, stages 03 to 05, interface detailread 2026-09-14 |
|
| Deployment & Data Residency | Full |
|
Three deployment targets are offered, cloud, the customer's own enterprise VPC, or on premises. Under Flexible Deployment Options they are listed as Cloud, Enterprise VPC and On-Prem. Two of those are customer environments, the customer's own VPC and the customer's own premises, and the customer chooses between them. On premises is the option that matters in this market, and it fits the product. The platform reads control systems, SCADA, historians, MES and UNS on a plant network, and industrial customers commonly refuse to route control system data off site. Most deployments go live in less than two weeks, with Forward Deployed Engineers working on site. There is no region list for the cloud option and no installation or sizing documentation. Nothing claims an air gapped option, which is a different commitment from on premises. Sourcegetnexus.ai flexible-deployment section and sectionread 2026-09-14 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
Typed agents are described but not cataloged, and each deployment is built with the customer. Each agent focuses on a long-horizon task across equipment, process and quality, and agents are dispatched as swarms to areas of underperformance. The interface names a standing one, a preventive maintenance watchdog. These are named kinds of agent doing distinguishable work, with no catalog to choose from. There is nothing to browse or select. The site has four items in its navigation, from Home to Book a Demo, and no product menu, agent roster or pages for individual agents. Delivery is custom work. Each system is fully customized to the plant, and Forward Deployed Engineers work with the customer's manufacturing and process experts to build a self-improving system around the plant's own domain. Agents built this way are bespoke work, not prebuilt units taken from a shelf. Earlier materials described prebuilt ops agents for factory workflows and industrial coding agents tuned to output control languages, plus drag and drop workflow building. The coding agents no longer appear on the site. Sourcegetnexus.ai stage 03, forward-deployed-engineer section, site navigationread 2026-09-14 |
|
| Triggers & Channel Coverage | Full |
|
The production line is watched continuously, and agents are dispatched the moment a loss emerges. Stage two of the platform flow, Instrument, watches the line in real time, 24/7, and surfaces bottlenecks, WIP accumulation and OEE losses the moment they emerge. Agents also fire on incidents and quality drifts, and on production constraint issues. A line watched without pause that fires agents the moment something emerges is a real event trigger. Events on the line are the only trigger. There is no schedule or webhook, and no chat, email, voice or other conversational path, so work reaches the agents from the line, not from people or other systems. Sourcegetnexus.ai platform flow, stage 02, and the June basisread 2026-09-15 |
|
| Model Flexibility & Routing | Full |
|
The customer chooses the model and supplies its own key. Nexus can be deployed in the cloud or on premises, with the customer's choice of model through BYOK. BYOK goes further than a selector the vendor runs, because the model relationship, the account and the commercial terms all belong to the customer. It is offered as a platform property beside the deployment options. No provider is named, which here reads as agnostic by design, since it sits beside an explicit offer to bring your own key. There is no list of supported models, routing policy or selector interface. An earlier product tuned large language models to output IEC-61131-3 Ladder Logic and Structured Text for industrial control. That was the vendor's own model work, not a customer choice. Sourcegetnexus.ai flexible-deployment sectionread 2026-09-14 |
|
| APIs, SDKs & MCP Extensibility | Not documented |
|
There is no API, SDK or MCP server that would let an outside system call the platform. The SDKs Nexus mentions belong to other vendors. Its connectors integrate natively with all layers of the factory stack, from proprietary control system file formats and SDKs to UNS. Those are the control vendors' SDKs, which Nexus uses to reach a PLC or a historian, the opposite direction from a developer surface of its own. Nothing on the site points inward. The navigation has four items, from Home to Book a Demo, and the footer carries only Terms of Use, Privacy Policy and LinkedIn. There is no developers entry or documentation host, no API reference or webhook, and no embeddable component. Nexus sells to system integrators and equipment OEMs, so an API may well exist under contract, but nothing published claims one. An earlier product line imported, edited and exported industrial project files such as Studio 5000 formats, and it no longer appears on the site. Sourcegetnexus.ai section, navigation and footer read in fullread 2026-09-14 |
|
| Testing, Debugging & Optimization | Not documented |
|
Nothing tests or measures the agents, and what Nexus simulates and improves is the factory. No change to an agent goes through a harness, scored cases or a golden set, and no accuracy figure, judge or release gate is published. The closest feature tests something else. The live process model runs continuous what-if simulations to size every opportunity and show which problem to tackle first. That simulates the plant to rank interventions, so its subject is the factory, not the software. Nexus calls itself the self-improving OS for manufacturing, and stage five says every fix makes the next one faster. What improves is the factory, as throughput, quality and capacity improve month over month. Nothing published measures the quality of agent output either, such as an acceptance rate for recommendations or a false positive figure. The one number given is a go-live time of under two weeks, which measures implementation. An earlier controls engineering product validated generated PLC code against safety and regulatory requirements. It no longer appears on the site, and validating the customer's control code is the product's job, not a test of the agent. With Forward Deployed Engineers on each deployment, a validation practice may exist without being published. Sourcegetnexus.ai stages 02 and 05, hero and titleread 2026-09-14 |
|
| Browser & Computer Use | Not documented |
|
Action runs through industrial system integrations, not through a browser or a computer. No hosted or local browser, desktop session or remote computer control appears. The path is machine to machine at both ends. Connectors read control systems, SCADA, historians, MES and UNS at one end, and a work order is filed into a maintenance system at the other, with no screen in the loop. This is an industrial agent driven by protocols, not one that works through engineering software interfaces. UNS topics, historian tags and PLC file formats have no screen to break when an interface changes, so what can fail here is a connector or a tag mapping, not a moved button. The agent interface is a surface people read, and the Forward Deployed Engineers who configure the system are people operating software. An earlier ability to import and edit Studio 5000 project files was file manipulation, not operating the engineering IDE. The architecture is described precisely enough at both ends that a path that drives screens is unlikely. Sourcegetnexus.ai section, stages 02 to 04, architecture diagramread 2026-09-14 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Custom pricing (book a demo)
Related vendors
- 11th Estate — Agentic platform whose AI engine scans markets, matches an…
- Abacum — FP&A platform for growing companies whose AI Modeler builds, edits…
- Adopt AI — AI native accounting and bookkeeping firm whose agents run…
- Aera Technology — Decision intelligence platform where an always on agent executes…
- Akro AI — On premise operational intelligence that automates document heavy…
- alfred_ — AI executive assistant that triages the inbox overnight and scores…
Alternatives to Nexus Intelligence
The closest documented capability profiles to Nexus Intelligence among enterprise operations agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Vibrium AI11.0 / 14Adds documented Testing, Debugging & Optimization
- Coworker11.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- Kinaxis10.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- Legora10.5 / 14Adds documented APIs, SDKs & MCP Extensibility
- Otel AI8.5 / 14A lighter documented profile than Nexus Intelligence
- Atomicwork12.0 / 14Adds documented APIs, SDKs & MCP Extensibility and Testing, Debugging & Optimization
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded