Small teams. Big thanks. Pwdly makes GeekChamp’s list.

GeekChamp has listed Pwdly at number 27 out of 91 password managers, with an editor score of 6.2 out of 10. And the bit that made me smile most? Its best-for label: “Small teams on a fixed budget.”

That is a very Pwdly-shaped sentence. No smoke machine required.

You can read GeekChamp’s full Pwdly review. The listing is marked as checked on 20 September 2026 and is based on published product information. We’re treating it as an editorial, research-based assessment — not hands-on testing or a security audit.

A new scorecard, and a familiar sweet spot

In our last update, we talked about iTechGuides giving Pwdly 5.0 out of 10 and placing it at number 41 of 90. We resisted the urge to turn a middle-of-the-pack score into a suspiciously shiny award. I stand by that decision.

This time, the numbers are a little more cheerful. But these are two different publishers’ scorecards, not a before-and-after test. GeekChamp’s 6.2 doesn’t mean Pwdly suddenly became 24% better, and number 27 isn’t proof that we climbed somebody else’s league table. Different lists, different editorial judgements.

Still: being included again, and being described in terms that actually fit the product, feels good. I’m allowed a small grin. Possibly even a celebratory biscuit.

“Small teams on a fixed budget” is the point

Pwdly started with a fairly unglamorous problem: a team needed to share passwords, and a spreadsheet was doing a job a spreadsheet had absolutely no business doing.

The goal wasn’t to build the longest feature list in the category. It was to make that everyday work less awkward: put credentials in the right project, give the right people access, and stop turning every shared login into a little coordination exercise.

An agency needs access to a client’s accounts. A developer needs a shared service login. Someone needs the two-factor code, and the person with the authenticator app is nowhere near their phone. These are ordinary team problems. They deserve something better than another message saying “can you send me the code?”

That’s the world Pwdly is built around: project-based sharing, shared TOTP codes and a browser extension that puts the login workflow closer to where the work happens. Not a pitch to replace every enterprise identity platform on earth.

A fixed budget doesn’t make a team’s credentials less important. It just means the tool needs to earn its place in the monthly bills. Seeing GeekChamp recognise that particular fit is more meaningful to me than a generic “great for everyone” badge.

A genuine thank you

So, thank you to GeekChamp for including Pwdly and taking the time to document it. And thank you to the teams using it, reporting the rough edges and giving a small product a place in their actual working day.

As I said in the last post, feature development has been slower while other commitments need my attention. I still use Pwdly daily, as does my team, and other teams continue to use it too. That hasn’t changed.

Neither has the intention to keep it useful. A favourable mention is lovely; it’s not a substitute for maintaining the thing people rely on. We’ll take the encouragement, keep the perspective, and carry on.

One word I probably shouldn’t let slip

There is also something I’m working on in the background. I’m not ready to introduce it properly, but I’ll let one word slip:

Inboxes

That’s your lot for now. A very restrained leak, by my standards.

No launch date, no grand reveal and no attempt to turn a single word into a roadmap. Just a little hint that there’s something else on my workbench.

For today, though: number 27 of 91, a 6.2 out of 10, and a best-for label that sounds like the people I built Pwdly for. I’m grateful. And yes, I’m having the biscuit.