Provider Dash MANAGER · MPDM Download v0.8.0

Features · v0.8.0

Built around identities,
not tabs.

My Provider Dash Manager keeps every account signed in inside its own Chromium session, then gives you one deliberate place to switch, secure and keep track of them. Here is exactly what that includes.

  • 37 services built in
  • Any site by URL
  • Windows 10 / 11

01 · Accounts & sessions

Each identity gets its own world.

Every account is a persist:<service>__<account> Chromium partition: separate cookies, localStorage, IndexedDB and cache. Accounts can never see each other's session.

Any number of accounts

Add as many accounts per service as you need. Switching is just activating another live view; nothing is signed out to reach the other.

Sessions survive restarts

Sign in once and stay signed in. The open-tab set is saved and restored; recent tabs come back warm, the rest asleep, and you land on Home.

Warm tabs, bounded memory

Each live dashboard costs roughly 125 MB of private memory, so the app keeps a configurable number warm (default 5) and sleeps the rest. Slept tabs stay in the strip and resume on click.

Optional per-account proxy

Route one account through a proxy when a client or region requires it, with proper connection flushing when the setting changes.

Measured, not guessed

5 live tabs≈ 1.0 GB
10 live tabs≈ 1.6 GB
All tabs asleep≈ 0.35 GB

Private memory, the figure Task Manager reports. Roughly 125 MB for each live dashboard on a ~350 MB baseline.

02 · Layout & browsing

The chrome never gets in the way.

The left rail holds providers and their accounts. The top strip holds only open tabs. Account pages are rendered beneath that chrome, so Home and switching controls are always reachable.

  • Left rail — your identities. Providers you use, accounts nested underneath, with hover actions to open, sleep, close, fill login, connect a token or manage. Collapse any provider.
  • Top bar — open tabs only. A filter box and group-by-provider mode with collapsible groups. Slept tabs stay in the strip, dimmed.
  • Home is always close. Every account as a card with live status, the service picker, the Updates panel and saved-login settings.
  • Browser controls. Back, forward, reload/stop, back-to-dashboard and an editable address bar. Navigation stays inside that account's session and accepts http/https only.

KEYBOARD

Ctrl W
Sleep tab
Ctrl Shift W
Sleep all
Ctrl Tab
Cycle tabs
Ctrl 1…9
Jump to tab
Esc
Home
Alt ← / →
Back / forward
Ctrl R or F5
Reload
Ctrl L
Address bar

03 · Built-in services

37 services, grouped by the work.

Each entry has its own dashboard and sign-in URLs, colour, multi-account policy and optional API token type. Login pages are verified to load inside an isolated partition and land on a host the credential guard trusts.

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)

Google sign-in works inside the app. Third-party “Continue with Google” flows are different: Google blocks those in embedded browsers. The app's Browser button hands a stubborn flow to your system browser, and the rest of the app keeps working.

04 · Password manager

Two accounts. Two passwords. No guessing.

Saved logins belong to the account that typed them, not just the site. That is the difference between a password manager and a password manager that understands identities.

Capture inside the account

Logins typed inside an account tab are remembered for that account. Two accounts on the same service refill with different credentials.

Autofill or manual fill

Sign-in pages are recognised and filled when autofill is on; a manual fill action is always available from the account's rail actions.

Manage every login

Home → Saved logins → Manage logins groups every stored login by service, with delete. No password is ever shown.

Choose the default

When more than one login matches a site, the app asks instead of guessing. Your choice is remembered as that account's default, marked ★ in the manager.

Import from browsers or CSV

Read installed Chromium browsers directly (Chrome, Edge, Brave, Vivaldi, Opera) or import a CSV from any browser, including Firefox. Re-importing updates changed passwords instead of keeping the stale one.

Encrypted and origin-bound

Encrypted at rest with Windows DPAPI. Passwords never reach the app's own UI process. A login is tied to the account and the service's own domains, so a password typed on a look-alike page is not captured and a saved password is not filled outside those domains.

05 · API status

A dashboard that knows what is behind the login.

Paste a read-only API token into an account and its Home card shows live status. The token field tells you which credential each service expects.

  • Project, app, repository or package counts and names for every built-in developer service except PyPI, whose tokens are upload-only.
  • Latest deploy state on Vercel; account name plus charges and payouts state on Stripe.
  • Tokens are validated before being stored, encrypted with DPAPI, revocable in one click, and never leave the main process.
  • Read-only endpoints only. The app never mutates anything through a service API.
STATUS CARD FIELDS
Project, site, app, repository or package count count + names
Latest deployment state Vercel
Stripe account state charges / payouts
Token scope read-only

These are the fields the app already reads through service APIs. No account data or token is shown on this site.

06 · Updates

Updates that get out of the way.

The app checks on startup and hourly against the public release feed. A newer release downloads in the background and installs silently, with no wizard, the next time you close it.

Found

The rail badge and Updates panel show the newest release and its notes.

Downloaded

The rail badge becomes Restart to update x.y.z. Press it to relaunch on the new version, or just close the app.

Installed

The update installs in place, without a wizard. Accounts, sessions and saved logins live outside the install and survive.

Prefer manual control? Turn Auto-update off in the Updates panel. Check, Download and Restart & update become explicit steps with release notes and progress. The interactive installer is only used for first installs.

07 · Ad-block & dark mode

Quieter pages, darker nights.

Both run inside each account's own session, so you do not install or maintain a single extension. Both are built around what Electron can actually support.

AD-BLOCKING

Driven by EasyList: roughly 52,000 blocked hosts plus generic cosmetic rules, refreshed weekly, applied per account partition.

  • Main-frame navigation and sign-in infrastructure are never blocked.
  • Generic rules are skipped on the dashboards the app manages.
  • uBlock Origin cannot run inside Electron, so this built-in blocker fills that role.
DARK MODE

Powered by Dark Reader's own engine, driven directly rather than installed as an extension. One toggle on Home applies to every account tab.

  • Instant — pages do not reload, so scroll position and half-typed forms survive.
  • Runs inside each tab's isolated world at roughly 2 MB per open account.
  • Works where Electron's extension APIs would not support the browser extension.

08 · Extensibility

If it has a login, it can have a rail row.

Add any service by URL

Any site gets its own rail row and fully isolated per-account sessions, exactly like a built-in service.

Service plugins

Drop a small JSON manifest into plugins/ — or install it from the UI — to define a service and, optionally, how to read its API for status cards.

Guided, never automated

Account creation is always manual and guided inside the account's session. Nothing signs up on your behalf, because automated signup violates several providers' acceptable-use policies.

09 · Provider terms

The app surfaces the rules instead of hiding them.

Multiple accounts are a technical capability, not a licence to ignore a provider's terms. The rail states the stance for each service.

Provider stanceWhat the app shows
One account per personGitHub and Railway: the rail says so. Use their organisations and workspaces instead.
Separate accounts tolerated, watch for abuseVercel, Netlify, Supabase, Cloudflare, Heroku and DigitalOcean.
Extra accounts treated as ordinaryThe registries, GitLab, Fly.io, Neon, Google, Microsoft and the mail providers.
One account per businessStripe expects one per business. The app does not change that.

Ready when you are

Every account. One window.

37 services built in, any other site by URL, and sessions that stay signed in.