Skip to content
For people who want AI to recall the right context

zakki

Your words dissolve into AI. Your records don't have to.

zakki keeps your original notes, photos, provenance, and branches in one personal memory layer. Review the raw record yourself first, then pass only the needed context to any AI through MCP.

Keep the original Mobile-first capture Recall through any AI

Why it exists

Chat history is not a memory layer

zakki turns raw records into a reusable personal layer so you can revisit what happened yourself and let connected AI recall it accurately.

01

Context dissolves into chats

You keep re-explaining yourself because the original record never becomes a durable memory layer.

02

AI recalls the wrong version

When only summaries remain, you cannot trace the source, timing, or branch behind the answer.

03

Structured note systems break the habit

Tools that demand formatting before capture make it harder to accumulate raw records in the first place.

Use cases

Build a memory layer from raw records, then let AI recall it

These examples show how you save original records, revisit them yourself, and only then ask AI to reason from the right memory.

Training log

Save reps, weight, photos, and body signals at the gym. Revisit yesterday's raw record, then ask AI to adjust today's plan from the same memory.

What enters the layer

Example: bench 70kg x 5, slight shoulder pain, gym photo

What you can ask AI to recall

Example: Recall yesterday's session and adjust today's plan without repeating the same shoulder strain

Work notes

Capture meeting notes and open questions right after the conversation. Re-read your original record, then ask AI to spot gaps or contradictions.

What enters the layer

Example: company A worries about approval flow, API limit is 60 requests per minute

What you can ask AI to recall

Example: Recall this meeting record and find contradictions or gaps I might have missed

Daily observations

Stack sleep notes, energy dips, and small observations. Look back at your own pattern first, then ask AI to recall what you may be missing.

What enters the layer

Example: slept 6 hours, focus dropped in the afternoon, bought protein on the way home

What you can ask AI to recall

Example: Recall the last two weeks and tell me what pattern I may be missing around the afternoon crash

Mobile screens

Grow a memory layer from quick mobile capture

Home, new record, photo attachment, and search all support low-friction accumulation of original records.

  • Start a new record directly from home
  • Attach a photo while the detail is fresh
  • Search later and pull the memory back
Preview of the zakki home screen
Home with raw records and quick capture
Preview of the zakki entry composer screen
Record composer with photo attachment

MCP recall flow

Pass the right memory layer to AI through MCP

Connected AI clients call only the resources and tools they need. Human-authored records stay primary, and AI-saved follow-ups stay on a separate usage meter with their own provenance.

1. Record

Add a short record or photo from mobile

2. Read via MCP

Fetch only the needed records with digest resources and search

3. AI recalls and responds

Reply with your records and branches in view

Prompt to AI

Recall yesterday's workout and adjust today's plan without repeating the same shoulder strain

What AI reads

entries://digest/2026-03-31 search({ query: "shoulder", from: "2026-03-01" })

Answer you get back

Yesterday's record shows bench 70kg x 5 plus shoulder discomfort. Today is safer if you ease off pressing and bias toward back work.

Keep the original

Capture text and images before detail disappears. The raw record stays available.

Recall through any AI

MCP lets external AI read the right slice of your memory layer. AI-saved follow-ups stay distinct from your own records and use a separate meter.

Your memory, yours

Your records belong to you. We never use them to train AI models.

Plans

Free

$0

Short-term memory layer with basic image storage

  • Text & image capture
  • Human-authored records: 50 per 30-day cycle
  • AI-saved records: 10 per 30-day cycle, counted separately from human-authored records
  • 60-day AI memory window
  • MCP read access

Premium

$9.99/month

Long-term memory layer and broader AI recall

  • Human-authored records: unlimited
  • AI-saved records: 100 per 30-day cycle, counted separately from human-authored records
  • Full-history AI memory and unlimited Focus contexts
  • Expanded image storage and purchase restore

Human-authored records and AI-saved records are counted separately.

First 14 days: human-authored records are unlimited, AI-saved records are limited to 5 total.

Get early access to zakki

Join the waitlist or volunteer for a short interview.

Need product help? Contact support