DEV Community

A sync server that cannot read your data (Raspberry Pi, 30 minutes)

Your password manager syncs through someone else's server. Mine syncs through a Raspberry Pi in my flat - and I can tell you exactly what that server can and cannot see.

The idea: a server that cannot read anything

A sync server is a small service that accepts encrypted records and hands them to your other devices. The important part is what it does not have:

  • no master password;
  • no keys;
  • no plaintext - only nonce, ciphertext and version metadata.

That is the zero-knowledge model: the server is blind storage. If someone steals the Pi, they get ciphertext. If I forget the master password, the data is gone - and that's the honest trade-off, not a bug.

What you need

  • Raspberry Pi 4 (2-4 GB) or Pi 5, power supply, case;
  • an SSD (preferable to microSD for a database);
  • Debian / Raspberry Pi OS lite;
  • the tenvault-sync binary (Rust) or the Docker image;
  • 20-30 minutes and SSH access.

Setup, in short

sudo apt update && sudo apt upgrade -y
mkdir -p ~/tenvault/data
TENVAULT_ADDR=0.0.0.0:8095 TENVAULT_DB=~/tenvault/data/vault.json ./tenvault-sync

Then a systemd unit so it survives reboots and crashes: dedicated user (not root), Restart=always, ReadWritePaths limited to the data folder, logs via journalctl -u tenvault-sync.

The part everyone forgets: exposure

Do not put the plain HTTP port on the internet. Use a Cloudflare Tunnel (free) or a reverse proxy with a certificate. SSH by keys only. Revoke devices you no longer use - device tokens are long and random, and revocation is a feature, not an afterthought.

Backups, and the only rule that matters

Daily backup of the database, encrypted, on a separate disk. And once a month: restore it on a copy and confirm the data is there. A backup you never restored is not a backup - it is a hope.

What it costs

  • Pi 4/5: $60-110 one-off;
  • SSD: $25-50;
  • electricity: 2-5 W - a few dollars a year;
  • domain (optional): from $3/year; Cloudflare Tunnel is free;
  • your time: half an hour.

Compare that with a cloud password manager subscription for a family or a small team over two years - and the data stays on someone else's server the whole time.

When this is a bad idea

If you don't want to administer anything, don't self-host. A server needs updates, backups and an occasional reboot. The good news: devices keep their local copy, so a dead server doesn't mean lost data - just delayed sync.

The full guide, with the systemd unit, failure scenarios and the TenVault case: Self-hosted sync server on a Raspberry Pi. The password manager itself: TenVault.

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.