Your Password Manager Isn’t a Launcher

Every morning I open Keeper, search for “GA4”, copy the URL, paste it into a new tab, and repeat that little dance for Search Console, three localhost ports, and whichever GitHub repo I’m reviewing that day.

Keeper is excellent at the one job it’s built for: keeping my passwords safe. But as a way to launch the twenty-odd things I actually touch every day, it’s painful. No one-click “open my whole workspace”. No tagging by project. No quick visual scan to remind me which of these three localhost ports is the frontend. Just a flat, alphabetical list of secrets.

So I went looking for a better way to organise the links and environments I use daily — and it turns out there isn’t one right answer. There are three, depending on how much setup you’re willing to do.

TL;DR:

• A password manager is a security vault, not a launcher — keep credentials there and nothing else.
• For daily work, use browser tab groups (Chrome saves closed groups for one-click reopening) or a keyboard launcher such as Raycast.
• For a status overview of local and remote services, self-host a dashboard: Homepage or Dashy show live up/down indicators; Linkding is a tag-first bookmark store.
• My setup is two layers: tab groups for daily execution, a small Homepage instance for cross-project audits.

---

Why a password manager makes a bad developer launcher

Password managers are optimised for security, not speed. Every entry is one flat item behind a master password, sorted alphabetically or by folder at best. There’s no concept of “open these six things together because I’m about to review a deploy”, and no live indicator telling you whether localhost:8000 is even running before you click through to a connection error.

That’s not a flaw — it’s just a different job. Once I accepted that, the question became simpler: what is built for fast, grouped, visual access to the tools and ports I use every day?

---

The three options (dashboards, tab groups, launchers), a comparison and a checklist follow below.

Option 1: Self-hosted developer dashboards (Homepage, Dashy, Linkding)

🔒 Subscribe to keep reading.

Option 2: Browser tab groups and bookmark managers (no deployment)

🔒 Subscribe to keep reading.

Option 3: Raycast Quicklinks and OS-level launchers (keyboard-first)

🔒 Subscribe to keep reading.

Comparison: dashboards vs tab groups vs launchers for developer links

🔒 Subscribe to keep reading.

Two-layer system: tab groups for daily work, Homepage for audits

🔒 Subscribe to keep reading.

Mental model: password manager vs launcher vs dashboard

🔒 Subscribe to keep reading.

Checklist for organising developer links and local environments

🔒 Subscribe to keep reading.

Final thoughts on organising developer links

🔒 Subscribe to keep reading.

References

🔒 Subscribe to keep reading.