Your agents start cold. Memory Core™ ends that. Persistent, graph-structured memory that compounds across sessions, across agents, across teams — hosted on Azure, MACC-eligible, zero infrastructure overhead.
Enterprise teams building on Azure AI Foundry, Microsoft 365 Copilot Studio, or any LLM framework hit the same structural wall.
Memory Core operates below the agent layer — a persistent, graph-native knowledge substrate that any agent, any framework, any session can write to and read from.
Memory Core is purpose-built for Azure-first AI deployments — from developer evaluation through enterprise production.
The IP is filed. The infrastructure is live on Azure. The substrate is in production today. We're working with a small group of platform partners and enterprise design partners ahead of public Marketplace transact — and we'd like the conversation with the right teams.
Pricing is being shaped against design-partner usage. Public Marketplace pricing will publish when we are confident the structure reflects the value delivered. Until then, every conversation is bespoke.
Azure AI Foundry Agent Service includes vector-based session memory during preview. Memory Core is a different class of product.
| Capability | Foundry Agent Service Memory | Memory Core |
|---|---|---|
| Memory type | Vector-only | Graph-native + vector |
| Cross-session persistence | Session-scoped | Persistent substrate |
| Multi-agent shared memory | Pipeline-scoped only | Cross-agent, substrate-level |
| Works outside Foundry | Foundry-locked | Any LLM framework |
| Multi-team isolation | — | Per-tenant, data-plane enforced |
| Compounds over time | — | Memory that compounds with use |
| Relationship traversal | Semantic similarity only | Graph-native — cause, sequence, identity |
| Commercial status | Free during preview · in-product memory | Private preview · partner conversations open · Marketplace transact pending |
Memory Core is designed for production AI deployments in regulated and security-sensitive environments. The top-of-page strip carries the scan-signals; this section expands the specifics.