Team tier

eidetic Pro for teams. Same daemon, multi-seat license. Targets dev teams who want shared engram visibility across 3-5 engineers.

→ Contact for Team ($99/mo)

What Team includes

5 Pro seats

Each seat gets its own sync.json, its own R2 namespace, its own device-id pool. Engrams stay private per seat — no cross-engineer leakage by default.

Shared-context opt-in

The Team tier ships the X-Team-ID header foundation (v0.0.39+): when configured, the daemon sends the header on every /sync upload, dual-writing engrams under engrams/team/<team_id>/<device_id>/ for cross-seat recall. Designate any of the 5 seats as a "team" surface; their engrams sync to a shared bucket so anyone on the team can query "did anyone solve this already?" via nucleus_ask.

Onboarding within 24h

Pay → reply with the 5 seat emails + a team identifier → you get 5 sync.json files within 24 hours of payment.

Email support

hi@eidetic.works. Response within 12 hours on weekdays for Team subscribers (vs 24h for Pro).

Early-access features

Team subscribers get new features 1 week before Pro. AI-powered recall, web dashboard, retention policy templates land on Team first.

Pricing

$99/month flat. No per-seat scaling — your 6th hire pays nothing extra, but tier ceiling is 10 seats per Team subscription. Larger teams: contact for Org tier.

First 10 Team subscribers keep this price forever.

Setup

1. Pay via Gumroad → confirmation email.
2. Reply with 5 seat emails + a team identifier (e.g. team-acme).
3. We run gen_pro_key.sh 5 times — one per seat — using device_id format <team>-seat-N (e.g. acme-seat-1).
4. Each seat gets their individual sync.json by email.
5. Drop the file at ~/.eidetic/sync.json per seat. v0.0.35+ hot-reload picks it up automatically.

Configuration

The Team-specific addition to sync.json is the team_id field:

{
  "worker_url": "https://eidetic-sync.morning-lake-f944.workers.dev",
  "api_key":    "",
  "device_id":  "acme-seat-1",
  "team_id":    "acme-engineering",
  "sync_interval": 60
}

Format constraint on team_id: 4-32 chars, lowercase alphanumeric plus - and _. Omit the field for solo Pro behavior.

--check shows team_id and prints (shared-team mode) annotation when configured.

What stays private vs shared

• Private (default): every engram captured under each seat's local daemon. Stored at engrams/<device_id>/ in R2.
• Shared (opt-in via team_id): the same engram dual-writes to engrams/team/<team_id>/<device_id>/. The Worker exposes a GET /team-engrams?team_id=X endpoint that lists across all team uploads.

Until the Worker is updated with the team-listing endpoint, the X-Team-ID header is silently accepted and ignored — safe to ship before the server side is live.

Refund

7 days no-questions-asked.