Neo4j Context Engine gives agents shared business context

On October 20, 2026, Neo4j announced Context Engine, a product intended to give enterprise agents a shared model of business concepts, relationships and processes. It is available in private preview, according to both the announcement and the product page checked on October 29. Neo4j describes a six-layer business ontology, graph-based retrieval, access through APIs and the Model Context Protocol (MCP), and memory tied to operational decisions. These are vendor-described capabilities, not independently established production outcomes.

The announcement makes a specific architectural problem visible. Agents are being added to sales, service and internal workflows faster than organizations are agreeing on what their records mean.

Why the same customer can have several meanings

Imagine a hypothetical professional-services firm. The sales agent treats an account as active once an opportunity reaches a certain stage. The billing system recognizes a customer only after an invoice is issued. A service agent relies on a signed contract. Each definition is useful in its own context. Trouble starts when an agent uses one definition to make a decision governed by another.

Adding more documents to each agent's retrieval index does not settle the disagreement. The relevant documents might contain three valid definitions, written for different departments. A language model can retrieve all three and still lack authority to decide which applies to a refund, an offer or a contractual exception.

The first engineering task is therefore to distinguish a business term from the conditions under which it can be used. “Customer” needs an owner, scope and effective definition. “Eligible for renewal discount” needs the relevant contract, date and approval rule. A current invoice balance belongs in the billing system, even if the meaning of “overdue” is documented elsewhere.

What Neo4j is proposing

In its October 19 technical article, Neo4j described six interconnected layers: business processes and organization; domain concepts; data products; physical systems; tools and integrations; and runtime knowledge. An ontology is a structured description of concepts and how they relate. A graph represents those relationships explicitly, rather than leaving the model to infer them from unrelated passages.

For example, an account may be linked to a legal entity, an active agreement, an assigned manager and a specific pricing policy. A useful context model can show which relationship authorizes a decision, which source supplies the current value and which conditions require a person to intervene. The transactional systems still have to remain authoritative for balances, stock or contract status.

Neo4j says its Context Build and Runtime component can draw context from existing data platforms, while GraphRAG retrievers make related knowledge available to agents. GraphRAG is retrieval augmented by graph structure: it uses relationships between entities or concepts to find relevant evidence. The term does not imply that every question needs a graph database. Microsoft's April 24, 2024 research examined a graph-based approach to broad questions across large text collections; those findings should not be read as a benchmark of Neo4j's newly announced product.

Context Studio is described as a place to manage the ontology and configure agents and MCP connections. MCP is an open protocol for connecting AI applications with tools and data sources; it does not decide which employee may approve a refund or which account records a model is allowed to read. Those controls remain an application and identity-management responsibility. Neo4j's product page also describes human validation of proposed ontology mappings. That safeguard matters more than an automatically generated diagram.

A shared context layer must not become a second source of truth

A context service can explain that a signed agreement determines eligibility for a special price. It should not quietly maintain a separate copy of the price that overrides the billing or contract system. If the agreement changes, the agent needs the current state and an auditable reference to its source.

That separation is easy to describe and harder to operate. Teams need versioned definitions, ownership, effective dates, permission checks and tests against representative exceptions. If an agent cannot retrieve an authorized fact, it should acknowledge the limitation or escalate rather than borrow information from a different role.

The NIST AI Risk Management Framework, published in January 2023, organizes governance, mapping, measurement and management as ongoing responsibilities. It is not a certification of Neo4j or any particular architecture. It does offer a useful counterweight to the idea that a knowledge graph alone can govern autonomous behavior.

Three ways to handle business context

A document library is enough when agents answer bounded questions from stable policies and there is a clear editorial owner. Retrieval can cite the policy and expose its revision date. This is often the right starting point for a small internal assistant.

Agent-specific RAG becomes attractive when teams have distinct domains and modest overlap. Each agent can search its own approved material. The cost appears when the same customer definition or exception must be updated in several indexes and prompts. Divergence is then a maintenance risk, not a model defect.

A shared context layer deserves consideration when multiple agents must interpret the same entities across departments, act on related systems and explain decisions. It adds modeling and governance work. A graph may make relationships easier to represent, but a well-maintained relational model, policy service and conventional APIs can be sufficient for less connected workflows.

The choice should follow a real failure mode. A firm with one agent that answers opening hours does not need six layers of ontology. A business running several agents across contracts, billing and service may need common definitions even if it never adopts Neo4j.

Test the rule before scaling the agents

Start with one disputed decision. Record the two answers, the sources each agent used and the business rule that should decide the case. Name the owner of that rule. Identify the system that holds the live value and the action that requires approval. Then test what happens when the contract changes, a user loses access or a request arrives with incomplete information.

Only after those cases behave consistently should the organization decide whether to introduce a shared context platform. Our approach to software built around operational rules starts with those handoffs and exceptions, not with a predetermined database. The related analysis on owning software decisions explains why control over data definitions and change rights matters after the first deployment.

Neo4j Context Engine is a notable private-preview proposal because it treats business meaning as something to govern across agents. Whether a graph platform earns a place in the architecture depends on how often conflicting interpretations occur, how consequential they are and whether the organization is prepared to maintain a common definition.

Questions enterprise teams are already asking

What is a business ontology for AI agents? A business ontology defines concepts, relationships and rules that agents need to interpret work consistently. It can express, for example, how an account relates to a contract, which policy applies and which system holds the current state. Neo4j's October 2026 Context Engine announcement describes a six-layer implementation; that structure is a vendor product design, not an industry requirement.

How is GraphRAG different from ordinary RAG? Ordinary retrieval-augmented generation typically searches passages or indexed documents. GraphRAG also uses modeled relationships between entities or concepts to retrieve relevant evidence. Its value depends on the question, the quality of the graph and the cost of maintaining it. A 2024 Microsoft Research paper examined one approach to broad questions over document collections; it does not establish that graphs outperform every simpler retrieval design.

Is Neo4j Context Engine generally available? No. The official Neo4j announcement dated October 20, 2026 and its product page checked October 29 describe private preview access. Product capabilities, pricing and availability should be verified again before any procurement decision.

Does sharing context give every agent permission to access the same data? No. Common definitions do not grant universal access. Identity, authorization, purpose and action approval must still be enforced by the underlying systems and integration layer. A shared context model should expose only the information each agent and user are permitted to use.