Point your agent at this.
Your vault server is one MariaDB database on a machine you own. Your AI agent can set it up. Give it one line:
Read https://vault.littlehelpers.se/agent-setup.md and set up my SecureVault server by following it.
For an AI agent with a shell on the machine that will host your vault. Read the page it reads.
What your agent does
- Looks first: the system, systemd, Docker, Tailscale, and whether a database already runs there.
- Takes one path. The installer on Debian, Ubuntu, Raspberry Pi OS, Arch Linux or Fedora. Docker on any other computer. An Android phone only if you insist.
- Downloads the server kit and checks its SHA-256 before it unpacks anything.
- Sets up one database and one user that can do nothing outside it, with a generated password, reachable on your home network or over Tailscale and from nowhere else.
- Reports four things as they stand, each with a yes or a no: database, starts after restart, firewall rule, nightly backup.
What it asks you
- Which machine hosts the vault. It must be on whenever you want your passwords.
- Whether your devices are only at home, or also away. Away from home needs Tailscale on the server and on every device.
- Which address your other devices reach that machine at, if it has more than one.
- What to do if the machine already runs MariaDB or MySQL. It stops and asks.
- Your yes before it gives anything up, for example on a machine that cannot start the database by itself.
What you do yourself
- Install Tailscale or Docker and sign in, if your set-up needs them. The agent does not install them.
- Type any command that needs your sudo password. The agent never asks for a password.
- Show the connection in your own terminal. The agent gives you the command; it prints a
securevault://connectline and a QR code that the agent never sees. Paste or scan it in the app. - Give the server a fixed address in your router.
- Keep a copy of the backups somewhere else. A backup on the server does not survive the server.
What it must not do
The page gives the agent rules. It never makes the database reachable from the internet, never chooses or prints the password, never opens the files that hold it, and never deletes data unless you asked for exactly that.
The database password is generated by the kit. Secrets in your vault are encrypted on your devices before they reach the database; account names and usernames are not, which is why the database stays on private networks.
What was tested
On 20 November 2026, in containers on one x86-64 Linux desktop: the installer on Debian 12 and 13, Ubuntu 22.04 and 24.04, Arch Linux and Fedora 45; Docker Engine 29 on Linux, with the clients on the same computer. An Android phone once, on one Samsung Galaxy A54.
Not tested: a real Raspberry Pi and Raspberry Pi OS (only Debian 12 for 64-bit ARM, emulated), Docker Desktop on macOS and Windows, a Docker server reached from another machine, SELinux in enforcing mode, a real Tailscale network, other Linux distributions, and a phone server after a reboot. Your agent says so in its report when you are on untested ground.
Read it yourself
- agent-setup.mdThe page your agent follows, as plain text.
- The self-hosting manualThe same steps for people: every option, backup and restore, update, uninstall, troubleshooting.
- Server kit 1.0.0securevault-server-kit-1.0.0.tar.gz, 36 kB. Installer, Docker Compose set-up, backup and restore scripts, the manual.SHA-256 4b4c37c675aad97595a976b6b5a4c1539efa40b2674d30f5f3e296173941265b
- llms.txtFor agents that look for it.