504,105 visitors this month

Latest reviews

RHRhea Vandermeer3d ago
I put off making a product video for about six months because every previous attempt turned into an afternoon in an editor. Recorded the screen capture, dropped it in, picked a template and had something I was not embarrassed by in under an hour. The part that actually saved me was the automatic captions — most people watch these on mute and I would not have bothered otherwise. My one complaint is that the template choice matters more than it looks like it does; the first one I picked made everything feel like an advert.
Typeframes
TOTobias Lindqvist9d ago
Set this up for a small open source project after people kept asking where they could send something. Took about ten minutes and the first support came through the same week. What works is that supporters do not need an account — that single thing removes most of the drop-off I saw with the alternative I tried first. Payouts have been on schedule. Marking it four rather than five because the analytics are thin; I would like to know where people are arriving from and I cannot tell.
Buy Me a Coffee
MAMarguerite Osei15d ago
Been using this for about four months for content planning. It is genuinely good at surfacing things I would not have thought to look for, and a couple of those became our best-performing posts of the quarter. Worth being realistic about what the numbers are though. The growth figures are directional rather than exact, and I have seen a few topics flagged as rising that were really one large news cycle. I treat it as a list of things to go investigate rather than a list of things to go write, and on that basis it earns its cost.
Exploding Topics
DEDevashish Raman22d ago
I have used this on every backend project for years and it is still the first thing I install. Collections shared across the team save a genuine amount of onboarding time, and the scripting is powerful enough that we run a decent chunk of our integration checks through it. The honest criticism is that it has grown a lot. What was a fast request client now takes a while to start and pushes cloud features I do not want. It is still the tool I reach for; I just notice the weight now in a way I did not three years ago.
Postman
PRPriyanka Balachandran1mo ago
Moved a marketing site and two documentation sites over last year. The thing I did not expect to care about was deploy previews on every pull request — being able to send a designer a working link instead of a screenshot changed how our review process works. Rollbacks are one click and have saved me twice. Build minutes are the thing to watch on the pricing side; our docs site rebuilds often and we hit the limit faster than I planned for, so check that before committing if you deploy frequently.
Netlify

Password Managers

Storing and sharing credentials safely.

Nothing launched in this category yet.

About Password Managers

A password manager is the single highest-return security decision an individual or a small company can make, and the reasoning is simple: the overwhelming majority of account compromise comes from passwords reused across services, and a manager is what makes not reusing them practical. Everything else in personal security is a refinement on top of this.

The launches here divide into cloud-synced managers, local-only managers, and the family and team tiers that add shared vaults. For most people the cloud-synced option is correct, because a manager you cannot reach on your phone is one you will work around. The security model to look for is end-to-end encryption where the provider cannot decrypt your vault — which means a forgotten master password is unrecoverable, and that is the correct trade.

Local-only managers, where an encrypted file lives on your own machine and you handle synchronisation, remove the provider from the trust equation entirely. They suit people who are comfortable managing the file and its backups, and they fail badly for people who are not, because a vault that exists in one place is a vault one drive failure from gone.

Passkeys are the meaningful development in this space and are worth adopting where offered. They replace a password with a key pair bound to the site, which structurally defeats phishing: there is nothing to type into a fake page. Most managers now store and sync them, and the practical advice is to use passkeys where available and keep the manager for everything else, which will be the majority for years.

For teams, shared vaults solve a real problem — the credentials that currently live in a chat message from two years ago — and introduce a governance requirement: knowing who can reach what, and removing access when someone leaves. Tools with proper audit and provisioning are worth the premium at any size above a handful of people.

Two practical notes. First, set up recovery before you need it: an emergency access contact or a printed recovery code stored physically. Second, application secrets are a different problem with different tooling; see [secrets management](/categories/secrets) rather than putting production keys in a personal vault.