Here's how our Vauz 2 beta demo in Calgary went
On Wednesday, November 4, we had a stand in Calgary with a Mac running the Vauz 2 beta, and people wandered over to see what the fuss was about
Beta.5 went up on our download page the afternoon before. That’s about as much buffer as a small team ever leaves itself 🙃 It held up anyway. Nothing crashed, nothing froze, and nobody had to hear “it worked this morning, I swear”
How many people came by? No idea. We didn’t count, and counting people isn’t really our line of work. What we can say is thank you, to everyone who stopped, poked at the Mac, asked the awkward questions and argued with us a little. That’s exactly what a beta is for
What we brought
Vauz 2 isn’t a new coat of paint. It’s a new Vauz, built from scratch, and we went back through nearly every part of the old one and rebuilt whatever we weren’t happy with. The vault, the way it unlocks, the autofill, the updates, all of it
It’s a preview, so it’s Mac only for now: Apple silicon, macOS 14 or later. Everything in it is free until 31 December 2026. After that the Plus and Premium features need those plans, and the free plan stays free for life
In beta.5
- Auto-lockwhen you step away, switch windows or your Mac sleeps
- Wrong V-Key lockout3 wrong tries and you wait, longer each time
- Scheduled backupsto a folder you choose
- Import and exportVauz's own JSON, CSV and TXT, and CXF from any manager
- Clipboardcopied passwords wiped after a minute, and clipboard-history apps asked not to keep them
- No outbound requestsone switch, invisible on any network
- Signed updatesAuto-install, Notify or Security only
Coming soon
- Sync
- Windows
- Linux
- iOS
- Android
- Passkeys
One honest catch: the beta takes Vauz 1.x’s place on your Mac, and it can’t open a 1.x vault. So if you’re on 1.x, export your logins first with Encrypt files on, keep that file somewhere safe, and then install
Question everybody asked
“So how are you different from other password managers?”
We lost count of how many times we heard that one, which is on brand. Here’s the answer we gave, give or take some hand-waving
Your vault lives on your machine. In beta.5, Vauz never sends it anywhere. There’s no cloud copy on our servers. Online backups and a relay sync between your devices are coming soon. Both will be optional, and whatever they send to our servers is sealed on your machine before it leaves, so all we’d ever hold is a locked ciphered box we can’t open
There’s nothing to remember unless you want something to remember. Out of the box, the key to your vault is protected by your Mac’s Secure Enclave, a security chip whose own key never leaves it. So the vault opens on your machine without you typing a thing, and on no other. If many people use your machine, or if your machine is prone to malware - set a V-Key. Then, your vault is encrypted using your V-Key. If you forget the V-Key - nobody can reset it for you, us included. If you’ve turned on Touch ID, it still opens the vault and lets you set a new V-Key, as long as no fingerprint has been added or removed since. Without Touch ID, and with a forgotten V-Key the vault stays locked forever (your vault is so secure that even quantum computers can’t decipher it. For now )
The extension doesn’t keep your logins and passwords. It’s just a runner. Before it gets so much as a username, Vauz asks you, in the Vauz app, outside the browser where a web page can’t reach it
The list of usernames sits in a frame that belongs to the extension. The web page gets a box it can’t read, can’t style and can’t click into. And Vauz only acts on real clicks and key presses from you, so a page script faking a click gets nothing. Pages that aren’t https never get a fill at all. An address dressed up as a well-known site gets nothing either, and a near-miss gets a warning first
Is that slower than a browser filling everything on its own? A little, yes
Is it safer than a browser filling everything on its own? Also, yes
You approve the site before a login shows up. That’s the trade-off 🤷♂️
One switch turns off every request Vauz makes. It’s called “No outbound requests”. Toggle it on and Vauz sends nothing (unless you ask it to), so it works fully offline. That’s also a trade-off, and with no outbounds on, you get no updates, no security fixes, but you have a password manager that’s invisible on any network. Your choice
The surprise: everything lives in the browser
The thing that caught us off guard wasn’t a question. It was how many people keep every single password in their browser and had never given it a second thought. The reasons came in a few flavours, all of them some version of “convenience over security”
Look, we get it. Convenience wins most arguments 🤷 But your browser’s saved passwords are the first drawer an infostealer opens. We went through how that malware works, and the short version is that it grabs saved passwords and signed-in sessions in one go and ships them to the scammer behind it. To be straight about it, no password manager stops malware that’s already running as you. Not ours, not anyone’s. What changes is how much one bad download is worth
Underneath that was a bigger shrug about internet hygiene in general. So, for anyone who walked past our stand, here’s the free version, no download required:
- One password per site. A leak at one shop shouldn’t open your email. A password manager, any password manager, makes this painless
- Your email password is the big one. Everything else gets reset through your inbox. Make it unique and turn on two-factor there first
- Install the updates. The boring button is the one that closes the holes that are already public
The vibe coder and the .env file
Our favourite chat of the day had nothing to do with Vauz. Someone who builds apps with an AI assistant (“vibe coding”, for anyone whose corner of the internet hasn’t come across the phrase yet) stopped by, and somewhere in the conversation it turned out nobody had ever told them that an .env file must never be committed to GitHub. So we did
In case you vibe-code too, here’s the lesson. An .env file is where an app keeps its secrets: API keys, database passwords, tokens for every paid service it talks to. Spoiler alert: Vauz is going to replace the .env file soon. Your secrets will live in Vauz, and any agent that needs one asks Vauz for it. You confirm every single use, the way you approve a fill, and by default the agent never even sees the key 🤫 It’s not in the beta yet
-
Put
.envin.gitignorebefore your first commit. Then git never picks it up -
Commit an
.env.exampleinstead. Same names, fake values, so the next person (or the next AI) knows what to fill in -
Already committed it? These stop git tracking the file and keep your local copy. They don’t scrub the commits you’ve already made, so if any of those reached GitHub, or might, read the next point
echo ".env" >> .gitignore git rm --cached .env git add .gitignore git commit -m "Stop tracking .env" -
Already pushed it? Then the keys are out, and the fix is new keys. GitHub’s own guide on removing sensitive data says to revoke or rotate the secret as the first step. Deleting the file in a new commit doesn’t take it out of history, and copies can live on in clones and forks
This is not a rare mistake. GitGuardian’s State of Secrets Sprawl 2026 counted 28.65 million new hardcoded secrets in public GitHub commits in 2025, 34% more than the year before. In the same report, commits made with Claude Code’s help leaked a secret 3.2% of the time, against 1.5% for public GitHub as a whole. Whether that’s the robot or the human holding it, we’ll let them sort it out 🤖 And leaked keys don’t expire out of embarrassment: more than 64% of the secrets GitGuardian confirmed as valid in 2022 still worked in January 2026
So, vibe coder, if you’re reading this: rotate the keys. Then come back and tell us how the beta went
Try it, break it, tell us
The Vauz 2 beta is a free download for Macs with Apple silicon and macOS 14 or later. It updates itself to each new beta and then to Vauz 2.0, unless you’ve switched off outbound requests. Windows, Linux and sync come later
Then tell us what works and what doesn’t through the feedback form . We read every message. But don’t write us hate messages, pretty please 🥺👉👈
And to everyone who came over on Wednesday: thanks for the questions, the curiosity and the pushback. Calgary, you were great
Try the beta
Vauz 2 is on Macs now, and every feature is free until 31 December 2026.
The beta runs on Macs with Apple silicon and macOS 14 or later. Download it, try to break it, and tell us what happened. The free plan stays completely free for life, with Plus and Premium available when you need more!
Use Vauz completely free — for, like, ever