Skip to content
Developer Tools & AutomationD-06Live in production

Strongroom

A password vault, client tracker and team notebook for an agency — the server cannot read the vault

Timeline
2026 — present
Repositories
1
Role
Product architecture, zero-knowledge vault, real-time chat and billing
Summary
A self-hosted workspace for agencies. Every client is one project with its own encrypted vault, docs, people and a weekly status that builds a twelve-week health pulse. Secrets are encrypted in the browser with the same model as Bitwarden; the server only ever holds ciphertext.
600,000
PBKDF2 rounds
the master password never leaves the browser
$0
Starter plan
up to 3 people and 5 clients, with chat and boards included
14 days
Free trial
on Team and Agency, with no card

What we built

Strongroom, in use

Sample data, real screens. The product itself is atstrongroom.zyntlow.com.

Open a client, open the vault, and the login and its live 2FA code are right there. Encrypted in your browser: we only ever store ciphertext.

What it is

Strongroom is a workspace for an agency, live at strongroom.zyntlow.com. Each client is one project: its own encrypted vault of logins, its docs, its people, and a weekly status that builds a twelve-week health pulse. Sign up and the agency gets an address of its own, such as acme.strongroom.zyntlow.com, and a private database.

The governing constraint is the one behind the other live products, applied to secrets: the server cannot read the vault. It runs on a server, not on a laptop, and what it stores is ciphertext.

The hard parts

The vault is encrypted before it leaves the browser. The master password becomes a key through PBKDF2-SHA256 at 600,000 rounds. That key seals a random user key with AES-256-GCM, and the user key seals an RSA-OAEP private key. Each client has its own AES-256 key, sealed separately for each person with their public key. The server keeps an email, a name, a role, a scrypt of the auth hash, sealed keys and ciphertext.

Removing someone rotates the key. Taking a person off a client, or off the team, gives every vault they could open a new key: items are re-encrypted in an admin’s browser and the new key is sealed for the people who stay. New people are confirmed by comparing a fingerprint on two screens, so a compromised server cannot swap in its own key.

A tracker that people actually update. The board groups clients by health: at risk, blocked, watch, on track. A health only moves with a written reason, and a client with no update for seven days shows as needing one.

One workspace, one SQLite file. Each agency’s data sits in its own file, chosen from the address of the request. Every request and every background job runs inside one workspace’s context, so no query can reach another’s data.

Around the vault

  • Pages — a notebook for playbooks and SOPs, with templates and / blocks. Pages are shared notes, readable by anyone on the client; secrets go in the vault.
  • Chat and huddles — a channel for the team, a chat for every client, and calls over LiveKit. Anything that needs someone arrives as a banner, a push and an email.
  • Contracts — drafted in the same editor as Pages and sent as a link. The signer needs no account; what is kept is the answers, the signature, the time, the address and device, and a SHA-256 fingerprint of exactly what they saw. The PDF is made on the server.
  • Connections and Adams — call transcripts and documents from Google Drive, any app that can POST, and TallyHubGh’s partner directory are filed under clients and made searchable. Adams answers over all of it, and sees only an inventory of the vault, never a password or a code.

Plans and billing

Starter is free for up to three people and five clients. Team and Agency are priced per person per month in US dollars, start with a 14-day trial and need no card. Billing runs through Paystack, with a signed webhook, a seven-day grace period on a failed renewal, and credit for unused time when changing plan.

What it is not

Nobody can recover a lost master password; an admin can reset a person, who sets a new one and is confirmed again. Client names and status updates are plaintext, because they are the tracker, not the vault.

Next product
Ferry

Drop a file on one device, pick it up on the other — no app, no account, and big files never touch the server