SAP HANA Cloud Agent Memory Service — persistent, governed memory for business agents
As of 2026-11-14
What is SAP HANA Cloud Agent Memory Service?
SAP HANA Cloud Agent Memory Service: unconfirmed as of 11 Nov 2026 (no general availability confirmed by any SAP source); it is named in the September 2026 HANA Cloud release highlights as "SAP Agent Memory Service", and the SAP Cloud SDK for Python supports it from sap-cloud-sdk 0.36.0. SAP's reference demo scopes records by agent and invoker, enforces end-user access in CAP, shares a record between agents only on explicit user confirmation and supports revocation; GDPR retention, erasure and poisoning controls remain the application's job.
What the service is
SAP HANA Cloud Agent Memory Service: unconfirmed as of 11 Nov 2026 (no general availability confirmed by any SAP source); it is named in the September 2026 HANA Cloud release highlights as "SAP Agent Memory Service", and the SAP Cloud SDK for Python supports it from sap-cloud-sdk 0.36.0. SAP describes it as persistence and retrieval for agent memory, backed by the HANA Cloud Vector Engine: a managed API that stores memories and conversation messages and retrieves them semantically, so an agent can carry a relevant preference or decision into a later session without replaying its whole history. The motivating problem is practical. A business agent that forgets everything between conversations makes users repeat themselves; one that remembers everything indiscriminately becomes a privacy and security liability. The service is SAP's attempt to give memory a governed home beside the data it relates to. The sources reviewed do not state a general-availability status or a date for the service beyond its appearance in the September 2026 release highlights, so verify the status for your HANA Cloud edition.
SAP first signalled "agentic memory" for HANA Cloud at TechEd in November 2025, describing agents that persist context across long-running sessions and memorise past inputs and decisions. The service named in the September 2026 release highlights would be the productised form of that direction, but its availability is unconfirmed; SAP Community material showing it with Joule agents does not establish a product status.
Why it matters
- Agents that forget are annoying and agents that remember everything are a liability: the design question is who may write, read, share and delete memory, and SAP's demo answers it with scoping, explicit sharing and revocation outside the agents.
- Memory is personal data in GDPR terms and a persistent input channel in security terms, so retention, erasure, correction and poisoning defences must be designed before the first record is written.
- It sits next to, not instead of, grounding and the knowledge graph: grounding for shared company knowledge, graph for relationships, memory for what one user told one agent.
Key points
- Status unconfirmed (no SAP GA source found by 11 Nov 2026); an Agent Memory client exists in the SAP Cloud SDK for Python. The SAP HANA Cloud release highlights of 25 September 2026 describe it ('SAP Agent Memory Service') as persistent agent memory and semantic retrieval on the HANA Cloud Vector Engine; design against it only after confirming availability on the tenant.
- Managed API for memories and conversation messages, as described by SAP; general availability not confirmed by an SAP source as of 11 Nov 2026.
- Records are organised by agentID and invokerID; CAP derives the scope from the authenticated user and enforces end-user access.
- Selective sharing: a second agent gets read-only access to one explicitly shared record for the same user.
- Sharing and revocation run through a separate Joule skill with user confirmation; neither agent has a tool to grant itself access.
- Retrieval is vector-based (REAL_VECTOR, cosine similarity, L2 distance); the application still decides what to remember, correct and forget.
- GDPR: purpose limitation, minimisation, storage limitation, accuracy, erasure and privacy by default apply to memory (our reading, not SAP's or legal advice).
- Security: persistent memory is a poisoning target (OWASP agentic risk class); validate writes, keep provenance, make shared records read-only.
Terms used on this page
- Agent memory
- Persistent store of facts, preferences and decisions an agent can recall across sessions.
- invokerID
- Identifier of the user on whose behalf an agent runs; with agentID it scopes a memory record.
- Selective sharing
- Granting a second agent read-only access to one chosen memory record, after user confirmation.
- Revocation
- Removing a previously granted share without deleting the original record.
- Vector Engine
- HANA Cloud capability storing embeddings in REAL_VECTOR columns and comparing them by similarity.
- Knowledge Graph Engine
- HANA Cloud engine for RDF graphs queried with SPARQL, used for relationships rather than personal memory.
- Memory poisoning
- Writing adversarial content into persistent memory so it steers later sessions (OWASP agentic risk).
Sources
- SAP Community — Give Business Agents Memory with SAP HANA Cloud Agent Memory Service
- SAP Community — What's New in SAP HANA Cloud, September 2026
- SAP Community — What's new in SAP Cloud Application Programming Model, September 2026
- SAP News — New agentic capabilities in SAP BTP (TechEd, Nov 2025): agentic memory, HANA Cloud MCP
- SAP Community — SAP HANA Cloud Becomes Agentic: Discovery Agent & Data Agent
- SAP Learning — SAP HANA Cloud Vector Engine (REAL_VECTOR, similarity functions)
- SAP Help — SAP HANA Cloud, SAP HANA Database Knowledge Graph Guide
- MIT AI Agent Index — Joule Agents (state retention, guardrails, documentation gaps)
- SAPinsider — SAP Business AI Platform: BTP foundation (Sapphire 2026; Build, Contextualize & Reason, Govern)
- SAPinsider — SAP Sapphire 2026: knowledge graph and Business Data Cloud as data foundation
- SAP Help Portal — Joule Integration Guide (2026-09-28): conversation-log opt-in/out, unsubscribing erases tenant data
- SAP Community — SAP Joule Work mobile app version 3.2
- GDPR Article 5 — principles relating to processing of personal data
- GDPR Article 17 — right to erasure
- GDPR Article 25 — data protection by design and by default
- OWASP Agent Memory Guard (incubator project; memory poisoning defence)
- Vectorize — OWASP ASI06: Memory and Context Poisoning explained
- SAP TechEd 2026 (Berlin & virtual, 27–29 Oct 2026) — session DA205: Agentic memory: Knowledge graph engine and recall in SAP HANA Cloud
- SAP TechEd 2026 (Berlin & virtual, 27–29 Oct 2026) — session DA263: Knowledge graph and agent memory: Build an agent that remembers
- SAP TechEd 2026 (Berlin & virtual, 27–29 Oct 2026) — session DA164: Building agentic applications with SAP HANA Cloud
Full card with the Consultant plan — €19.90/month. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.
Open missions
67 live roles and contracts in SAP AI & Joule right now — see the SAP AI & Joule missions · freelance SAP contracts.