@totalreclaw/totalreclaw 1.0.4 → 1.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -12
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -81,18 +81,36 @@ Your recovery phrase is a 12-word BIP-39 mnemonic -- like a crypto wallet seed.
|
|
|
81
81
|
| `TOTALRECLAW_SUBGRAPH_MODE` | `true` | Enable on-chain storage |
|
|
82
82
|
| `TOTALRECLAW_EXTRACT_EVERY_TURNS` | `5` | Turns between automatic extractions |
|
|
83
83
|
|
|
84
|
-
##
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
|
89
|
-
|
|
90
|
-
|
|
|
91
|
-
|
|
|
92
|
-
|
|
|
93
|
-
|
|
|
94
|
-
|
|
95
|
-
|
|
84
|
+
## How TotalReclaw compares
|
|
85
|
+
|
|
86
|
+
Every AI memory tool stores your data on a server that can read it. TotalReclaw is the only one that encrypts on your device first -- a compromised server reveals nothing.
|
|
87
|
+
|
|
88
|
+
| | TotalReclaw | Mem0 | Zep | Letta | MCP Memory | memU |
|
|
89
|
+
|---|---|---|---|---|---|---|
|
|
90
|
+
| **Server sees plaintext** | Never | Yes | Yes | Yes | N/A (local) | Yes |
|
|
91
|
+
| **Client-side E2EE** | AES-256-GCM | No | No | No | No | No |
|
|
92
|
+
| **Cross-device sync** | Seed phrase | Account | Account | Account | No | Account |
|
|
93
|
+
| **Data export** | One-click plaintext | JSON (7-day link) | No | Via API | Copy file | No |
|
|
94
|
+
| **On-chain storage** | Gnosis Chain | No | No | No | No | No |
|
|
95
|
+
| **Self-hostable** | Yes | Yes | No | Yes | Yes (local) | Yes |
|
|
96
|
+
| **OpenClaw plugin** | Yes | Yes | No | No | No | Yes |
|
|
97
|
+
| **MCP server** | Yes | Yes | No | No | Yes | No |
|
|
98
|
+
| **Knowledge graph** | No | Yes ($249/mo) | Yes | Yes | Simple | No |
|
|
99
|
+
| **Free tier** | 100 writes/mo | 10K memories | 1K credits | 3 agents | Unlimited | Varies |
|
|
100
|
+
|
|
101
|
+
### Where TotalReclaw wins
|
|
102
|
+
|
|
103
|
+
- **Zero-knowledge encryption** -- No other memory tool encrypts client-side. Mem0 and Zep offer SOC 2 and HIPAA, but their servers still process your plaintext. TotalReclaw's server only ever sees encrypted blobs.
|
|
104
|
+
- **Seed-phrase portability** -- One 12-word phrase, any device, any agent. No accounts, no passwords, no vendor. Works like a crypto wallet.
|
|
105
|
+
- **On-chain anchoring** -- Memories are stored on Gnosis Chain and indexed by The Graph. No single server controls your data.
|
|
106
|
+
- **True data ownership** -- One-click plaintext export. No 7-day expiry links, no API-only access. Your data, your format.
|
|
107
|
+
|
|
108
|
+
### Where others win
|
|
109
|
+
|
|
110
|
+
- **Knowledge graphs** -- Zep's temporal graph tracks how facts evolve over time. Mem0's graph memory ($249/mo) maps entity relationships. TotalReclaw can't build graphs because the server can't read the data -- that's the privacy trade-off.
|
|
111
|
+
- **Ecosystem maturity** -- Mem0 has 49K GitHub stars, $24M in funding, and integrations with every major framework. TotalReclaw is a beta product.
|
|
112
|
+
- **Offline simplicity** -- The official MCP Memory Server and Engram need zero network, zero accounts, zero setup. Good enough for single-device use.
|
|
113
|
+
- **Enterprise compliance** -- Mem0 and Zep offer SOC 2, HIPAA, RBAC, SSO. TotalReclaw doesn't need most of these (zero-knowledge means there's nothing to comply about), but enterprises want the paperwork.
|
|
96
114
|
|
|
97
115
|
## Links
|
|
98
116
|
|