Simple, honest, mostly free.

Yes. Forever. Runs entirely on your machine, zero network calls, no account required. Free caps at 2 active projects at a time - enough for most developers to never pay us. That's fine.

The dashboard's headline number: "Hydrate gave you 2.3 more days of coding this week." It reads your Claude Code ledger, computes the savings Hydrate produced in tokens, and translates that into your own active coding hours at your observed tokens-per-hour cadence. If you're on Pro or Max and regularly hit the weekly cap, this is the number you feel - extra runway before the quota lands. It's Free because it's the visceral demonstration of Hydrate's value; paywalling it would defeat the point. Configure once with hydrate plan set --tier=pro, and Hydrate even observes your rate-limit events to detect your tier automatically when enough telemetry accumulates.

A project is active when Hydrate is doing live work for it: injecting facts into your next Claude Code session, capturing the session on exit, updating the dashboard. A dormant project sits read-only - facts + history preserved, but hooks no-op when you're in its directory. You can have as many dormant projects as you want at any tier.

Three ways: (1) you hit your active limit and activate a new one - Hydrate asks which existing project to dormant; (2) explicit CLI hydrate project deactivate <slug>; (3) auto-dormant after 60 days of no sessions, so slots free up without you thinking about it.

No data, no. Facts stay. Session summaries stay. Dashboard history stays - all read-only. What you lose is the live benefit: Hydrate stops injecting context into new Claude Code runs in that project, and stops capturing new sessions. Reactivate any time (subject to your active limit).

hydrate backup --project=x writes a passphrase-encrypted bundle of that project's facts + session summaries. hydrate restore pulse.hyd ingests it on another machine, with four merge strategies for how conflicts resolve. Pro unlocks both commands. See the docs →

Dehydrate is a hygiene feature, included on every tier including Free. It ingests your CLAUDE.md and docs/ into Hydrate's structured fact store and shrinks the source markdown. The point is to keep CLAUDE.md maintainable without losing any working knowledge - Claude Code still sees the full context via the memory-injection hook. It is not a cost-amplifier on top of Hydrate: the civichub benchmark showed a properly dehydrated project hits the same -22% vs-vanilla saving as the un-dehydrated equivalent. Same saving, 82% less markdown. See the docs →

Yes, from the Stripe Customer Portal. You keep access through the end of the paid period, then your licence automatically falls back to Free. Your local data stays on your machine regardless.

Licence keys have a 30-day offline grace period. Planes, trains, air-gapped corp networks - you're fine. On reconnect, the licence auto-refreshes.

Team covers up to ~50 seats, no SSO, hosted by us. If you need SSO, self-hosting, org-wide policy facts, audit logs, or a SOC 2 report - that's Enterprise.