Zero-Knowledge Backups with Pikkumies
Back up a folder from your own Linux machine to a Pulsed Media Storage Box so that only you can read the files in it, then let Pikkumies run the backup, check it and test a restore from one plain request. In the test run shown below, one sentence backed up a small Documents folder (3 files, 296 KB), read every stored byte back with restic's full check and restored the files with matching sha256 checksums: 5 minutes 33 seconds, 32,216 AI credits, about 3 euro cents of credits.
Recorded on Pulsed Media test accounts: a Linux account stands in for your machine (shown as you@laptop) and a second test account on a Pulsed Media server plays the Storage Box (shown as boxuser@storagebox). The clips come from two runs of these same steps, and long waits are shortened.
What stays private
restic encrypts your data on your machine before it leaves: file contents, file names and the snapshot list, with AES-256 in counter mode and a Poly1305-AES authentication code. The key comes from your passphrase through scrypt. The Storage Box receives the backup as encrypted data, and without the passphrase it cannot be read, by Pulsed Media or by anyone else who gets a copy, as long as the passphrase is a strong one (restic design document, Threat Model).
Some things still reach someone else in a readable form:
- The conversation with Pikkumies. Your request, the commands Pikkumies runs and their output, which include file names, paths and the repository address, go through Pulsed Media's AI credit service to the model that answers. The credit service is built never to store or log request or response contents; what the model service keeps is outside Pulsed Media's control. For a backup, restic reads the files on your machine, and their contents are not part of the conversation.
- What the box can see. Among the things restic's threat model lists, whoever holds the storage can see how big the backup is, when it changed and which address it connects from. Each key file in the repository also names, in plain text, the machine and user that created it and when. They could also delete it, which is why one backup is not enough: keep a second copy elsewhere.
The passphrase does not leave. You type it when restic creates the repository and once more at Pikkumies' login. Pikkumies keeps it in a file only your account can read and hands restic that file, never the passphrase as text. Its restic instructions tell it never to ask for the passphrase in the chat, and the login refuses to run anywhere but a terminal.
The backup runs on your own machine for a reason: restic's design assumes the machine that makes the backup is trusted. A backup made on a seedbox is still encrypted on the Storage Box, but its passphrase then sits on a Pulsed Media server, so it is not zero-knowledge. Client-Side Encryption for Your Seedbox or Storage Box covers the other ways to encrypt files before they reach Pulsed Media.
Before you start
- A Linux machine you control, with restic and the tools Pikkumies needs. On Debian or Ubuntu:
sudo apt install restic git curl wget openssh-client php-cli php-curl libatomic1
- A Storage Box and its server name and username.
- Pulsed Media AI credits and the key for them, from the client area under AI credits. Active Pulsed Media services earn them; Pulsed Media AI Credits lists how many.
Step 1: Key login to the Storage Box
Pikkumies runs restic without a terminal, so the SFTP login has to work with a key. Give the box your SSH key once. Replace USERNAME and SERVERNAME with your own:
ssh-keygen -t ed25519 ssh-copy-id USERNAME@SERVERNAME.pulsedmedia.com
SSH covers keys in more detail, PuTTY included.
Step 2: Install Pikkumies
The Virsilipas installer asks for your AI key, saves it in ~/.virsilipasKey where Pikkumies finds it, and installs Pikkumies from its public GitHub repository into your own account, with no root:
wget -q -O virsilipas.sh https://virsilipas.mcx.fi/virsilipas.sh bash virsilipas.sh pikkumies
The first install builds Pikkumies' agent runtime in the background, which takes a few minutes. pikkumies doctor shows when it is ready. The Virsilipas tutorial shows the key page and the installer step by step.
Step 3: Create the repository and log in
This step stays with you because it needs the passphrase. Set the repository address once, create the repository, then log Pikkumies in to it:
export REPO=sftp:USERNAME@SERVERNAME.pulsedmedia.com:restic-documents restic -r $REPO init php ~/pikkumies/tools/backup/restic/restic.php login --repo $REPO --human

Write the passphrase down somewhere safe. restic says it plainly when it creates the repository: losing the password means the data is lost for good.
The path after the colon has no leading slash. On a Pulsed Media box it is relative to your home directory, and sftp:USERNAME@ fails with permission denied.
Step 4: Ask for a backup
From here on, plain words are enough:
pikkumies "Back up my Documents folder to my restic repository now, then check that the backup can be read back. Keep it short."

The answer comes with a receipt for each part:
- the new snapshot and how many files it wrote;
restic check --read-data, which reads all stored data back and reports no errors were found;- the files restored into a new folder,
~/restore-check-plus the date, with each checksum matching the original.
The restore folder stays in place: deleting it was not part of the request, so Pikkumies' safety check refused to remove it. Delete it yourself when you have looked at it.
What the Storage Box sees
On the box itself, the repository is a folder of encrypted files with names that are hashes. A search for a line that is in one of the backed-up documents finds nothing:
ls restic-documents find restic-documents/data -type f | head -3 grep -r 'rent 2026' restic-documents || echo 'not found'

Getting a file back
Ask for the file in plain words, for example:
pikkumies "I deleted Documents/taxes/2026.txt by mistake. Get it back from my latest backup."
Pikkumies restores only into a new or empty folder inside your home, where the files appear under their full original path, and it refuses a folder that already has files in it. A restored file is moved back with mv -n, which never writes over a file that is already there. Removing old snapshots takes two steps: Pikkumies first shows which snapshots would go, and removes them only when you asked for that. Restoring Files from a Restic Backup with Pikkumies shows a recorded restore step by step, with the three levels of check and old-snapshot removal.
Troubleshooting
- permission denied when creating the repository: the path starts with a slash. Use
sftp:USERNAME@.SERVERNAME.pulsedmedia.com: restic-documents - The login refuses to run: it reads the passphrase from a terminal only. Run it in your own terminal, not from a script or from inside Pikkumies.
- no restic repository is set up for this tool: Step 3 has not been done on this machine. Run the login there.
- restic asks for a password at every command: restic itself does not keep the passphrase. Run backups through Pikkumies, or set
RESTIC_PASSWORD_FILEfor your own restic commands.
What a run costs
The test run above used 32,216 credits for 3 files; a larger folder takes longer and can use more. Storage Box payments earn AI credits, at multiplier 2.5 on most plans: a box paid €10 adds 250,000 credits before any account bonus, seven runs like this one, with some left over. See the Storage Box plans.
See also
- Client-Side Encryption for Your Seedbox or Storage Box: gpg, rclone crypt and encrypted folders
- Restic S3 Backup to Your Storage Box on PMSS: restic over the box's S3 endpoint
- Daily Encrypted Seedbox Backups with Pikkumies: a nightly encrypted archive of a seedbox's settings; its passphrase is kept on the seedbox, so it is not zero-knowledge
- Pikkumies on PMSS: what Pikkumies is and how it works in a seedbox account
- Storage Boxes: plans, protocols and backup tools on Pulsed Media Storage Boxes