01
An individual who wants structured document memory
- Recommended setup
- Nunchi Memory Local
Human Memory and Agent Memory stay separated on your own device.
Nunchi Memory / Norfolk + Nexus
Memory ownership belongs to the user.
Memory must not become a weapon for locking users into a company. Nunchi Memory helps your memory stay yours even when platforms and agents change.
Choose by situation
Choose the memory setup that fits your situation.
Free local / macOS Apple Silicon
Nunchi Memory Local
For individuals managing documents and agent memory on their own device
Norfolk, Nexus, local databases, embedding storage, and Engram integration stay on one machine. Personal local use is free and does not require a cloud account.
Cloud beta
Nunchi Memory Cloud
For small teams sharing PRDs, meetings, decisions, and agent work memory
A 2-20 person team shares the same Human Memory and Agent Memory. Open beta starts with 30 days free, capacity caps, and no automatic paid conversion.
Execution runtime
Nunchi Memory + Engram
For agents that should use personal or team memory while doing real work
Engram is the execution runtime optimized for Nexus. Locally it uses the AMCP Memory Port; across boundaries it uses Axon with the same memory contract.
Enterprise workflow
Circuit
For closing Slack-started work as PRs or recovery reports
Circuit is separate from Nunchi Memory. Conductor, customer-local workers, Engram, Axon, and Cortex create the execution boundary inside the customer environment.
What Nunchi Memory contains
Nunchi Memory bundles Norfolk and Nexus.
Human material and agent work memory are not mixed into the same RAG lane. They stay separate, then meet through Engram and AMCP at explicit runtime boundaries.
Human Memory
Norfolk
Turns human documents, notes, meetings, links, and captures into evidence atoms.
Agent Memory
Nexus
Keeps agent decisions, verification, recovery paths, and session memory reusable in future runs.
Nexus-optimized Runtime
Engram
Execution runtime that uses Nexus Agent Memory most deeply.
Scenario map
02
A developer whose coding agent should remember yesterday’s decisions
- Recommended setup
- Nunchi Memory Local + Engram
Engram recalls Nexus memory and writes verification results back.
03
A team that needs everyone to start from the same PRDs and meeting conclusions
- Recommended setup
- Nunchi Memory Cloud
Norfolk evidence memory and Nexus work memory are shared at the team level.
04
An IT team that wants incidents and repetitive development work closed from Slack
- Recommended setup
- Circuit
A separate execution workflow runs on top of Nunchi Memory.
AMCP / Axon boundary
Direct locally, through Axon across boundaries.
AMCP is the semantic contract for Nunchi Memory access. On the same device, Engram calls AMCP-shaped local adapters directly. Across process, device, team, or product boundaries, Axon carries the same contract over the wire.
AMCP semantic contract
Local in-process
Engram → AMCP Memory Port → Local Norfolk / Nexus
- Nunchi Memory Local
- Local Engram
- Personal local DB
Cross-boundary wire
Engram / external agent → Axon → Team memory / external systems
- Nunchi Memory Cloud
- Circuit
- Enterprise gateway