ACCESS / PRIVATE BETA
Get Sophia.
Not publicly available yet.
01 / RELEASE
In development.
Sophia is in private beta. The public release will be open source under Apache 2.0. Our v1 criterion is daily use: our own agents consistently choosing it because it saves them time and makes their work better.
02 / REQUIREMENTS
What you need.
- OS
Linux. Debian and Ubuntu first.
- AGENT
Codex or Claude Code for supervised sessions. An MCP-speaking client for a connection you manage.
- MODEL
Your own model keys or configured local provider. No bundled cloud key. No silent fallback.
- SPEND
Mining is model calls on your own bill: every document or code module that becomes typed facts costs at least one call. The authors mined this repository’s 2,400 modules with small-model seats in batches of six. No dollar figure has been measured yet; when one exists it goes on the status page, labelled as measured or estimated.
03 / REMOVAL
Taking it off again.
Three steps, in this order, because the first one needs the installed wrapper to stop the service safely.
- 1
As your own user, no sudo:
/usr/lib/sophia/bin/sophia-install-user-service --uninstall. It stops and disables the user service and deletes the unit file. - 2
Quit Sophia from its tray menu.
- 3
As root:
sudo dpkg -r sophia-daemon.
The package never touches your home directory, so removal leaves your record where it is: the encrypted databases, backups and vault under your data directory, and the encryption key in your keyring or its file fallback. Delete those yourself if you want nothing left.
04 / IF THINGS BREAK
What survives.
- DAEMON DIES
Every write lands in an append-only journal first. After an unclean shutdown the database’s own integrity check runs during boot before anything is served, and a boot that cannot verify refuses to write rather than guessing.
- KEY LOST
The encryption key lives in your OS keyring with a file fallback beside the data. A copy of the database without that key is unreadable, so back up the key with the data. Nothing in the daemon can recover a lost key.
- RESTORE
Scheduled backups are verified bundles: a compacted copy of the record, its journal witness and its wiki. Restore checks identity and hashes before it replaces anything, and moves what it replaces aside rather than deleting it.
- EXIT
Your documents stay on disk as ordinary files. A plaintext export of the record itself is planned and not yet available.
Source-checked against the install and data-and-backup guides in the product repository on 2026-09-11. Guarantees and their limits: the trust covenant.