Your AI coding
memory, everywhere
deja captures what you and your coding agent discover — gotchas, patterns, decisions — and syncs them across every machine. Never explain the same thing twice.
Three commands. Zero friction.
Save discoveries as you code
Run deja save from your terminal (or let your agent do it) whenever you hit a gotcha, nail a pattern, or make an architectural decision.
Cloud syncs in the background
deja.sh receives the memory instantly and makes it available on every machine where you're logged in. No manual push, no conflicts.
Load context before you start
Run deja load with a description of what you're about to work on. Your agent gets the relevant memories injected as context automatically.
Built for developers who
hate losing context
Six memory types
gotcha, decision, pattern, preference, progress, procedure — each type tells your agent how to use the memory.
BM25 full-text search
Postgres tsvector with GIN index. Search by content, filter by type or project. Fast even at scale.
Isolated by user
Every memory is scoped to your account. Project-level namespacing keeps work and personal memories separate.
Delta sync
Only memories updated since your last sync are transferred. Resumable, offline-safe, conflict-free.
PAT authentication
Browser-based login generates a Personal Access Token. CI/CD environments use --token for headless login.
JSONL export
Your data is always yours. Export everything as JSONL from the dashboard or API. No lock-in.
Simple, honest pricing
For getting started.
- 200 active memories
- 3 projects
- Cloud sync
- Web dashboard
- BM25 search
For daily drivers.
- 5,000 active memories
- 10 projects
- Priority sync (<100ms)
- JSONL export
- Everything in Free
// powered by Stripe · cancel anytime
// memory limits count active rows only — archived memories don't count toward your quota
Common questions
>What is deja exactly?
deja is a CLI tool that lets you save and recall memories from AI coding sessions. deja.sh is the cloud sync layer — your memories follow you across machines.
>How does authentication work?
Run deja login. It opens your browser, you sign in with Google once, and the CLI receives a Personal Access Token. No OAuth in the CLI — it just gets a token.
>Do I need deja.sh to use the CLI?
No. The CLI is fully functional offline with a local SQLite database. deja.sh is optional cloud sync. If you never run deja login, everything works locally.
>How is my data protected?
All memories are isolated by user_id at the database level. Tokens are stored as SHA-256 hashes. TLS in transit. Railway hosting with backups.
>Can I self-host?
Yes. The API is a NestJS app and the web is Next.js. Both run with a Postgres instance. See the self-hosting guide in the docs.
>What happens when I cancel a paid plan?
You immediately drop to the Free tier (200 active memory limit). Your existing memories are preserved — you just can't add new ones until you're back under the limit. Archiving is one way to get back under: archived memories don't count toward your quota.