One architectural call. Every teammate's session honours it.
You spent half of Monday's standup explaining why we don't use ORMs. By Wednesday a PR shows up using GORM. The juniors aren't ignoring you - their Claude Code sessions never saw the decision. Hydrate fixes the channel, not the people.
What changes
- Architecture propagation.
hydrate sync --from-team=<id>pulls the canon a senior dev pinned on Opus and writes it into every teammate'sCLAUDE.md. Their next Claude Code session reads it as project instructions. - Junior models inherit senior model behaviour. Our published benchmark shows a 40% → 80% canon-resistance flip when rules live in the authoritative channel - which means Haiku on a juniors' machine refuses the same temptations Opus would, at ~10% of the Opus cost.
- Per-project memory shared across seats. Decisions and naming conventions captured in any teammate's session are available to the rest of the team. The person who sets the architecture primes everyone else's Claude Code.
- Aggregate usage dashboard. See cost / token / cache-hit ratios per project across the team. Find which teammate's workflow is the leak.
The economics
The Hybrid cell from our public benchmark (/benchmarks) is the team-lead pitch in one row: Sonnet seeds the architecture in session 1; Haiku+Hydrate handles the next six sessions. 7-of-7 sessions ship; total cost $1.41; $0.20 per shipped session - 45% of pure Sonnet cost, 12% of pure Opus.
That's not a synthetic estimate; the harness is in the press kit and you can re-run it against your own Anthropic key or subscription.
Tier & pricing
Team-tier features (shared memory across seats, team canon sync, aggregate dashboard, priority support) ship post-beta at $29 per user per month. Today, install Free or Pro on each teammate's machine - both lock the personal $5/mo rate forever. When Team ships, you get the same feature surface plus the team glue.
Install (about 30 seconds per developer)
curl -fsSL gethydrate.dev/install | sh Apple Silicon and Intel both supported - the installer picks the right binary.
curl -fsSL gethydrate.dev/install | sh amd64 and arm64 both supported - the installer picks the right binary.
Native Windows binaries ship post-beta. For now, install via WSL2 - the installer detects Linux inside WSL and works exactly as on a regular Linux box.
# Inside WSL2 (Ubuntu, Debian, etc.):
curl -fsSL gethydrate.dev/install | sh
No WSL?
Install WSL2 in 60 seconds →
Or grab the Linux tarball manually:
latest release →