Running a fleet without it running you

Decide the roles before you add anything

The single highest-leverage decision is what each account is for, made before you import it. Most working operations sort into three roles:

• Farms — disposable, gather constantly, exist to feed something else. Losing one costs a week.
• Banks — hold and forward resources. Fewer, more valuable, lower profile.
• Mains — what the whole operation exists to serve. Most experienced operators never automate these at all; see the ban-risk guide.

Tag on import, not later. Retagging forty accounts after the fact is the kind of chore that never gets done, and every fleet-wide view is worthless until it is.

Proxies: when they earn their cost

Proxies are the most over-prescribed item in this hobby. Reasoning, not measurement:

1. A handful of accounts: probably unnecessary. Normal households have several players on one connection.
2. Dozens on one connection: worth considering, since the pattern stops resembling anything a household produces.
3. Accounts you cannot afford to lose together: the real argument for separation is blast radius, not detection.

Apex takes a SOCKS proxy per account, so you can separate selectively rather than paying for the whole fleet.

What actually limits fleet size

Not the software. In order of what people hit first:

• Memory. The usual ceiling. Budget generously and check real usage at your account count before scaling.
• Upstream bandwidth, if every account is proxied through one connection.
• Your own attention. The one nobody plans for. Past roughly twenty accounts, manual checking stops working — which is the entire reason Apex flags accounts rather than expecting you to go looking.

The operating routine that works

Once tagging and recovery are in place, the daily job collapses to three things:

1. Glance at fleet-wide resource totals. If last night looks like the night before, nothing needs you.
2. Look at anything flagged. Apex gives up after three restart attempts precisely so a genuinely broken account surfaces instead of looping quietly.
3. After a game update, expect breakage and check early. Every bot breaks on update day; what differs is how fast you notice.

If the fleet is a business

Operators renting accounts to other people hit a different wall: every settings change becomes a support request. That is what the client portal on the Operation tier is for — your customers adjust their own whitelisted settings and Apex applies them without a restart. Pricing is here.