A small store for small apps. Your data is encrypted on your phone, so the store keeps it but cannot read it. Use ours, or host your own.
An app keeps its data in a utote store instead of on its own server. The app says what it keeps in a short file, the manifest. You connect the app to a store. Each phone, person or agent gets its own access, and you can end each one by itself.
Collections are sealed by default. Your device encrypts each document before it leaves. The store holds only the encrypted copy and a version number. Your password and your Secret Key open the keys on a new device. The store never sees either one.
An app is static files: a page, one script and a manifest. The author hosts nothing and holds nobody's data.
The store is yours to pick. Use tote.koowee.org, or run your own on cheap PHP hosting or your own machine. Apps work the same with each.
Each document is encrypted on your device. A store that is broken into gives up encrypted copies, not your lists.
A second person joins from their own phone, with their own password. Your keys never go on their phone.
An unlocked page keeps a copy and queues changes. It sends them when the store answers again.
Each document has a version. If two phones change it at once, the store keeps the first and refuses the second, so no edit is lost without notice.
Each device has its own access, tied to that device's key. End one lost phone, and the others keep working.
Put adapter.js and unlock.js beside your page. They have no dependencies and no build step. Declare your collections:
{
"app": "notes",
"schema": 1,
"needs": { "docs": {
"notes": { "key": "notes/{id}" },
"keyring": { "key": "{kind}/{who}/{what}", "clear": ["pub", "epk"] }
} }
}
Then connect, unlock and use the data:
import { Store } from './adapter.js';
import { unlock } from './unlock.js';
const store = await Store.fromLocation('tote.koowee.org', {
offline: true,
confirmInvite: host => askPerson(`Connect to the store at ${host}?`),
});
await unlock(store, { collections: { notes: {} }, ui: { askSecret } });
const notes = store.docs('notes');
await notes.set('notes/first', { text: 'hello' }, { ifVersion: 0 }); // create only
const doc = await notes.get('notes/first'); // { exists, version, data() }
The app-author guide covers conflicts, offline writes, sharing and errors. The security model says what a hostile store can and cannot do.
You do not need ours. Any server that passes the spec's conformance suite works with every app.
A store is one small server. Pick the one that fits where you can run things. The same conformance suite runs against each, so an app does not care which one it talks to.
| Server | Runs on | Holds |
|---|---|---|
| utote.php | Shared PHP hosting with MySQL or MariaDB. tote.koowee.org runs it. | Documents only. It is a relay: it keeps encrypted copies and passes them on. |
| utotepy | Your own machine, with Python and DuckDB | Documents, settings, files and optional SQL, with an MCP server for agents |
| utote-node planned | Node.js, where Python is hard to install | Not decided yet: a full server or a relay. There is no code yet. |
# copy the relay files to your host, then on the host:
php relay.php schema # make the tables
php relay.php init me/notes/main manifest.json # add an app
php relay.php invite me/notes/main write https://notes.example/ # a link for one device
uv sync
DS_ROOT_TOKEN=change-me DS_ROOT_NS=home DS_DATA_DIR=./data \
.venv/bin/python -m utotepy # listens on 127.0.0.1:8787
Put a proxy with TLS in front of it. The developer guide lists every setting.
Attach a store to DuckDB and query it with SQL, outside any app. Encrypted data opens on the machine where DuckDB runs. The store still never sees a key. It reads first. Writes come in a second version. There is no code yet.
INSTALL tote; LOAD tote;
ATTACH 'https://tote.koowee.org/me/notes/main' AS notes (TYPE tote, KEY_FILE '~/.config/utote/laptop.jwk');
SELECT key, body->>'$.text' AS text FROM notes.docs.notes;
A later add-on for utote.js will let a page hand its decrypted documents to DuckDB-Wasm in the browser, to read. Read the DuckDB roadmap.
A store server for Node.js. See Host your own.
Both are small, and both are ours.
utote is early. Read this before you keep anything in it.