What DevHoard is

DevHoard is a long-term memory vault for developers — snippets, prompts, commands, notes, links, optional secrets, and (on Pro) images — reachable from the web app and from agents over MCP.

Tagline: Where devs hoard their coveted data.

In every user-facing place the product name is DevHoard (never legacy folder names).

Who it helps

People who:

Reuse the same shell one-liners and LLM prompts across projects
Want search and light organization without standing up Obsidian + sync on every machine
Need Cursor (or similar) to read and write the same hoard over MCP

What you store

Free (text + MCP)	Pro
SNIPPET, PROMPT, COMMAND, NOTE, LINK, SECRET	IMAGE uploads to private R2 (~25 GB soft quota)

Organization: collections, tags, pin, trash, JSON/MD export, in-vault [Title](#missing) links. Search uses Postgres FTS. Details: vault-items, item-types.

Drawings / generic files and Stripe purchase come later; soft-launch Pro is a manual plan flip until Phase 5.

App surfaces

Surface	Role
`/app`	Your Hoard (vault table; ⌘K search)
`/app/inbox`	Hoard MCP Inbox — Keep/Dismiss captures
`/app/dashboard`	Personal stats (not Owner metrics)
`/docs`	This wiki · Help in the app rail
`/terms` · `/privacy`	Soft-launch legal drafts

Admin vs Pro: ADMIN_EMAILS unlocks Owner metrics only. Image uploads need Neon User.plan = PRO and R2 env.

Why MCP matters

Plenty of tools are local PKM or web snippet managers. DevHoard’s wedge is a personal MCP endpoint against a hosted Neon-backed vault — same data in the browser and in the agent. Setup: mcp-cursor.

Prefer Hoard first, organize later: captures from MCP, packs, and imports land in the Hoard MCP Inbox until you Keep or Dismiss.

Plans (honest)

Plan	Intent
Free	Text memories + personal MCP + one workspace
Pro (~$12/mo when Stripe ships)	Images + storage quota + priority MCP
Team	Deferred

Next reading

vault-items — how items, encryption, and search work
item-types — the type catalog and rail filters
mcp-cursor — wire Cursor to /api/mcp