Profile manager for the Afina antidetect browser

Every account is an isolated browser profile with its own fingerprint, proxy, cookies and per-account variables. Manage hundreds with tags, groups and bulk actions — and stay inside one antidetect browser.

Profiles • Tags • Custom data

One workspace for every account you run

Browser profiles in Afina are first-class objects: each one carries its own fingerprint, network stack, storage and per-account variables. Open one, run scripts on it, share it with teammates — without polluting any other profile.

Isolated profiles

Each profile is a separate browser environment with its own fingerprint, proxy, cookies and storage. Nothing leaks between accounts, even when you run them in parallel.

Per-account variables

Store key/value data on every profile — plain or encrypted. Use them inside RPA scripts as ${variable}, share between runs, or keep secrets in a sealed vault.

Bulk actions

Select dozens of profiles at once and start, stop, tag, group or run a script across the whole selection. The same primitives power multi-accounting at scale.

Tags, groups and filters

Organize profiles by use case, client or campaign. Group access is what powers teamwork — give teammates only the profiles they need.

FAQs

Have questions? We're here to help.

Online Support Available

Telegram Discord

An Afina profile is an isolated browser environment — its own fingerprint, proxy, cookies, storage, history and per-account variables. Profiles do not share anything by default, so running ten of them in parallel is the same as running ten different physical devices.

Hundreds. The desktop app handles bulk operations on large selections, and the local API can drive thousands programmatically. Practical limits come from your machine's RAM and CPU, not from Afina.

Two key-value stores attached to each profile: plain settings (in account.settings) and an encrypted blob (account_data_blob). They're available inside RPA scripts as ${variable} substitutions — perfect for passwords, seed phrases, per-account configuration.

Yes. Tags are free-form labels for fast filtering; account groups are containers used for bulk actions, scheduled task batches and team-access rules. A profile can carry multiple tags and belong to multiple groups.

Yes — bulk start, stop, run-script, run-task-group, hard-delete and tag/group changes accept multi-selections. The same primitives power the multi-accounting workflow described on the dedicated page.

Profiles are stored on your device and synced to the Afina cloud only when you choose. Team licenses share profiles across seats via account groups and team UUIDs; solo licenses keep everything local to your install.

Manage every account from one place

Spin up isolated profiles, tag them, fill them with custom data and run automations on them — without ever leaving the browser.

The Afina profile manager turns every account into a first-class browser profile with its own fingerprint, proxy, cookies, storage and per-account variables. Run hundreds in parallel without anything leaking between them, organise with tags and groups, share via the team workspace.

Browser extensions and incognito windows share the host browser's stack: same WebGL renderer, same fonts, same TLS fingerprint. Platforms link accounts through those shared signals. Afina profiles are full standalone Chromium environments — separate cookies jar, separate IndexedDB, separate cache, separate fingerprint — so a hundred accounts read as a hundred real machines.

What's inside the profile manager

1. Fully isolated profiles

Each profile is a separate browser environment: own fingerprint, proxy, cookies, localStorage, IndexedDB, service workers, cache and history. Nothing leaks between accounts even when you run dozens in parallel — anti-fraud has no shared signal to correlate on.

2. Per-account variables and sealed vault

Two key-value stores on every profile: plain account.settings for configuration and an encrypted account_data_blob for secrets. Both are usable inside RPA scripts as ${variable} substitutions — perfect for passwords, seed phrases, 2FA seeds, per-account configuration.

3. Bulk actions across selections

Select dozens of profiles at once and start, stop, tag, group, run a script or schedule a task across the whole batch. The same primitives that power multi-accounting at scale and team-driven workflows.

4. Tags, groups and filters

Tags are free-form labels for instant filtering; groups are containers used for bulk actions, task scheduling and team-access rules. A profile can carry multiple tags and belong to multiple groups — onboarding a teammate is one tag change.

5. Local-first, cloud-optional

Profiles live on your device by default. Opt in to sync per profile or per group through Afina cloud or your own Google Drive — that's how teams and your other machines pick the same profiles up.

Where teams use the profile manager

Affiliate, SMM and SEO teams warm and scale account portfolios from a single workspace. Airdrop farms hold wallets in sealed vault per profile. Agencies serve clients with isolated profile groups — each client lives in its own slice. QA and security research teams reproduce flaky flows against fingerprinted profiles instead of brittle headless Chromium. Everything runs locally; nothing crosses between profiles unless you wire it explicitly.