Account Manager

Store multiple accounts and launch the game with any of them, including multi instance launching, auto relaunch, groups, private servers, and live monitoring.

The Account Manager is a built in panel for storing multiple accounts and launching the game with any of them, without signing in by hand every time. Each account is added once by capturing its login session, which Ionize stores locally and encrypted. From there you can launch one or many accounts at once, point them at a specific place or private server, automatically restart crashed instances, watch each instance's live CPU, memory and connection status, and organize everything into groups.

Launching, browser login and live process stats are Windows only. Your accounts never leave your machine. See Storage and security.

Opening the Account Manager

Activity bar: click the Account Manager item (people icon) on the side rail.
Command palette: search for "Account Manager: Open" (Ctrl 6).
Keep it docked in the main window, or use Overlay to pop out a compact always on top monitor.

Adding accounts

There are three ways to add accounts. However you add them, Ionize fetches each account's identity (username and display name), confirms the session is valid, then encrypts and stores it. Accounts are de duplicated automatically, so re adding an existing one simply updates it. After importing, a summary reports how many accounts were imported, updated, and failed (with a reason for each failure).

Log in from a browser (recommended)

Click Login from Browser. Ionize opens Microsoft Edge or Google Chrome in a throwaway profile on the platform login page. Sign in as you normally would. Ionize detects the session automatically, imports the account, and closes the browser for you. (Requires Edge or Chrome installed.)

Paste sessions

Click the import button, paste one session token per line, and click Import. Handy for bulk adding accounts you already have.

Load from a file

In the same import dialog, pick one or more .txt / .csv / .log files. Their contents are merged into the paste box for review, then imported the same way. You can also save the Roblox account already signed in on this PC.

Launching

In Launch Settings, enter a Place ID and wait for the green validation pill (it shows the resolved game name, creator and live player count), or choose a private server.

Tick the account(s) you want in the list, then click Launch Selected. Ionize launches each selected account in turn, waiting the Launch delay (default 5s, range 0 to 120s) between each so clients do not all start at once. The connection line moves from Connecting to Connected as each client attaches, and live CPU and memory fill in.

Running more than one client at a time needs Ionize's Multi Instance setting enabled. If it is off, the panel prompts you with a shortcut to turn it on.

To relaunch a single account immediately (skipping the delay), use the circular arrow button on its row. To close running clients, select the accounts and click Stop.

Auto relaunch

Enable Auto relaunch closed instances in Launch Settings (or on a group) to have Ionize restart accounts after a client exits unexpectedly. The Launch Settings toggle also applies to accounts in scope and is OR'd with each account's own Auto relaunch checkbox. A background monitor watches the tracked processes and, after the Relaunch delay (default 5s, range 5 to 300s), relaunches the account; the row shows a live "Relaunching in Ns" countdown. A crash loop cap stops retrying after three quick failures.

When you turn this on, Ionize suggests enabling Silent Errors so crash dialogs do not block the relaunch.

Groups

Groups let you run different sets of accounts with different settings. Each group carries its own full launch configuration (place ID, delays, auto relaunch, private server mode), so one group can target one place while another targets a different one. Accounts store the group id (pick it from the Group dropdown in the editor); the list shows group names.

Add group, rename, or remove from the Launch Settings group dropdown.
Assign accounts with the Group dropdown in the account editor.
The accounts list is split into sections per group (plus an Ungrouped section) with counts.

Private servers

Open the mode selector in Launch Settings:

None: launch straight into the place ID.
Round robin: spread launched accounts across a pool of private servers.
Assigned: each account uses the private server assigned to it.

Add servers under Advanced Private Servers: give each a name, place ID, and a private link or code. Ionize resolves the link to the place at launch time and caches the result.

Health checks

Click Check Health (or run it on a selection) to test whether each stored session is still valid. Every account shows an alive, dead, or unknown badge, along with when it was last checked.

Monitoring

Header summary: totals for accounts, connected, connecting, relaunching, total memory, total CPU, and alive/dead counts.
Per row: session health, connection state (Idle / Connecting / Connected / Relaunching), committed memory, CPU, assigned private server, and last launch time.
Performance overlay: click Overlay for a small always on top window that refreshes every few seconds with connected/total, process count, memory, CPU and a per account list. Opening it hibernates the main window to save resources.
Recent Activity: a live, timestamped log of launches, connections, closes, relaunches, imports and errors.

Launch settings, groups and private servers autosave a couple of seconds after you change them (and before every launch); per account edits save immediately.

Account data

Each account stores:

Username / Display name: pulled from the platform when the account is added
Alias: your own nickname for the account (shown first when set)
Group: which group the account belongs to
Notes: free text notes
Session status: alive / dead / unknown, from the last health check
Auto relaunch: whether this account is included in auto relaunch
Assigned private server: used in Assigned mode
Last checked / Last launched: timestamps
Live usage: PID, committed memory, CPU and connection state while running

The login session itself is stored encrypted and is never shown in the interface.

Storage and security

Local only. Accounts, sessions, settings, groups and private servers live in the Windows Credential Manager under a single Ionize vault key. Nothing about your accounts is sent to Ionize servers. The only network calls go directly to the platform (to fetch identity, auth tickets and resolve places) and to your local browser during browser login.

Encrypted at rest. On Windows, sessions are encrypted with the operating system's data protection API and Credential Manager, tied to your Windows user, so the vault cannot be read on another machine or account. The decrypted session never reaches the interface.

Windows only actions. Launching, browser login, stopping/tracking clients and live CPU all require Windows.

Multi Instance. Running multiple clients depends on Ionize's Multi Instance setting being enabled. See Interface for the rest of the workspace.

Quick start

Open the Account Manager and click Login from Browser, then sign in. The account imports automatically.
Enter a Place ID in Launch Settings and wait for the green pill.
Tick the account and click Launch Selected.
To run several at once, enable Multi Instance when prompted, set a Launch delay, turn on Auto relaunch, then select all and launch.