Provider Dash MANAGER · MPDM Download v0.8.0

Windows desktop app · v0.8.0

Every account.
One window.

Keep Google, Microsoft, AWS, Vercel, Netlify, Supabase, Cloudflare, GitHub, npm, Stripe, Gmail, Outlook and Proton Mail accounts signed in at the same time — each in its own isolated Chromium session. 37 services built in. Any other site by URL.

npx my-provider-dash-manager
Download for Windows Install guide
  • Windows 10 / 11
  • No account or telemetry
  • Free for personal & commercial use
Home — My Provider Dash Manager v0.8.0
My Provider Dash Manager Home screen: the account rail on the left and one card per account, colour-coded by service

A real screenshot from a demo profile. Names and accounts are examples.

37
built-in services
1
window for every identity
0
telemetry events
v0.8.0
current release

The problem

Every provider assumes you have one identity.

Freelancers, agencies and developers carry a personal account, a client account, a work account — often on the same service. The browser was never built for that.

WITHOUT ISOLATION
  • Signing out of one account to reach another, then signing back in again.
  • Juggling browser profiles, one window each, with no single place to see every account.
  • Asking “which account am I actually in right now?” before changing anything.
  • Losing your workspace on restart, or re-typing the fifth account's password.
  • Ads, blinding white dashboards, and a different extension setup per profile.
WITH PROVIDER DASH
  • Every account stays signed in, in its own storage partition.
  • One window: providers in the left rail, open accounts as tabs on top.
  • Every tab and rail row is colour-coded and labelled by account.
  • The open-tab set is remembered and restored on the next launch.
  • Built-in ad-blocking and dark mode, plus saved logins bound to each account.

It is not a browser and not a scraper. It is a container for identities: real dashboards, real sessions, one place.

Inside the app

Chrome for accounts, not pages.

The rail holds your identities. The strip holds only what is open. Home brings every account back into view without signing anything out.

Home — account rail and account cards
Home: providers and accounts nested in the left rail, each account shown as a colour-coded card with sign-in state
Home. Accounts stay in the rail with their own colour and live sign-in state. The installed version sits bottom-left.
Service picker, updates and saved logins
The Add an account service picker grouped by category, plus the Updates panel and saved-login controls
The Add account picker, Updates panel and saved-login controls. Captured at v0.6.2, when 27 services shipped; the current build has 37.
An isolated account tab
A Gmail account open inside its own tab, with back, forward, reload, dashboard and address bar controls
A Gmail session in its own tab, with back, forward, reload, back-to-dashboard and an editable address bar.

Screenshots use a demo profile with placeholder account names. The app's UI is shown as captured; the site does not mock up product screens.

Built-in registry

37 services ready. Any other site by URL.

Grouped by category, each with its own colour, sign-in route and multi-account guidance. The rail and Home show only the services you actually use; everything else waits in the Add account picker.

Hosting & deploy 8

  • Vercel
  • Netlify
  • Cloudflare
  • Railway
  • Render
  • Fly.io
  • Heroku
  • DigitalOcean

Databases 2

  • Supabase
  • Neon

Code & packages 6

  • GitHub
  • GitLab
  • npm
  • PyPI
  • Docker Hub
  • Hugging Face

Payments 1

  • Stripe

Google 7

  • Google Account
  • Gmail
  • Google Cloud
  • Firebase
  • Google Workspace Admin
  • Google Play Console
  • Google AI Studio

Microsoft 4

  • Microsoft Account
  • Outlook
  • Azure
  • Microsoft 365 Admin

Mail 6

  • Proton Mail
  • Zoho Mail
  • Fastmail
  • Yahoo Mail
  • Tuta Mail
  • iCloud Mail

Cloud 1

  • AWS

AI 2

  • OpenAI Platform
  • Claude Platform (Anthropic)

Not on the list? Add service by URL gives any site its own rail row and fully isolated per-account sessions. A JSON plugin manifest can go further and define how to read its API for a status card.

How extensibility works

What it handles

The daily friction, removed.

Not a dashboard skin over a browser. Each feature is built around the account as the unit of work.

01

Isolated sessions

Separate cookies, localStorage, IndexedDB and cache per account. Sign in once; sessions survive restarts and never see each other.

Accounts & sessions 02

A rail built for identities

Providers nest their accounts. Tabs exist only for what is open. Home is always one click — or Esc — away.

Layout & browsing 03

Passwords per account

Logins typed inside a tab are remembered for that account, refilled on the right origin, encrypted with Windows DPAPI, and importable from browsers.

Password manager 04

Status at a glance

Optional read-only API tokens light up project counts, names and deploy state on Home cards. Tokens are validated before storage and never leave the main process.

API status cards 05

Quiet updates

New releases download in the background and install silently when you close the app. Prefer buttons? Turn auto-update off and step through it yourself.

Updates 06

Less noise

EasyList-powered ad-blocking and Dark Reader's engine, both inside each account's session. No extensions to install or keep in sync.

Ad-block & dark mode

Security posture, honestly

Local-first. Encrypted at rest. Explicit about the limits.

Cookies, tokens and saved passwords are encrypted with Windows DPAPI. Saved logins are bound to the account and the service's own origins. There is no server, no app account and no telemetry. DPAPI does not protect against malware running as you — no desktop app can — and the installer is not code-signed yet. The site says so on the security page instead of hiding it.

Read the security model
  • DPAPI encryption for saved logins and API tokens
  • Origin-bound credential capture and fill
  • Sandboxed account views, context isolation, deny-by-default permissions
  • No sync and no telemetry — state stays on this machine

Install

Two routes. Same app.

Use the command line if you already have Node.js 18+. Otherwise download the installer from GitHub Releases. Both install the same per-user Windows app.

Download installer Requirements & CLI
PowerShell 
# install or update, then launch
$ npx my-provider-dash-manager

# installed globally? the alias works too
$ mpdm update
Windows 10 / 11 · 64-bit See requirements

From install to signed in

Three steps, no setup wizard.

  1. 01

    Add an account

    Click Add account at the bottom of the rail, choose a service, name the account, then log in or create one. The real sign-in page opens inside that account's own isolated session.

  2. 02

    Sign in normally

    Google services sign in directly. On other sites, prefer email/password or GitHub over “Continue with Google”, which Google blocks in embedded browsers. The Browser button finishes stubborn flows in your system browser.

  3. 03

    Switch and stay signed in

    Click a tab or a rail row. Everything stays warm and signed in. Optionally connect a read-only API token for a status card, or import passwords from your browser.

Straight answers

Before you install.

The full FAQ covers memory use, password import, SmartScreen, provider terms and what happens to your data.

Can I be signed into two accounts on the same service at once?

Yes. Each account gets its own Chromium storage partition, so both stay signed in simultaneously and you switch between them like tabs. Nothing is ever signed out to reach the other.

How much memory does an extra account use?

Roughly 125 MB of private memory per live dashboard (the figure Task Manager reports), on a ~350 MB baseline with everything asleep. The app keeps five tabs warm by default and sleeps the rest; slept tabs stay in the strip and resume on click.

Is it safe to store my passwords?

Saved logins are encrypted with Windows DPAPI and bound to the account and the service's own domains. A password typed on an unrelated page reached from a tab is never captured, and a saved password is never filled into a page outside the service's domains. DPAPI protects against another user on the machine, a stolen disk and casual copying; it does not protect against malware running as you, which no desktop app can. Passwords never reach the app's own UI process.

Does it work on macOS or Linux?

Not yet. The app and its installer are Windows-only. The architecture is cross-platform, so other operating systems stay open as future work.

Read all 13 questions

Stop signing out

Start switching.

One Windows app for every account you own. Free for personal and commercial use; source-available under the project licence.

npx my-provider-dash-manager
Download for Windows View source