Inngest AgentKit — Network State

https://agentkit.inngest.com/concepts/memory

Memory as Network State — shared key-value store owned by the multi-agent network, readable by router / agents / tools. Persisted durably via Inngest infrastructure. Memory writes decoupled from response latency: agent responds immediately, background Inngest function handles DB write durably with retries.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 49 cited facts, 2 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Tier
T3
Created
searched not found fix
Latest release
not applicable — not OSS fix
License
Apache-2.0 repo fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-core vendor fix
Deployment locus
hybrid vendor fix
Platform vs product
platform vendor fix
SDK languages
typescript registry fix
Protocols
mcp-client vendor fix
Compliance
soc2-type1, soc2-type2 vendor fix

Memory taxonomy

storage
kv
retrieval
exact-match
persistence
session
update
overwrite
unit
kv-token
governance
inspectable
conflict
overwrite

When to use

Optimised for: durable event-driven multi-agent state

Anti-fit: not for non-Inngest stacks

Pros & cons

Pros

Durable workflow state for agents — resume cleanly after failure; production-grade orchestration backbone.

Cons

Tied to Inngest platform; memory is workflow-state-shaped, not free-form.

Claims & capabilities

Open source. TypeScript. Official Mem0 cookbook.

Technical surface

API surface
not applicable — research paper
Backend storage
not applicable — research paper
Deployment
Both (deploy AgentKit to preferred cloud provider; Inngest platform manages durable state)
Embedding model
not applicable — research paper
Multi-tenancy
not applicable — research paper
MCP
yes — MCP servers usable as agent tools (documented)
A2A
searched not found
OpenTelemetry
first-class — Inngest dashboards + OTel exports

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 (48 cited facts, 2 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-23
    • Funding / ownership “$34M total; Series B $20.5M May 2025; Series A $6.1M Jan 2024 led by a16z; investors include Notable Capital, a16z,…” → “$34M total; Series B $20.5M May 2025; Series A $6.1M Jan 2024 led by a16z; investors include Notable Capital, a16z” source
    #223
  2. 2026-10-22
    • License “not applicable — not OSS” → “Apache-2.0” source
    • MCP support first recorded as “yes — MCP servers usable as agent tools (documented)” source
    #195