AIToday

OctaMem launches a memory layer for AI agents that stores and retrieves context without requiring a vector database, addressing the cost of repeatedly re-reading the same information and organizational knowledge loss.

Hacker News3h ago3 min read
OctaMem launches a memory layer for AI agents that stores and retrieves context without requiring a vector database, addressing the cost of repeatedly re-reading the same information and organizational knowledge loss.

Summaries like this, in your inbox every morning.

Sign up free →

3 Key Points

  • What happened

    OctaMem introduced a memory infrastructure that organizes agent data into three types—semantic (facts and knowledge), episodic (events and history), and procedural (workflows and rules)—and retrieves only relevant context per request. The system ingests documents (contracts, PDFs, spreadsheets, emails) and parses them into structured, queryable records rather than embedding blobs. It integrates via REST, Python, JavaScript, SDKs, IDE plugins, and MCP (a protocol for tool-calling) and is available on a free tier with 2 GB memory, no credit card required.

  • Why it matters

    AI agents today re-send the same context on every call, burning tokens and costs unnecessarily; without a centralized memory, institutional knowledge walks out the door when employees leave. A shared memory layer that compounds across sessions and teams allows organizations to own knowledge as infrastructure, not lose it to scattered notes or individual departures. The system includes an immutable audit chain (reads, writes, redactions logged with hash chains) so compliance and security teams can inspect and control memory end-to-end.

  • What to watch

    OctaMem offers configurable retention windows, per-record deletion, role-based access control (Okta, Entra, Google SSO), AES-256-GCM encryption at rest, TLS 1.3 in transit, and multi-AZ deployment with 30-minute RTO and 5-minute RPO. A desktop app for macOS (Apple Silicon and Intel) is available now; Windows and Linux versions are coming. Every memory record carries an immutable ID, type, score, source, and timestamp, enabling full auditability and deletion by record or context.

Discussion

No comments yet. Be the first to share your thoughts!

Log in to join the discussion

Related Articles

Stay ahead with AI news

Get curated AI news from 200+ sources delivered daily to your inbox. Free to use.

Get Started Free

Free · takes 30 seconds · unsubscribe anytime

5 minutes a day. The AI essentials.

200+ sources · Email / LINE / Slack

Get it free →