This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Titen
Open-source agent memory with receipts. No API key, no LLM.
Ask your agent "why do you remember that?" Titen answers with receipts: every memory keeps its source, who may read it, and the evidence that contradicts it. • No API key, no LLM, no embedding provider, 0 deps • Drop-in for the MCP reference memory server: same 9 tools, auto-import • titen audit finds duplicates, recall loops, leaked secrets and stale memory in any store • Bun + SQLite or Cloudflare Workers + D1, Apache-2.0
Hey Product Hunt 👋 I'm Rama, maker of Titen.
Try this: ask your AI agent "why do you remember that?"
Most memory layers can't answer. They hand back a nearby paragraph and a similarity score. That's vibes, not memory. And once a team of agents shares that store, nobody can tell what's current, who was allowed to see it, or which agent quietly overwrote whom.
Titen is built on one rule: every memory keeps its receipts.
→ Where it came from: raw observations with a content hash and a timestamp
→ Who may read it: org / project / subject scoping runs BEFORE retrieval, not after
→ What contradicts it: disputes stay disputed, both sides kept, never averaged
Three things that make it different:
1. It needs nothing. No API key, no LLM, no embedding provider, zero runtime dependencies. One command (needs Bun 1.2+) and your agent has memory over MCP:
npx titen-memory mcp
2. It's a drop-in for @modelcontextprotocol/server-memory. Same 9 tool names, your existing graph is imported on first run. Underneath, search becomes real ranked FTS5 instead of String.includes.
3. The benchmark publishes our losses. On LongMemEval-S (pooled, n=500) the zero-provider lane scored 0.246 recall@1 vs 0.182 for Mem0 OSS (infer=False). Two of our own pre-registered falsifiers also fired against us. They're printed on the chart, not hidden: titen.dev/benchmark
🧾 Launch-day challenge: the Memory Audit
Point it at any agent memory store (Titen, the MCP reference server's memory.json, or a Mem0 export):
npx titen-memory audit ./memory.json
Read-only, offline, nothing uploaded. It counts exact duplicates, near duplicates, recall loops, leaked secret patterns and stale entries, with per-item evidence you can check by hand.
We ran it on Titen's own store first: 17.9% duplicates, 96.7% stale. Published in the repo. Your turn. Drop your numbers below 👇
Honest notes: Titen is pre-1.0 (pin an exact version). By default you author the claims; model-assisted extraction ships but stays gated until a model passes 90% on our eval. And on huge unscoped stores, compile latency still crosses our own 250 ms line.
Why "Titen"? It comes from the Javanese "niteni": to notice, and to keep what you noticed. The logo is kawung, a four-petal batik motif. Its four petals stand for tenant, subject, agent and run.
I'd love to hear: what's the one thing you wish your agent could explain about its own memory?
GitHub: github.com/RamaAditya49/titen
About Titen on Product Hunt
“Open-source agent memory with receipts. No API key, no LLM.”
Titen was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #417 on the daily leaderboard. Ask your agent "why do you remember that?" Titen answers with receipts: every memory keeps its source, who may read it, and the evidence that contradicts it. • No API key, no LLM, no embedding provider, 0 deps • Drop-in for the MCP reference memory server: same 9 tools, auto-import • titen audit finds duplicates, recall loops, leaked secrets and stale memory in any store • Bun + SQLite or Cloudflare Workers + D1, Apache-2.0
On the analytics side, Titen competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Titen performed against the three products that launched closest to it on the same day.
Who hunted Titen?
Titen was hunted by Rama Aditya. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Titen including community comment highlights and product details, visit the product overview.
Rama Aditya