Multi-Accounting for Freelance Platforms: Agencies & Clients

GetAntik editorial team · October 3, 2026 · 11 min read

How agencies manage dozens of client accounts on Upwork, Fiverr and Toptal with isolated browser profiles — without breaking platform rules.

Why one browser is a problem on freelance platforms

An agency working across freelance platforms almost never runs a single account. There's the agency's own profile on Upwork, access to accounts belonging to five or ten clients who hired you to recruit contractors, personal accounts for your specialists on Fiverr and Toptal that they use to bid on jobs. Add test accounts for exploring new niches and portfolio accounts, and you end up with 20–40 logins that can't physically be spread across separate computers.

If all of this gets opened in one browser through incognito tabs, the platform sees the same device fingerprint, the same IP, and overlapping cookies between tabs. For Upwork and Fiverr, that's one of the signals of linked accounts — these platforms explicitly forbid multiple accounts belonging to one person operating in parallel without official agency status, and suspicious activity from a single device is a common trigger for review or suspension.

An antidetect browser solves this differently: each account gets its own isolated profile with separate cookies, its own managed fingerprint (OS, browser version, screen, fonts, WebGL) and its own proxy. To the platform, it looks like different people on different devices — because that's actually how the team is managing it.

What's legitimate and what isn't

It's worth separating two scenarios up front, because platform rules differ for each.

Legitimate:

• An agency runs its own profile on Upwork under the official Agency status — this lets you add specialists to a team through the platform's built-in functionality. That's an approved model, not a workaround.
• A client gives the agency access to their existing account (Upwork Client, Fiverr Buyer) so the agency can hire and manage contractors on their behalf. The account belongs to the client; the agency is simply operating it by delegation.
• A specialist runs one personal freelancer account, and the agency sets up a separate isolated browser profile for them — not to deceive the platform, but to keep their working environment from overlapping with other client sessions and to avoid mixing in someone else's cookies.
• Test or portfolio accounts that the platform explicitly allows creating (for example, a separate account for a different specialization, where the specific marketplace's rules permit it).

Not legitimate, and not worth doing:

• Creating several fake freelancer profiles as one person in order to bid on the same project multiple times or game the rating system.
• Getting around a ban on a specific account by creating a new profile with the same data — if a platform closed access for a violation, that's a deliberate platform decision, and antidetect tools aren't meant to circumvent it.
• Selling access to someone else's verified account, or operating under someone else's name without their knowledge.

GetAntik is a tool for organizing legitimate parallel access, not for disguising yourself as different people where a platform requires one real person per account.

How it works in practice: three layers of separation

1. One profile per account, not per client

A common mistake is setting up one profile "per client" and logging into Upwork, then Fiverr, then a notification inbox, all within it. That mixes sessions and fingerprints across different services for the same client, even though those services aren't formally linked. The better rule: one isolated profile equals one login on one platform. If a client has both an Upwork account and a Fiverr account, that's two profiles, even if the proxy and timezone are identical.

At 30–40 accounts, a list like this turns into chaos fast without structure — groups by client, proxy status, who on the team is currently in which profile. The approach to organizing a large pool of profiles is covered in how to organize hundreds of profiles without drowning in chaos — the grouping and tagging logic there fits particularly well with a "client → platform → profile" structure.

2. Proxies matched to the account's geo, not the agency's office

Freelance platforms cross-check browser timezone, interface language, and IP geolocation against the country declared in the account profile. If a client's Upwork account is registered to the UK but you open it through a proxy in Southeast Asia, the platform will notice the mismatch and may request additional verification or temporarily restrict features — bidding, withdrawals, posting projects.

The rule is simple: the proxy is matched to the account's country of registration, not the agency's office location. For client accounts spread across different countries, you need a pool of residential or mobile proxies by geo, with the ability to quickly confirm the IP isn't blacklisted and actually resolves to the right country.

Different proxy types suit different tasks — a static client account that needs to look stable for months needs one approach, a one-off test profile needs another. This is covered in detail in proxy types for multi-accounting: how to choose the right one. GetAntik includes a proxy manager with checks and integration with HollyProxy, so you don't have to switch between services for purchasing and rotating IPs.

3. Cookies and warm-up — separate for each account

A new Upwork or Toptal account that immediately starts actively bidding on projects raises more suspicion than one that first browses profiles, fills out a portfolio, and spends a week behaving like a normal viewer. The same applies to client accounts — if an agency gets access to a long-existing but recently inactive client account, a sudden spike in activity from a new device also looks atypical.

Cookie import and export in JSON and Netscape formats let you carry an existing client session into an isolated profile without logging in again from a new device — reducing the number of "suspicious sign-ins" that might otherwise trigger extra verification. Manual and scheduled cookie warm-up helps new profiles accumulate history before real work activity starts on them.

Table: what to check on major platforms

Before rolling this scheme out to a new platform, read its current rules on multi-accounting and agency programs — they change more often than you'd expect, and what was permitted six months ago may now carry restrictions.

Team access: who can touch which accounts

For an agency running dozens of client accounts, the question isn't "how do we stay hidden" — it's "who's responsible for Client X's account today, and what are they allowed to do in it." A project manager shouldn't have access to a client's withdrawal settings, a content specialist shouldn't touch financial settings, and a new intern shouldn't have access to all 40 profiles at once.

A role model with per-member profile limits and distinct permissions for owner, admin, member and finance solves exactly this: everyone sees only their own pool of profiles, financial operations go through a dedicated role, and handing a profile off between teammates when a project changes or someone leaves happens inside the system, without passwords getting forwarded over chat. More on how roles and limits work in team collaboration with profiles: roles, limits and handoff.

Live view and remote control of a teammate's browser is also useful here — a project lead can check in on how a junior specialist is handling a negotiation in a client's Upwork chat, without asking for the password or opening the account in parallel from their own device.

Access security: 2FA and encryption

Access to client accounts on freelance platforms is access to a client's money — payment methods, payout history to freelancers, sometimes banking details are stored there. Losing that access or having it leak isn't an abstract risk; it's direct financial damage to the client and the agency's reputation.

A per-profile 2FA key vault solves a common problem: the two-factor code for a client account sits in an app on the phone of whichever employee set it up, and that person is on vacation exactly when access is urgently needed. If the key is tied to the profile instead of a person's personal device, any team member with the right permissions can retrieve the code without waiting for a colleague.

Profile data is encrypted on the device with the account password — the server has no access to the contents, meaning even if the server side were compromised, client account cookies, passwords and keys stay protected. This matters particularly for agencies: you're effectively storing someone else's credentials, and the responsibility for protecting them is yours, not just the platform's. This is covered in more depth in profile security: encryption, 2FA vault and access recovery.

Common mistakes when switching to isolated profiles

Using one proxy for all clients to save money. Residential proxies cost money, and the temptation to route three clients through one IP is real. But if two different clients' accounts end up on the same IP, it doesn't go unnoticed by the platform — especially when both accounts operate in the same niche and the platform sees matching behavior patterns.

Mixing a specialist's personal profile with a client profile. A freelancer logs into their personal Upwork account and a client project from the same browser profile "to avoid cluttering tabs." If reviewed, the platform will see a connection between the freelancer's personal activity and actions taken on the agency's behalf — potentially damaging both accounts.

Passing passwords through chat when staff change. A classic scenario: a specialist leaves, but the password for a client's Fiverr account stays in their phone notes because it was just dictated out loud over a call. The right process is handing the profile off through the system's built-in function, which automatically cuts access for the former employee and logs who last accessed it and when.

Skipping warm-up for "temporary" accounts. Even if a client account is only needed for a three-week project, a burst of activity from a new device without history still reads as an anomaly to the platform — especially if the account had been quiet for months before.

When you don't need an antidetect browser

If an agency works with one or two clients and three or four accounts, splitting them into isolated profiles with separate proxies may be overkill — plain separate browser windows and careful password storage in a manager will do. The antidetect approach pays off once you're counting accounts in the dozens, several people work in parallel, and the cost of a mistake — a temporary suspension of a client account with money inside — outweighs the cost of the tool.

You can start with the free plan for 3 profiles to test the separation logic on real client cases before moving the whole account pool to isolated profiles. Paid plans starting at $5/month for 20 profiles cover a small team's needs, and the pricing plans with roles and per-member limits fit once several people in the agency are already handling different clients in parallel.

FAQ

Can one specialist run two personal accounts on the same platform through different profiles? If the platform's rules allow it (for example, separate accounts for different specializations), it's technically easy to set up through isolated profiles. But before creating a second account, check the platform's current policy — many explicitly forbid one person from holding multiple personal freelancer accounts at once.

Do you need an antidetect setup if the agency is officially registered as an Upwork Agency? Yes — agency status resolves the question of structural legality, but not the technical question of isolating sessions between specialists and client projects. Even a fully legitimate agency model works more reliably when every specialist and every client access point has its own browser profile instead of a shared tab.

What if a client changes their account password and forgets to tell the agency? This is a standard situation when managing someone else's accounts, and it's independent of the tool — you need a communication protocol with clients around access changes. An antidetect browser helps indirectly: if the session is preserved through up-to-date cookies, you need to re-log in less often.

How do you quickly cut access for a former employee across all client accounts at once? Through the role system and revoking access at the team account level — all profiles assigned to that employee stop being accessible in one action, without manually changing passwords in every client dashboard. The offboarding process is covered in detail in offboarding an employee: how to cut access without losing accounts.

How many profiles does a mid-sized agency actually need? Work from this formula: one profile per active login (client account + specialist's personal account + test profiles), not per client. An agency with 10 clients and 5 in-house specialists typically lands at 25–40 profiles within the first month of work.

freelance platformsmulti-accountingagency managementantidetect browseraccount security