# Hydrate

> Local-first persistent memory for Claude Code. Claude Code forgets between sessions — Hydrate remembers what you built and decided, and injects that context into the next session. Free forever for solo devs; Pro/Team share architectural canon across projects and teammates.

## Product

- [Hydrate - episodic memory for Claude Code](/index.md): Claude Code starts each session with a blank mind. Hydrate captures what was built, decided, and named - then quietly injects it into the next session. No prompt engineering. No screenshots of previous chats. Just context that works.
- [Pricing](/pricing.md): Free forever for up to 2 active. $9/mo for unlimited projects, per-project backup / restore, and more. $29/user/mo for teams. Enterprise self-host available.
- [Benchmarks](/benchmarks.md): Three Claude models, seven sessions, two configs, real API spend. Every number is reproducible and clickable.
- [Hydrate vs the alternatives](/compare.md): Honest comparison of Hydrate against Pieces, Supermemory, Mem0, Zep, Letta, Windsurf, Cody, and Claude's native project memory. Where we win, where we don't.
- [Enterprise](/enterprise.md): Hydrate for teams of 10-10,000. Self-host, SSO, org-scoped policy, SOC 2, air-gap support.

## Docs

- [Overview](/docs.md): Hydrate is an episodic-memory layer for Claude Code. It installs two hooks, watches each session, extracts facts and session summaries, and injects relevant ones into the next session's context. Nothing you have to think about after the install.
- [Quickstart](/docs/quickstart.md): Claude builds the page. The Stop hook captures the session on exit.
- [Install](/docs/install.md): The installer detects your architecture, downloads the binary to /usr/local/bin/hydrate, and runs hydrate init to wire the Claude Code hooks.
- [CLI reference](/docs/cli.md): hydrate is the front door. Everything the daemon, dashboard, and hooks do is also reachable from the command line. Commands are grouped by surface area.
- [Hooks](/docs/hooks.md): Hydrate plugs into Claude Code via two first-party hooks. They're wired in during hydrate init and are invisible during normal use - you run claude exactly as you always have.
- [Scopes](/docs/scopes.md): Hydrate stores facts at three scope levels. Retrieval is the union across them, so a query in a specific project gets org-wide policy + your personal preferences + project-specific facts, all at once.
- [Dashboard](/docs/dashboard.md): The Hydrate dashboard runs on http://localhost:8089/dashboard and shows what's happening across every project Hydrate is watching. No account, no cloud, no telemetry - it's reading the same SQLite file the daemon writes to.
- [Dehydrate](/docs/dehydrate.md): Dehydrate is a hygiene feature of Hydrate. It shrinks a bloated CLAUDE.md into structured Hydrate memory without losing Claude Code performance. The markdown in your repo stays maintainable; Claude Code still gets the full context via memory injection.
- [Backup / restore](/docs/backup.md): Hydrate's backup / restore workflow moves a project's memory between machines without uploading anything. You get one encrypted file, a passphrase, and symmetric CLI commands.
- [Writing a multi-doc series](/docs/writing-a-series.md): A practical pattern for using Hydrate to keep a long series of documents consistent across sessions - the Canon Session approach.
- [Integrations](/docs/integrations.md): Hydrate ships in two integration shapes. Native hooks on Claude Code, MCP everywhere else.
- [Gemini CLI](/docs/integrations/gemini-cli.md): Hydrate memory in Gemini CLI via MCP. One command to register, one prompt to verify.
- [Enterprise](/docs/enterprise.md): Enterprise Hydrate is the same binary you'd install from Homebrew, plus a self-hosted backend. The client runs in thin-client mode (HYDRATE_BACKEND=siteengine) and talks HTTPS to your deployed stack.

## Writing

- [Guide - How to get the most out of Hydrate](/guide.md): Five patterns that make Hydrate pay off immediately. Hybrid mode, scope discipline, fact review, dashboard-as-thermometer, backup before handoffs.
- [Blog](/blog.md): Notes on Hydrate, episodic memory for Claude Code: how to use it, when to dehydrate a bloated CLAUDE.md, and the honest benchmark numbers behind both.
- [How to use Hydrate - Blog](/blog/how-to-use-hydrate.md): The practical guide to Hydrate: what installing it actually does, the five patterns that make it pay off, and the one case where you should turn it off.
- [How and when to dehydrate - Blog](/blog/how-and-when-to-dehydrate.md): Dehydrate is a hygiene tool for CLAUDE.md, not a cost amplifier. When to reach for it, when to leave it alone, the three modes, and the honest benchmark number from civichub.
- [Hydrate is not just a Claude Code hook - Blog](/blog/hydrate-is-not-just-a-hook.md): Claude Code's hook API is Hydrate's fastest-to-ship integration, but it's only half the product. The other half rides on MCP and works with every agent that speaks the protocol.
- [Hydrate memory is now on Gemini CLI - Blog](/blog/hydrate-on-gemini-cli.md): We shipped hydrate-mcp today. One Go binary, MCP over stdio, every MCP-capable agent gets Hydrate memory. Proven end-to-end on Gemini CLI.

## Other

- [Hydrate beta — what this means for you](/beta.md): Hydrate is in beta. Pro features are unlocked for everyone. Anyone who registers during beta — Free or Pro — locks in $5/mo Pro forever, decided whenever you like.
- [Tokenmaxxing isn't productivity - and we have the receipts](/blog/tokenmaxxing-and-the-empirical-answer.md): TechCrunch reported developers with the largest token budgets ship 2x at 10x cost; AI users see 9.4x more code churn. We measured the same gap and shipped a fix. Here's the data, with the methodology open for inspection.
- [Hydrate for engineering managers](/for/manager.md): Your Anthropic spend climbs faster than your shipping rate. Tokenmaxxing isn't productivity; cost-per-shipped-session is. Hydrate's Hybrid cell ships 7-of-7 at 12% of raw-Opus cost. Self-host or SaaS, $29/seat or Enterprise.
- [Hydrate for solo developers](/for/solo.md): If you ship alone with Claude Code, Hydrate buys you back the days you currently spend re-explaining your project to a forgetful model. Free for up to 2 active projects forever; $5/mo Pro locked-in if you register during beta.
- [Hydrate for team leads](/for/team-lead.md): Stop your juniors from re-deriving the architecture you settled last sprint. Hydrate's team canon sync propagates a senior dev's pinned rules to every teammate's CLAUDE.md, so juniors on Haiku inherit Opus-tier discipline at ~10% of the cost.
- [Try Hydrate, write about it, run the tests - press kit](/press.md): Everything a writer, YouTuber, or developer needs to try Hydrate, explain it accurately, and reproduce the benchmarks. Walk-through scenarios, manual recipes, and an opt-in to the closed-source benchmark harness for serious reviewers.
- [Privacy & AI transparency](/privacy.md): Hydrate's privacy notice + EU AI Act transparency statement. Who processes what, why, for how long, and the exact AI systems involved.
- [Terms of Use](/terms.md): Terms of use for Hydrate by Sedasoft Ltd. Free tier, Pro / Team subscriptions, Enterprise licencing, liability, and governing law.
- [Check your Pro rate](/upgrade.md): Enter your email to see what Pro will cost you. Anyone who registered during beta locks $5/mo forever.