Flowise Memory
https://docs.flowiseai.com/integrations/langchain/memory
Discontinued: Flowise (acquired by Workday, Aug 2025) was sunset in 2026 — code freeze 2026-07-29, GitHub repo archived 2026-08-13, end of life 2026-08-31. Was a visual LangChain canvas with LangChain-native memory nodes (Buffer, Buffer Window, Conversation Summary Buffer) backed by an internal chat_message DB table; Buffer Window kept the last K interactions, Summary Buffer compressed older turns while keeping recent ones verbatim.
Archived · Verified 2026-10-29 · fresh as of 2026-10-29 · 52 cited facts, 9 with a third-party source · 2 recorded changes · Suggest a correction
At a glance
- Tier
- T1
- Section
- Framework-embedded memory
- Created
- 2023 (Flowise launched 2023; YC S23) third-party fix
- Latest release
- flowise@3.1.4 (2026-07-29) — final repo fix
- License
- Apache-2.0 repo fix
- GitHub
- FlowiseAI/Flowise — ~55.4k stars, archived 2026-08-13 (sunset plan had targeted 2026-08-10) repo fix
- Pricing
- discontinued — product sunset (EOL 2026-08-31); OSS code remains forkable under Apache-2.0 vendor fix
- Funding
- total $500K (Seed, YC, 2023-01); acquired by Workday (announced 2025-08-14, terms undisclosed) third-party fix
- Freshness
- 2026-10-29 fix
- Layer
- agent-infra repo fix
- Licensing
- open-source repo fix
- Developer activity
- OpenRank 2.5 (12-mo avg 27.21) · 1 participants — 2026-08 third-party fix
Memory taxonomy
- storage
- vector
- retrieval
- similarity
- persistence
- session
- update
- append-only
- unit
- episode
- governance
- inspectable
- conflict
- append-only
When to use
Optimised for: visual LangChain canvas + memory nodes
Anti-fit: not for production-grade SLA workloads
Pros & cons
Pros
Visual builder lowers the bar for non-engineers to design memory pipelines; LangChain-compatible nodes.
Cons
Memory is as good as the LangChain primitive underneath — no novel architecture; less appealing to engineers building from code.
Claims & capabilities
Open source. Acquired by Workday August 2025.
Technical surface
- API surface
- REST, SDK: JS/TS
- Backend storage
- pluggable
- Deployment
- Both (OSS self-hosted; Flowise Cloud managed; air-gapped deployment supported)
- Embedding model
- multiple supported
- Multi-tenancy
- namespace
- MCP
- via official adapter — Flowise MCP node
- A2A
- searched not found
- OpenTelemetry
- searched not found
Compare Flowise Memory with…
Alternatives to Flowise Memory → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other framework-embedded memory in the catalog, ranked by inbound references.
- Spring AI ChatMemory T3
Wraps conversation memory behind an Advisor abstraction. MessageWindowChatMemory default 20-msg sliding window (preserves system messages); pluggable ChatMemoryRepository backends (in-memory, JDBC, Cassandra, Neo4j). Memory injected as cross-cutting concern at the ChatClient level.
- LangGraph Persistence T2
Distinct from LangMem. Built-in checkpointer saves graph state per super-step (short-term, thread-scoped). Store System adds long-term hierarchical key-value memory across threads with optional vector search + TTL. Postgres / Mongo / Redis stores for production.
- AutoGen Memory T2
AutoGen's memory layer: ListMemory chronological context plus teachable agents that vectorise corrections; integrates with Mem0/Zep rather than building deep memory natively. Microsoft AutoGen is in maintenance mode (community managed, bug and security fixes only), and Microsoft points new projects to Microsoft Agent Framework.
- CrewAI Memory T2
Memory subsystem inside the CrewAI orchestration framework; integrates with Mem0 for the long-term tier.
- Hermes Agent memory (Nous Research) T3
Nous Research's open-source self-improving agent keeps an agent-curated MEMORY.md/USER.md notebook injected at session start, full-text (FTS5) search over past sessions that returns raw messages without LLM summarisation, and optional Honcho user modelling. one of the most-starred agent projects of 2026.
- Semantic Kernel Memory T2
Microsoft Semantic Kernel's memory plugin (Microsoft.SemanticKernel.Plugins.Memory): a plug-in approach to long-term memory in the SK agent framework (agent memory marked experimental). Semantic Kernel's README names Microsoft Agent Framework 1.0 as its enterprise-ready successor, with a migration guide.
Sources (51 cited facts, 9 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Buffer + Buffer-Window + Conversation-Summary nodes vendor
- What it does & what's distinct Discontinued: Flowise (acquired by Workday, Aug 2025) was sunset in 2026 — code freeze 2… vendor
- Claims / benefits Open source. Acquired by Workday August 2025. vendor
- Modalities text (LangChain pipeline-based; text inputs/outputs) vendor
- Created 2023 (Flowise launched 2023; YC S23) third-party
- Latest release flowise@3.1.4 (2026-07-29) — final repo
- License Apache-2.0 repo
- GitHub FlowiseAI/Flowise — ~55.4k stars, archived 2026-08-13 (sunset plan had targeted 2026-08-… repo
- Funding total $500K (Seed, YC, 2023-01); acquired by Workday (announced 2025-08-14, terms undisc… third-party
- Customers / scale 11-50 ppl Acquired by Workday (Aug 2025), customer names not disclosed vendor
- Pricing discontinued — product sunset (EOL 2026-08-31); OSS code remains forkable under Apache-2.0 vendor
- Compliance Enterprise-grade observability, HITL human-in-the-loop checkpoints third-party
- Data handling Self-hosted and air-gapped deployment for full data sovereignty third-party
- Deployment Both (OSS self-hosted; Flowise Cloud managed; air-gapped deployment supported) third-party
- HQ US vendor
- Founders / pedigree FlowiseAI; YC S23; founders Hen Yen (ex-ExxonMobil data scientist) and Henry Heng third-party
- Memory volume / scale no scale claim (Flowise: 38k+ GitHub stars; memory node installs not tracked separately) repo
- API surface REST, SDK: JS/TS vendor
- Backend storage pluggable vendor
- Multi-tenancy namespace vendor
- SSO / RBAC SSO + RBAC vendor
- Embedding model multiple supported vendor
- Versioning immutable append-log vendor
- Tombstoning append-only no delete vendor
- Namespace primitives per-tenant vendor
- Contradiction handling LLM resolves and overwrites vendor
- Forgetting policy consolidation/summarization vendor
- MCP support via official adapter — Flowise MCP node vendor
- Webhooks / events webhooks supported vendor
- Import / export JSON chatflow export vendor
- Integration count 0 vendor
- Orchestration single-agent vendor
- Programmatic control declarative config (visual canvas) + REST vendor
- Pricing specifics pre-Workday OSS free + Starter $35/mo + Pro $65/mo; post-Workday acquisition Aug 2025 — … third-party
- Agent abstraction DAG (visual canvas wraps LangChain) vendor
- Memory primitives multiple (Buffer/Buffer Window/Conversation Summary backed by chat_message DB) vendor
- LLM lock any (BYO via LangChain LLMs) vendor
- Runtimes Node/TypeScript repo
- Session handling persistent thread (per chatflow session) vendor
- Validated verticals OSS LangChain users, prototyping (horizontal) vendor
- Time to running <1hr (Docker, OSS) vendor
- Anti-fit not for production-grade SLA workloads vendor
- Optimised for visual LangChain canvas + memory nodes vendor
- Adjacent infrastructure requires Flowise; BYO LLM + vector store vendor
- Pros Visual builder lowers the bar for non-engineers to design memory pipelines; LangChain-co… vendor
- Cons Memory is as good as the LangChain primitive underneath — no novel architecture; less ap… vendor
- Project & sources memory docs vendor
- adoption-accelerator yc-s23 third-party
- licensing-bucket open-source repo
- taxonomy-three-layer-rollup agent-infra repo
- developer-activity-opendigger {"activity":2.02,"as_of":"2026-08","openrank_12mo":27.21,"openrank_current":2.5,"partici… third-party
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
- 2026-10-23
- Funding / ownership “$500K total Seed (YC) · 2023-01” → “total $500K (Seed, YC, 2023-01); acquired by Workday (announced 2025-08-14, terms undisclosed)” source
- Compliance “Enterprise-grade observability, HITL human-in-the-loop checkpoints; Workday (acquirer) adds enterprise compliance p…” → “Enterprise-grade observability, HITL human-in-the-loop checkpoints” source
- 2026-10-22
- Lifecycle first recorded as “archived”
- License “not applicable — not OSS” → “Apache-2.0” source
- Latest release “not applicable — not OSS” → “flowise@3.1.4 (2026-07-29) — final” source
- Pricing “Pre-acquisition: Free OSS; Starter $35/mo; Pro $65/mo; Enterprise custom. Post-Workday acquisition Aug 2025: pricin…” → “discontinued — product sunset (EOL 2026-08-31); OSS code remains forkable under Apache-2.0” source
Related systems
References (2)
- LangChain (framework) integrates with · depends on at runtime — Was a visual LangChain canvas with LangChain-native memory nodes (Buffer, Buffer Window, Conversation Summary Buffer) backed by an internal chat_message DB table
- Zep & Graphiti integrates with — Flowise LangChain Memory nodes include Zep Memory. (verified 2026-10-29)
Referenced by (7)
- Arize Phoenix integrates with — Arize Phoenix docs have a Flowise Memory integration page. (verified 2026-10-29)
- Comet ML integrates with — Comet's Opik docs have a Flowise Memory integration page. (verified 2026-10-29)
- Langfuse integrates with — Langfuse's integrations directory has a Flowise Memory integration page. (verified 2026-10-29)
- MongoDB Atlas Vector Search integrates with — MongoDB's Atlas AI Integrations page lists Flowise Memory as an integration (some entries are marked community-maintained). (verified 2026-10-29)
- Pinecone integrates with — Pinecone's integrations directory has a Flowise Memory integration page. (verified 2026-10-29)
- Pydantic Logfire integrates with — Pydantic Logfire integrations docs have a Flowise page. (verified 2026-10-29)
- TrueFoundry AI Gateway integrates with — TrueFoundry AI Gateway ecosystem lists a Flowise integration page. (verified 2026-10-29)