Start here: JoyProxy Multi + Residential · Static

Multi-Account Desktop Solution

Run several desktop accounts on one PC without sharing an IP — each process gets its own static residential port. This is the Windows/macOS client plus upstream mapping.

Software: JoyProxy Multi. Upstream: static residential, one IP per account. Social/E-commerce pages explain why static; this page is how to bind it per EXE.

Get desktop clients Purchase static IPs
Who it's for

Operators with many logins on one workstation

Social operators

Several browsers, several IPs.

Seller ops on one PC

Store A vs store B processes.

QA

Parallel personas without VMs.

Power users

VMs are too heavy.

Pain Points

Client without static IPs still shares reputation

Installing Multi and pointing every process at the same rotating pack defeats the purpose. Buy static ports, then map them.

🔗

One PC, one IP

Platforms link accounts.

🖥️

VM sprawl

RAM and licenses.

🔄

Rotating on logins

Security emails.

⚙️

Manual proxy per window

Easy to mis-click.

📱

This will not isolate phones

Use Android client.

🏢

Ten staff laptops

Use a gateway, not Multi on each unsupervised PC.

What to buy

Multi client + static IPs

Recommended: JoyProxy Multi with one static residential IP per process. Alternative: proxy-server gateway if the whole office should share policy instead of per-PC maps.

Product Billing Use it when…
JoyProxy Multi Desktop Recommended Per-process desktop client Recommended — per-process mapping on the desktop client.
Residential · Static Per IP / period Required upstream pattern — one static IP per isolated account.
Recommended path

How to start (one recommended path)

Path A — Multi + static (recommended)

One EXE, one port.

  1. Install JoyProxy Multi.
  2. Buy one static residential IP per account.
  3. Bind chrome-profile-A to port A.
  4. Never launch two accounts on the same mapping.
Static proxies →

Path B — Team should not use per-PC maps

Centralize instead.

  1. If IT must control egress, deploy joyproxy-server.
  2. See Proxy Gateway.
  3. Multi remains for power users only.
  4. Do not mix both on the same login without a diagram.
Proxy gateway →
Decision guide

Pick one — do not mix these on the same job

Use Multi when

  • Same machine, many isolated apps.
  • You need process-level control.
  • VMs are overkill.

Use a gateway when

  • Many people, one policy.
  • Credentials must not live on laptops.
  • You want server logs.
Getting started

First-week checklist

FAQ

Common questions

Linux desktop?

Check releases — Windows/macOS are primary.

Same as Social solution?

Social is the IP policy. This is the desktop binder.

Games?

Only if the game honors system/process proxy — test.

Open source?

Yes.

Antidetect?

Complementary, not a replacement.

Resources

Go deeper

App isolation overview Social IP policy E-commerce IP policy GitHub

Map the next EXE to its own static IP

Install Multi, then lease static residential ports. Rotating is the wrong upstream for logins.

Get desktop clients Purchase static IPs