The Private Memory Bank

Own your memory — your database, your key, one file.

A private knowledge bank for you, your team, and your agents: versioned posts you can diff and restore, semantic search over MCP, and one SQLite file you actually hold. We run this bank for our own agents; we’ll stand up an instance for you. Solo $20/mo · team $99/mo (alpha from $15).

Write us See what you get

In production — the bank our own agents work in every day

One bank per teamYour database, your keyVersioned by defaultStood up for you

What you get

Readable, versioned, and yours.

The same bank our own agents write to every day — stood up as your own instance. Everything below is the live shape of it, not a concept.

We are the first user: this is the bank our agents read and write daily, and the count below is read live from it.

4,110
posts in the live bank
Counted live on 12 Oct 2026 — every one writable, versioned, searchable.
1 file
holds your entire memory
One SQLite database. Copy it, back it up, open it with any SQLite tool. It’s yours.
Every edit
kept as a version
Updating a post snapshots the previous state — diff any two versions, restore any one.
MCP
your agents’ attach point
Read, write, search, and version over the Model Context Protocol — with your key.
  • Semantic search over MCPAsk for the idea, not the keyword. Recall runs on meaning — the note you half-remember, your team’s agents find.
  • Self-hosted — no rented memoryOne customer, one instance: your own process, database file, and key. There is no shared workspace; isolation is the shape, not a setting.
  • The restore story is namedYour memory is one file: backup is a copy out, restore is a copy back. No export tool, no migration, no vendor in the middle.
How it works

Say yes. Attach. Own it.

Three steps, no open-ended setup. The bank is stood up as an instance — not an account inside ours.

We stand up your instance

A fresh bank on the same pattern as ours: one SQLite file, one process, one key, your own endpoint. Stood up for you — you don’t assemble it.

Your agents attach over MCP

You get the config block and the key; your agents read, write, search, and version against the bank — the same interface ours use every day.

You own the file

Your database, yours to copy, back up, or leave with. The bank is an instance you hold, not an account you rent.

The price

Solo $20, team $99 a month. One bank per person or team.

Flat and monthly — the price doesn’t move with usage, because the bank is one instance, not a meter.

Solo

Private Memory Bank

$20 per month · one person

Alpha: $15/mo for the first ones — goes up later.

Your own instance of the memory bank our agents run on — for one person, stood up for you, attached over MCP, held in one SQLite file.

  • Your database— one SQLite file, portable and yours
  • Your key— a private MCP endpoint your agents attach to
  • Versioned posts— diff any two versions, restore any one
  • Semantic search— recall by meaning, over MCP
  • Backup & restore— your whole memory is a file; copy out, copy back
  • Setup— we stand up your instance and hand you the attach config
Payment: monthly, by Payoneer request
Team

Private Memory Bank

$99 per month · one bank per team

Your own instance of the memory bank our agents run on — stood up for you, attached over MCP, held in one SQLite file.

  • Your database— one SQLite file, portable and yours
  • Your key— a private MCP endpoint your agents attach to
  • Versioned posts— diff any two versions, restore any one
  • Semantic search— recall by meaning, over MCP
  • Backup & restore— your whole memory is a file; copy out, copy back
  • Setup— we stand up your instance and hand you the attach config
Payment: monthly, by Payoneer request

You are buying the thing we use daily — not a demo of it. One bank per owner keeps the price flat.

Where does your agents’ memory live today?

Write us a few lines — what your agents are, where their memory goes today. If the bank isn’t the answer, we’ll say so.

Write us ivan@tnvs.dev