SecureVault

Three steps.

Your own server first, then the app on your devices, then the agent. You host the server yourself; nothing runs in our cloud.

  1. Your server

    The vault is one MariaDB database on a machine you own that is always on: a Raspberry Pi, a home server or an always-on PC. Your devices reach it on your home network, or over Tailscale when you are away. Never open its port to the internet.

    Point your agent at this. Give this line to an AI agent with a shell on that machine:

    It looks at the machine, asks you what it cannot see, downloads the server kit, checks its SHA-256 and sets up the database, a firewall rule and a nightly backup. See what it does, what it asks and what you still do yourself.

    Or by hand

    mkdir -p ~/securevault-server && cd ~/securevault-server \
     && curl -fsSLO https://vault.littlehelpers.se/download/securevault-server-kit-1.0.0.tar.gz \
     && echo "4b4c37c675aad97595a976b6b5a4c1539efa40b2674d30f5f3e296173941265b  securevault-server-kit-1.0.0.tar.gz" | sha256sum -c - \
     && tar -xzf securevault-server-kit-1.0.0.tar.gz --strip-components=1
    sudo ./install.sh

    The installer is for Debian, Ubuntu, Raspberry Pi OS, Arch Linux and Fedora. It needs root: it installs MariaDB if it is missing, writes one MariaDB settings file and adds a firewall rule. It creates the database and one user with a generated password and rights on that database only, limits the port and that user to private addresses, and prints a securevault://connect line and a QR code for step 2.

    On any other computer the kit runs in Docker with three commands (run on Linux only; Docker Desktop on macOS and Windows was not tested). The manual has every option, use away from home with Tailscale, backup and restore, and what was tested.

  2. The app

    Download the free app for Linux, Windows, macOS or Android. On first run it asks for your server: paste the securevault://connect line from step 1 or scan its QR code with a phone, or type the hosts, port, database, user and password. Then create your master password.

    # Linux: unpack into ~/.local/share and start it
    mkdir -p ~/.local/share && tar xzf securevault-1.1.1-linux-x64.tar.gz -C ~/.local/share
    ~/.local/share/securevault/securevault

    Windows: unzip and start SecureVault.exe. The app is not signed yet, so Windows asks first: choose More info, then Run anyway. macOS: open the disk image and drag SecureVault to Applications. Android: open the APK and allow your browser to install apps.

    The settings are kept in server.json on desktops (Linux: ~/.config/securevault/server.json, Windows: %APPDATA%\SecureVault\server.json) and in secure storage on Android. You can import existing passwords from Chrome, Bitwarden or Aegis under Settings, Import data.

  3. The agent

    Buy the Agent licence and download the agent module from your own download page. It runs on the Linux computer where your agents work, next to the SecureVault app, and reads the same server.json.

    tar xzf securevault-agent-1.1.1-linux.tar.gz
    cd securevault-agent-1.1.1
    ./install.sh
    claude mcp add --scope user secure-vault -- node ~/.local/share/securevault-agent/server.js

    The installer needs no root, installs into ~/.local/share/securevault-agent and checks what is missing. The last line adds the module to Claude Code; other MCP clients start the same server.js with node (stdio). If the app is not in ~/.local/share/securevault, tell the installer where it is: ./install.sh --app /path/to/securevault.

    Your agent can then ask the vault to sign in. Signing in to the app also unlocks the vault for your agents, until midnight unless you set another open limit in the app. When that has run out, the app asks for your master password again.

    What the agent module needs

    • Linux (x64) with a desktop session, Node.js 22 or newer, and the SecureVault app on the same computer, unpacked as in step 2
    • A Chromium-based browser for your agents with its own profile and a DevTools port, and an agent that can open pages in it: chromium --remote-debugging-port=9333 --user-data-dir="$HOME/.local/share/securevault-agent-browser"
    • ss (package iproute2); notify-send for a notification on every use
    • E-mailed and SMS codes are optional and stay off until you set them up; the README in the package says how

    Release 1.0.0 of the agent module was tested end to end on an X11 desktop. Hyprland, GNOME and KDE are handled by the code but were not tested in that release.