Rivet Memory Node (Ironclad)
https://rivet.ironcladapp.com/
Open-source visual AI programming environment. Memory is a first-class graph node: stores text block, supports stable IDs (saving same ID overwrites enabling updates), injects stored text into downstream nodes when relevant. Memory is designed and debugged visually.
Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 50 cited facts, 3 with a third-party source · 1 recorded change · Suggest a correction
At a glance
- Type
- Visual-graph first-class memory node vendor fix
- Tier
- T3
- Section
- Framework-embedded memory
- Created
- 2023 (Rivet launched 2023 by Ironclad) vendor fix
- Latest release
- not applicable — not OSS fix
- GitHub
- ironclad/rivet — ~4.7k stars, last commit n/a repo fix
- Pricing
- OSS free (MIT) repo fix
- Funding
- Ironclad (parent): backed by Accel, Sequoia, Y Combinator, BOND; $200M+ ARR; no Rivet-specific funding third-party fix
- Freshness
- 2026-10-22 fix
- Layer
- agent-infra repo fix
- Licensing
- open-source repo fix
- SDK languages
- typescript repo fix
Memory taxonomy
- storage
- kv
- retrieval
- exact-match
- persistence
- session
- update
- overwrite
- unit
- kv-token
- governance
- inspectable
- conflict
- overwrite
When to use
Optimised for: visual-graph programming + first-class memory node
Anti-fit: not for code-first agent developers
Pros & cons
Pros
Visual flow builder for memory composition; Ironclad's contract-AI origin lends domain context.
Cons
Enterprise positioning; smaller mind-share than Flowise / Langflow.
Claims & capabilities
Used by Ironclad's internal teams.
Technical surface
- API surface
- not applicable — research paper
- Backend storage
- not applicable — research paper
- Deployment
- Both (OSS desktop app or self-hosted; remote executor for cloud/production deployment)
- Embedding model
- not applicable — research paper
- Multi-tenancy
- not applicable — research paper
- MCP
- searched not found
- A2A
- not supported
- OpenTelemetry
- searched not found
Alternatives to Rivet Memory Node (Ironclad) → 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.
- Flowise Memory T1
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.
- 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.
Sources (49 cited facts, 3 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Visual-graph first-class memory node vendor
- What it does & what's distinct Open-source visual AI programming environment. Memory is a first-class graph node: store… vendor
- Claims / benefits Used by Ironclad's internal teams. vendor
- Modalities text vendor
- Created 2023 (Rivet launched 2023 by Ironclad) vendor
- License MIT repo
- GitHub ironclad/rivet — ~4.7k stars, last commit n/a repo
- Funding Ironclad (parent): backed by Accel, Sequoia, Y Combinator, BOND; $200M+ ARR; no Rivet-sp… third-party
- Customers / scale Ironclad internal teams; used by Ironclad's legal AI products vendor
- Pricing OSS free (MIT) repo
- Data handling OSS: data handling entirely under deployer control; no Rivet-specific data handling policy repo
- Deployment Both (OSS desktop app or self-hosted; remote executor for cloud/production deployment) vendor
- HQ US (San Francisco, CA — Ironclad HQ) third-party
- Founders / pedigree Ironclad Inc. (legal contract platform; Cai GoGwilt & Jason Boehmig co-founders) vendor
- Memory volume / scale no scale claim — research / open-source vendor
- Schema evolution free-form / no schema vendor
- Contradiction handling always overwrite (last-write-wins) vendor
- Forgetting policy TTL-based vendor
- A2A support not supported vendor
- Webhooks / events no vendor
- Import / export JSON / Rivet project file vendor
- Integration count 0 vendor
- Orchestration single-agent (per-graph; multi-agent via subgraph nodes) vendor
- Programmatic control full CRUD via visual graph node vendor
- Pricing specifics OSS (MIT) free; Ironclad commercial product paid separately repo
- Agent abstraction DAG (visual graph) vendor
- Memory primitives key-value (stable-ID memory node) vendor
- LLM lock any (BYO) vendor
- Runtimes Node/TypeScript repo
- Session handling sticky session (graph execution scoped) vendor
- Validated verticals legal-tech, visual-graph developers vendor
- Time to running <10min (Rivet desktop app, OSS) vendor
- Anti-fit not for code-first agent developers vendor
- Optimised for visual-graph programming + first-class memory node vendor
- Adjacent infrastructure requires Rivet; BYO LLM vendor
- Pros Visual flow builder for memory composition; Ironclad's contract-AI origin lends domain c… vendor
- Cons Enterprise positioning; smaller mind-share than Flowise / Langflow. vendor
- Project & sources rivet.ironcladapp.com vendor
- cost-input-usd-per-mtok 0 repo
- cost-output-usd-per-mtok 0 repo
- cost-tier free repo
- cost-pricing-model free-tier repo
- cost-last-verified 2026-06-29 repo
- adoption-accelerator yc-s15 third-party
- architecture-deployment-locus local vendor
- licensing-bucket open-source repo
- positioning-platform-vs-product platform vendor
- taxonomy-three-layer-rollup agent-infra repo
- sdk-languages typescript repo
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)