Agentic Index
MakinaRocks vs Nexus Intelligence (2026)
Both vendors last verified
MakinaRocks and Nexus Intelligence both bring agents to industrial operations, at opposite ends of the estate. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
MakinaRocks ships Runway, an enterprise AI OS managing the full model lifecycle in mission critical and air gapped environments, alongside DrawX, an agent product that turns engineering drawings into structured, searchable assets for estimating and bid decisions, while Nexus Intelligence's agents monitor PLC, SCADA, MES, and ERP and act end to end on plant operations. Both are contact sales. Choose MakinaRocks for the engineering and modeling layer. Choose Nexus Intelligence for plant floor operational agents.
On the Agentic Index self hosted platform ranking, MakinaRocks and Nexus Intelligence both clear the bar: each documents both containment capabilities in full. 171 of the 556 platforms it grades clear it. See the self hosted platform ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. MakinaRocks and Nexus Intelligence are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose MakinaRocks if
- Engineering drawings and estimating work, not plant floor telemetry, is the problem.
- Air gapped deployment inside a closed network is a hard requirement, which Nexus does not offer.
- You want a platform to build and operate your own models on, not only finished agents.
Choose Nexus Intelligence if
- Plant floor signals (PLC, SCADA, MES) are where your agents must live.
- End to end monitoring to action on operations is the value.
- Operational technology integration depth is decisive.
| Feature | M MakinaRocks |
N Nexus Intelligence |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
MakinaRocksIntegrations & Tool Calling Real time industrial data flows into the platform, but nothing writes into an outside system. The PLC connection is the real support, and it is a read. The other named counterparties, GPU servers, storage and network, are the platform's own substrate. The manufacturing pitch to integrate AI across design, production, quality and operations into a single framework is about consolidating the customer's AI systems, not about agents reaching outside systems. The internal integrations are real. The platform brings Gitea, MLflow, Airflow, Argo CD, OpenBao, LLM Playground, Chat and Langfuse under one identity plane, and accepts any workload via Helm chart. That is integration into the platform, not out of it. There is no authenticated action in an outside system, and no API agent that triggers external system actions, DB agent that queries databases in natural language or retrieval agent that consults manuals. Sourcemakinarocks.ai/en/product/runway/ industries section, makinarocks.ai/en/blog/what-is-ai-os/ platform apps section, PLC use-case page carried from the July passread 2026-09-14 |
||
|
Nexus IntelligenceIntegrations & Tool Calling 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 Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
MakinaRocksWorkflow Orchestration Two orchestration surfaces ship with the platform, one of them multi agent by name, and the sequence is left to the customer. Airflow for orchestration is a platform app present from installation, and the app catalog carries Langflow for building RAG pipelines and multi-agent workflows without writing orchestration code, a visual builder for multi agent work. The composition model is the product's central claim. Applications are not locked into a fixed pipeline, every component is independent, and the team decides how they connect, for example running experiments in JupyterLab, logging results to MLflow and deploying via Argo CD, or building a RAG pipeline in Langflow and serving it directly through Chat. Airflow and Langflow are open source components MakinaRocks packages, integrates under one identity plane and ships as part of the platform. MakinaRocks also describes an enterprise AI operating system that orchestrates specialized agents for anomaly detection, predictive maintenance and process control, but names no mechanism for it. There is no orchestration runtime of MakinaRocks' own and no workflow versioning, so this is shipped orchestration tooling, not a model of how agents coordinate. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ platform apps, app catalog and own-the-os sectionsread 2026-09-14 |
||
|
Nexus IntelligenceWorkflow Orchestration 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 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
MakinaRocksTriggers & Channel Coverage A scheduler and a chat interface ship with the platform, and agents are described acting on real time PLC data, but the platform has no event seam of its own. In one manufacturing use case, agents monitor production conditions continuously from real-time PLC data and act as conditions change. Airflow for orchestration is one of the eight platform apps available from installation, even in air-gapped environments, and Airflow is a scheduler, shipped and not just described. Chat is a third channel, also pre-installed, and MakinaRocks' illustration of composition ends with building a RAG pipeline in Langflow and serving it directly through Chat. A conversational surface is a channel, though a human-invoked one, so it widens coverage without evidencing autonomy. There is no webhook, event subscription, inbound queue or trigger configuration surface. What exists is a scheduler the customer wires up and a continuous data feed described in a single use case. Channel coverage is thin, with one real-time industrial feed, one scheduler and one chat interface, all within a single deployment. Sourcemakinarocks.ai/en/use-case/runway-manufacturing-ai-system-with-real-time-plc-data/ carried from the July pass, makinarocks.ai/en/blog/what-is-ai-os/ platform apps sectionread 2026-09-14 |
||
|
Nexus IntelligenceTriggers & Channel Coverage 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 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
MakinaRocksKnowledge Grounding & RAG The components to build a knowledge store ship with the platform, but none is operated over the customer's data. The app catalog offers vector databases including Milvus, Qdrant and Chroma DB and Langflow for building RAG pipelines, and the unified runtime lists vector databases among the connected components. These ship with the platform and are governed by it. The customer gets an open source database engine and pipeline builder, one tap away, inside the platform's identity plane. A vector database is the means to build a knowledge structure, not the structure itself. Here the index arrives empty. Nothing ingests the customer's manuals, drawings or maintenance histories, no source is indexed, refreshed or permissioned by the product, and there is no schema, refresh path or ownership of what is in the store. There is no citation visibility either, because MakinaRocks operates no retrieval. Shipping Milvus is shipping the empty shelf. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ app catalog and unified runtime sectionsread 2026-09-14 |
||
|
Nexus IntelligenceKnowledge Grounding & RAG 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 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
MakinaRocksMemory & State Persistence There is no agent memory of any kind. MakinaRocks describes the platform component by component, from shared GPU and storage services to the app catalog and audit logging, and no store of agent state appears in it, with no scope, lifetime or carry over between runs. Continual learning applied to its models is state accumulating in model weights, which is retraining, not something an agent reads back as context. The vector databases in the app catalog are knowledge stores over the customer's documents and data. A vector index is a retrieval structure, not a memory of what an agent did or decided, and offering three as installable options makes clear these are components the customer fills. Even conversation state is missing. The platform ships Chat as an AI interface, but there is no thread persistence, history retention or context carried between sessions, and storage as an infrastructure service is disk, not state. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ read in full, makinarocks.ai/en/product/runway/ read in fullread 2026-09-14 |
||
|
Nexus IntelligenceMemory & State Persistence 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 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
MakinaRocksHuman Oversight & Guardrails Runway controls who may run what, but no gate holds an agent's action for human approval. The platform controls who can access which apps and data from a single control plane, administrators can use built-in roles or define custom permission sets, and fine-grained permission controls extend to every AI application running on Runway. MakinaRocks compares this to phone app permissions, where settings control exactly what each app can access, such as camera, location, microphone and contacts, and the OS enforces those policies centrally. Permissions bound who may run what, not what must be approved before it commits. A role that prevents an engineer from deploying an app is an access decision taken once, at configuration time, and there is no approval queue, human in the loop step or hold for review between an agent's output and its effect. The line that the freedom to install any app does not mean anything goes is about which software may run, not which actions may proceed. No MakinaRocks page says agents suggest setpoint adjustments for human or system approval, and the defense pitch of absolute governance and security protocols is about control of AI deployment, not a person approving an agent's setpoint. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ governance section, makinarocks.ai/en/product/runway/ industries sectionread 2026-09-14 |
||
|
Nexus IntelligenceHuman Oversight & Guardrails 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 RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
MakinaRocksSecurity, Identity & Governance ISO certification badges sit alongside a deep identity and permission surface, though the certificates themselves are not available. Every page carries ISO 27001 and ISO 9001 badges, a Korean Good Software certification mark and a defense innovation program designation. The controls go deeper. Security is enforced across all layers through Keycloak-based SSO and RBAC, with the platform handling authentication, access control, resource management and security once, at the platform level. Runway 2.0 handles this through SSO, RBAC, fine-grained permission controls and audit logging, all managed from one place, and administrators can use built-in roles or define custom permission sets for their organization. This governance layer extends beyond models and datasets to every AI application running on Runway, and the platform apps include OpenBao for secrets. The gap is verification. The ISO badges are images with no certificate number, certifying body, scope statement or issue or expiry date, and there is no trust center or security page, the only legal page being a privacy policy, so a customer cannot verify the scope of what was certified. Sourcemakinarocks.ai/en/product/runway/ governance section and site footer, makinarocks.ai/en/blog/what-is-ai-os/ governance sectionread 2026-09-14 |
||
|
Nexus IntelligenceSecurity, Identity & Governance 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 Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
MakinaRocksObservability & Auditability Every platform operation lands in a centralized audit log, and an LLM tracing tool ships pre installed. Runway automatically captures every operation in centralized audit logs, which MakinaRocks says ensures 100% compliance, and its governance covers who can access which data, what actions have been taken, whether the entire operational trail is auditable and whether every action is traceable, all managed at the OS layer. Capturing every operation centrally, as a property of the platform and not a per-app afterthought, makes a record at run level. The second surface is Langfuse, one of the pre installed platform apps. Langfuse is an LLM tracing and observability tool, so the platform ships a surface on which an LLM application's individual runs can be inspected, which lifts this above a bare traceability claim. What is observed is the AI applications and agents running on Runway. The industrial monitoring the specialized agents perform on plant equipment is the product's output, not a record of the agents. There is no retention period, export path or SIEM integration, and the audit claim is stated at platform level, not shown as a log schema. Sourcemakinarocks.ai/en/product/runway/ governance section, makinarocks.ai/en/blog/what-is-ai-os/ platform apps and governance sectionsread 2026-09-14 |
||
|
Nexus IntelligenceObservability & Auditability 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 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
MakinaRocksDeployment & Data Residency Installation in air gapped and disconnected networks is a headline capability, described in working detail, alongside cloud and on premises options and edge execution on industrial computers. Runway offers instant deployment for air-gapped environments, deploying AI securely in restricted or disconnected networks, with automated import pipelines and private package mirrors for instant execution with zero external dependencies. The mechanism, automated offline packages and private mirror repositories, cuts deployment in air-gapped networks from months to two weeks by MakinaRocks' account. A vendor that has built package mirroring to make offline installation fast is operating in disconnected networks, not describing an aspiration. MakinaRocks treats it as a design requirement of the category, noting that in regulated industries like defense, manufacturing, public sector and financial services external network access is often restricted and AI applications need to run reliably there too. The capability extends to the tooling as well as the runtime. The full pre-installed suite works even in air-gapped environments, and the defense positioning is to deploy and control AI in air-gapped and high-security environments with zero external reliance. There is no region list or residency menu for a hosted option and no installation or sizing documentation, but the route into the customer's environment is described repeatedly. Sourcemakinarocks.ai/en/product/runway/ air-gapped feature, results and industries sections, makinarocks.ai/en/blog/what-is-ai-os/ air-gapped support sectionread 2026-09-14 |
||
|
Nexus IntelligenceDeployment & Data Residency 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 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
MakinaRocksPrebuilt Agents, Templates & Packs The browsable app catalog holds infrastructure, not agents. MakinaRocks describes it in app store terms, with vetted applications ready to install with a tap. Six installable entries are shown (Chroma DB, Code Server, JupyterLab, Langflow, Milvus and Qdrant) plus eight pre installed platform apps, and every one is a development environment, a database or a piece of engineering tooling. A catalog of vector databases can be browsed, but it is not a set of agents a customer adopts. The units that would qualify sit elsewhere. Four agent lines appear under Agents (Expert Augmentation, Control, Predictive Operations and Machine Vision), each with its own durable URL, alongside a separate named product agent, DrawX, which turns drawings into decisions with an AI agent. Nothing settles whether those four are adoptable units or four descriptions of one capability set, so they are named machinery and named agent types, not a catalog of adoptable units. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ app catalog and platform apps sections, makinarocks.ai primary navigation read across three pagesread 2026-09-14 |
||
|
Nexus IntelligencePrebuilt Agents, Templates & Packs 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 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
MakinaRocksModel Flexibility & Routing The customer's administrators choose and serve the models, through a model management app that comes pre installed. LLM Playground for managing large language models is one of eight platform apps present from installation, inside MakinaRocks' own identity and lifecycle plane, where everything is integrated through Keycloak-based SSO with one Runway login for everything. A model management surface handed to the customer's administrators answers who chooses, and the playground is MakinaRocks' own app, not a tool from another company. The unified runtime connects model configuration, serving infrastructure, vector databases and orchestration tooling within a single platform, and a MakinaRocks product update covers permissions, LLM serving in a closed network and experiment setup. Serving language models inside a closed network is the customer running models of their choosing on their own hardware with no provider in the path, and the pre-installed suite works even in air-gapped environments. A customer can also deploy a proprietary model serving API through the Helm path, which is permitted, not shipped. This covers the Runway platform, and the Specialized AI agent lines may run on a model MakinaRocks fixes. MakinaRocks publishes no detailed model list, routing policy or selector interface. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ platform apps and unified runtime sectionsread 2026-09-14 |
||
|
Nexus IntelligenceModel Flexibility & Routing 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 Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
MakinaRocksAPIs, SDKs & MCP Extensibility Customers can deploy their own software onto Runway, but nothing lets an outside system call the platform. The extension path is open and unbounded. Runway supports deploying any workload via Helm chart, whether an open-source tool not in the catalog, a proprietary model serving API, an internal analytics dashboard or a custom admin tool, with no vendor-curated boundary. Governance follows the extension instead of blocking it. Wherever an app comes from, the catalog, a Helm chart or joint development with MakinaRocks, the same authentication, access control and resource governance applies automatically. A named, standard packaging format with a deployment path and automatic policy inheritance is a real extensibility surface, not a marketing claim. The direction is inward, not outward. Helm charts let a customer put software onto the platform, but there is no API or SDK that lets an external system or another vendor's agent drive Runway. There is no REST API, CLI reference, MCP server, webhook or documentation host. A proprietary model serving API deployed by the customer is the customer's API running as a workload and says nothing about whether the platform itself is callable. An enterprise platform of this kind may well expose APIs under contract, but MakinaRocks asserts none. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ custom deployment and governance sections, makinarocks.ai navigation and footer read across three pagesread 2026-09-14 |
||
|
Nexus IntelligenceAPIs, SDKs & MCP Extensibility 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 Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
MakinaRocksTesting, Debugging & Optimization A pre deployment harness comes pre installed, with experiment tracking in MLflow ahead of a GitOps release. MLflow for experiment tracking is one of the platform apps present from installation, and MakinaRocks describes the working pattern as running experiments in JupyterLab, logging results to MLflow and deploying via Argo CD. Experiments logged and compared before a GitOps deployment put a change under test, and it is the sequence, not the tool, that makes it one. The release path sits alongside it, Argo CD for GitOps-based deployment with Gitea for source control, so a model or application change moves from a tracked experiment through a versioned repository into a deployment. MakinaRocks names experiment setup as a shipped capability in a product update, and the full suite works even in air-gapped environments, so the harness is not a cloud-only convenience. MLflow, Argo CD and Gitea are open source components MakinaRocks packages, governs under one identity plane and ships as the product. The object is what runs on the platform, which for a customer deploying MakinaRocks' own specialized agents includes those agents. The tagline of managing the full model lifecycle from planning and risk modeling through operations with continual learning describes lifecycle management, which is not a harness, and continual learning is absorbed into the model. There are no scored test cases, golden set, accuracy figure or published evaluation methodology of MakinaRocks' own. The harness is named, but its use is not measured. Sourcemakinarocks.ai/en/blog/what-is-ai-os/ platform apps and own-the-os sectionsread 2026-09-14 |
||
|
Nexus IntelligenceTesting, Debugging & Optimization 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 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
MakinaRocksBrowser & Computer Use The agents act on industrial systems and machine data, with no screen in the loop and no browser or computer use. The action path is data and infrastructure, such as real time PLC feeds, Helm deployed workloads and vector databases, with no rendered control to target. Machine Vision, one of the four agent lines, inspects physical parts and surfaces through cameras, which is seeing, not driving a computer interface. Breakage when UI elements change has no meaning against PLC tags, Helm charts and industrial cameras. JupyterLab and Code Server in the app catalog are development environments a person sits in front of, and Chat is an interface to the agents, not one the agents operate. MakinaRocks describes the architecture in enough detail that an undocumented screen-driving path is implausible. Sourcemakinarocks.ai/en/product/runway/ read in full, makinarocks.ai/en/blog/what-is-ai-os/ app catalog section, site navigationread 2026-09-14 |
||
|
Nexus IntelligenceBrowser & Computer Use 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 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | M MakinaRocks |
N Nexus Intelligence |
|---|---|---|
|
Entry price Lowest public entry point |
Enterprise pricing. Contact sales. | Custom pricing (book a demo) |
|
Pricing confidence How public the numbers are |
Contact only | Contact only |
|
Billing Primary billing axis |
— | — |
|
Variable cost Workload / overage exposure |
Low variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tier
|
No free tier
|
|
Buying motion Self-serve vs sales call |
— | — |
|
Pricing verified When this pricing was last checked |
More comparisons with MakinaRocks or Nexus Intelligence
Other matchups in enterprise operations agents
Not the pairing you were after? These compare a different set of enterprise operations agents on the same 14 capabilities.