Questions,
answered plainly.

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.

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.

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.

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

Home → Import from browser reads installed Chromium browsers directly. Chrome 127 and newer lock some entries with app-bound encryption that no other app can read; export those to CSV from the browser and use Import CSV instead. Firefox always uses the CSV path. Re-importing updates passwords you have changed.

The installer is not code-signed yet, so Windows shows a warning the first time. Choose More info → Run anyway. Code signing is planned and removes the warning entirely.

Yes. Add service by URL gives any site its own rail row and isolated per-account sessions, and JSON plugin manifests can define a service plus how to read its API for status cards.

Nothing is lost. Accounts, sessions, saved logins and settings live in %APPDATA%\multi-acc-manager and survive updates and reinstalls. Updates install silently in place and relaunch the app.

Not for the app itself. The standalone Windows executable needs nothing else installed. Node.js 18+ is required only for the npx install and update route.

No. Nothing syncs anywhere: there is no server, no account and no telemetry. Accounts, sessions and saved logins stay on the one Windows machine where you sign in.

No. Chrome Web Store extensions cannot run inside Electron. The app ships built-in ad-blocking and Dark Reader's engine for dark mode instead.

The app is free to use, personally and commercially. It is source-available, not open source: the licence permits use, study and verbatim redistribution, but not modified or derivative distribution. See the licence for the full terms.

The app surfaces each provider's stance instead of hiding it. GitHub and Railway allow one account per person and the rail says so — use their organisations and workspaces instead. Other providers treat extra accounts as ordinary, tolerate separate accounts, or expect one per business. Account creation is always manual and guided; nothing is automated.