Manage Multiple Vercel Accounts Without Logging Out

The way to manage multiple Vercel accounts, and Netlify, Cloudflare, Supabase or Gmail accounts too, is to keep each account in its own isolated browser session. A browser profile, a container tab or a dedicated multi-account app all do this, so you switch between accounts without logging out. Where a provider offers teams or organisations, use those first, and follow each provider's terms either way.

Why does switching accounts keep logging you out?

A website recognises you by cookies. Your browser keeps one set of cookies per site and profile, so signing in to a second Vercel account in the same profile replaces the first session. Some services solve part of this inside their own product. Vercel and Netlify let one login belong to several teams and give you a team switcher, and Google lets you add several accounts to one browser. Those switchers only help when the accounts hang off the same login or the same browser. A personal Vercel account and a client's Vercel account that use different logins still replace each other's session.

What are your options for using many accounts at once?

There are six realistic routes. Most people mix two or three of them.

Browser profiles

Each Chrome profile keeps its own bookmarks, history, passwords and settings, and its own signed-in sessions. Create one profile per identity and every account stays signed in. The price is one window per profile and the habit of checking which window you are in. Chrome's help page explains how to add a profile.

Container tabs

The Firefox extension Multi-Account Containers separates cookies by container, so one window can hold the same site under several identities in colour-coded tabs. It is the lightest option if you already use Firefox. Cookies are the boundary, so keep your own system for which password belongs to which container.

Separate browsers and private windows

Chrome for one account and Firefox for another works. A private window gives a clean session that is thrown away on close, so every return means a full login with a two-factor code. That suits a one-off task and wears you down as a daily routine.

Teams and organisations

Vercel, Netlify, Cloudflare and Supabase let one login join several teams, accounts or organisations, each with roles. Vercel's account documentation describes a team switcher in the dashboard, and Netlify's says a user can be a member of several teams and change between them from a menu. When a client invites you into their team, you often do not need a second account at all. Check which plan the provider requires for extra members.

A dedicated multi-account app

A desktop app can apply the container idea to accounts, with one isolated session per account in a single window and every account kept signed in. Danube Labs built My Provider Dash Manager for this. The details are further down.

How do the options compare?

What should you check for security?

Session isolation

Cookies, localStorage, IndexedDB and cache must be separate for every account. Profiles do that, and so does a per-account partition. In Electron, session.fromPartition() with a name that starts with persist: returns a persistent session shared by every page that uses the same partition name. An app that gives each account its own partition name therefore gets separate storage per account, and the sessions survive a restart.

Credential storage

Find out where saved logins live. Electron's safeStorage uses DPAPI on Windows, and the documentation says the content is protected from other users on the same machine, but not from other apps running in the same userspace. That covers another user and a stolen disk. Malware running as you can still read what you can read, so keep the device patched and do not treat any desktop password store as a vault against it.

Phishing-resistant domain matching

A look-alike login page is the realistic attack on admin dashboards. Autofill should be tied to the service's real domains, so a password is never filled on a page outside them. Passkeys work the same way by design. Browsers and operating systems enforce that a passkey is only used for the service it was created for. Vercel supports passkeys, so turn them on wherever a provider offers them.

Read-only API tokens

A status view rarely needs write access. Cloudflare API tokens come in permission groups that usually offer Read or Edit, can be scoped to specific zones or accounts, and accept an IP filter and a time to live. GitHub recommends fine-grained personal access tokens over classic ones. Give each tool the minimum, set an expiry and revoke the token when the job ends. Not every provider offers read-only scopes, so check before you rely on them.

Which provider rules apply to multiple accounts?

Technical isolation does not change a contract. Section B.3 of GitHub's Terms of Service says one person or legal entity may maintain no more than one free account, and that a machine account is allowed if it is only used for running a machine. For client work on GitHub, use organisations. Other providers have their own acceptable-use rules, and some watch for multi-accounting. Read the current terms of each service before you create a second account, never share a login between people, never automate sign-up, and never use extra accounts to get around quotas or plan limits. If a client owns the infrastructure, ask them to invite you.

How does My Provider Dash Manager handle multiple accounts?

It is a Windows desktop app built on Electron. Each account runs in its own persistent Chromium partition, named persist:<service>__<account>, inside its own view, so cookies, storage and cache never mix and sessions survive restarts. Thirty-seven services are built in, among them Vercel, Netlify, Cloudflare, Supabase, GitHub, npm, Stripe, Gmail, Outlook and Proton Mail, and you can add any site by URL.

• Warm-tab limit. A live dashboard costs roughly 125 MB, so the app keeps five warm by default and sleeps the rest. Sleeping tabs stay in the strip and wake on click. The README reports measured private memory of about 1.0 GB for 5 live tabs, 1.6 GB for 10 and 0.35 GB with all of them asleep.
• Saved logins. Encrypted with Windows DPAPI and bound to the account and to the service's own domains. A saved password is never filled outside those domains, and a password typed on another site reached from that tab, such as an OAuth hand-off or a look-alike page, is not captured.
• Read-only tokens. Optional. A token shows project counts or the latest Vercel deploy state on the account card without opening the dashboard. Tokens are validated before storage, encrypted, and revocable in one click.
• Local-first. No telemetry, no account, no server. Account pages run sandboxed, with context isolation and deny-by-default permissions.
• Provider notes. The app shows each provider's stance, for example that GitHub allows one personal account per person, and it never automates account creation.

How to set it up

1. Install Node.js 18 or newer, then run npx my-provider-dash-manager. It downloads the newest installer from GitHub, checks that it is a real Windows executable, runs it and launches the app.
2. The installer is not code-signed yet, so SmartScreen shows a warning on first run. Choose More info, then Run anyway, only if you are comfortable with that. The repository is public if you want to inspect it first.
3. Click Add account, pick the service, name the account (for example client-acme) and sign in normally. Where a site offers Continue with Google, use email and password instead, because Google blocks that flow inside embedded browsers.
4. Switch by clicking a tab or a row in the left rail. Ctrl+W puts a tab to sleep and Ctrl+Tab cycles through open ones.

The limits are plain. It runs on Windows only. The licence is source-available, free for personal and commercial use, and it does not allow redistributing modified versions, so it is not open source. DPAPI does not stop malware running as you.

What does a safe multi-account workflow look like?

1. Ask clients to invite you to their Vercel team, Netlify team, Cloudflare account or Supabase organisation instead of sending a password.
2. Keep your own accounts in separate sessions from client accounts.
3. Turn on two-factor authentication or a passkey on every account.
4. Give tools read-only or fine-grained tokens with an expiry date.
5. Name each account by owner and purpose so you can tell sessions apart at a glance.
6. When a contract ends, leave the team and revoke the tokens.

Need a tool like this for your own workflow?

Danube Labs is a founder-led software, AI and automation studio in Bucharest. My Provider Dash Manager is one of its products, and the same approach applies to internal dashboards and desktop tools built around how you work. See custom software for what that involves, browse all work, or book a free intro call.