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
- Type
- Durable-network-state / event-driven vendor fix
- Tier
- T3
- Section
- Framework-embedded memory
- Created
- searched not found fix
- Latest release
- not applicable — not OSS fix
- License
- Apache-2.0 repo fix
- GitHub
- inngest/agent-kit — ~926 stars, last commit n/a repo fix
- Pricing
- Free tier; Pro; Enterprise custom; exact pricing not published — contact for enterprise vendor fix
- Funding
- $34M total; Series B $20.5M May 2025; Series A $6.1M Jan 2024 led by a16z; investors include Notable Capital, a16z vendor fix
- Freshness
- 2026-10-22 fix
- Layer
- agent-infra repo fix
- SDK languages
- typescript registry fix
- Protocols
- mcp-client vendor fix
- Compliance
- soc2-type1, soc2-type2 vendor fix
- Developer activity
- OpenRank 0.43 (12-mo avg 2.17) · 7 participants — 2026-09 third-party 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
Alternatives to Inngest AgentKit — Network State → 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 (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 it is Durable-network-state / event-driven vendor
- What it does & what's distinct Memory as Network State — shared key-value store owned by the multi-agent network, reada… vendor
- Claims / benefits Open source. TypeScript. Official Mem0 cookbook. vendor
- Modalities text vendor
- License Apache-2.0 repo
- GitHub inngest/agent-kit — ~926 stars, last commit n/a repo
- Funding $34M total; Series B $20.5M May 2025; Series A $6.1M Jan 2024 led by a16z; investors inc… vendor
- Pricing Free tier; Pro; Enterprise custom; exact pricing not published — contact for enterprise vendor
- Compliance SOC 2 Type II; end-to-end encryption; SSO/SAML for enterprise vendor
- Data handling End-to-end encryption for all data in transit; durable infrastructure with retries; ente… vendor
- Deployment Both (deploy AgentKit to preferred cloud provider; Inngest platform manages durable state) vendor
- HQ US (San Francisco, CA — 600 California St) third-party
- Founders / pedigree Inngest Inc. (Tony Holdstock-Brown & Dan Farrelly, co-founders; ex-engineering leads) vendor
- Memory volume / scale no scale claim — bounded by Inngest durable infra vendor
- Schema evolution free-form / no schema vendor
- Contradiction handling always overwrite (last-write-wins) vendor
- Forgetting policy TTL-based vendor
- MCP support yes — MCP servers usable as agent tools (documented) vendor
- OTel first-class — Inngest dashboards + OTel exports vendor
- Webhooks / events event stream / pub-sub (Inngest events are first-class) vendor
- Import / export JSON via Inngest API vendor
- Integration count 0 vendor
- Orchestration multi-agent supervisor vendor
- Programmatic control full CRUD via TS SDK + Inngest functions vendor
- Pricing specifics tier flat-rate: Free; Pro; Enterprise custom (price not published) vendor
- Agent abstraction multi-agent supervisor + state-machine (Network) vendor
- Memory primitives key-value (Network State shared) vendor
- LLM lock any (BYO) vendor
- Runtimes Node/TypeScript vendor
- Session handling checkpoint-resumable (durable Inngest function) vendor
- Validated verticals event-driven multi-agent network developers vendor
- Time to running <1hr (Inngest account + AgentKit) vendor
- Anti-fit not for non-Inngest stacks vendor
- Optimised for durable event-driven multi-agent state vendor
- Adjacent infrastructure requires Inngest; BYO LLM vendor
- Pros Durable workflow state for agents — resume cleanly after failure; production-grade orche… vendor
- Cons Tied to Inngest platform; memory is workflow-state-shaped, not free-form. vendor
- Project & sources AgentKit memory docs vendor
- cost-pricing-model subscription vendor
- cost-last-verified 2026-06-29 vendor
- architecture-deployment-locus hybrid vendor
- licensing-bucket open-core vendor
- positioning-platform-vs-product platform vendor
- taxonomy-three-layer-rollup agent-infra repo
- developer-activity-opendigger {"activity":17.29,"as_of":"2026-09","openrank_12mo":2.17,"openrank_current":0.43,"partic… third-party
- compliance-certifications soc2-type1,soc2-type2 vendor
- sdk-languages typescript registry
- protocol-support mcp-client vendor
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 “$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
- 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