Reddit Profile Fleet Guide — 100–200 Accounts at Scale (Extended Edition)

Goal: Operate a fleet of 100–200 aged, karma-positive Reddit accounts for GrowReach — AI comment testing, comment seeding, and AI citation building (GEO/AEO). Companion to: reddit-karma-7day-guide.md (single-account 7-day plan — unchanged, still the per-account playbook). This guide is the fleet layer: infrastructure, pipeline, rotation, isolation, monitoring, and rollout at 5–10x the current scale. Current state (fetched live 2026-08-10 from r.10xers.co/api/metrics): 18 profiles, 17 active, 0 suspended, 1,066 total karma, 36 comments today. Profiles span AEST/EDT/BST/PDT timezones, ages up to 151 days. This guide scales that to 100–200. Status: v1.0 — August 2026.

0. Read This First — The One-Paragraph Truth

Reddit explicitly allows multiple accounts — even with the same email. The user agreement permits it, and Reddit’s own help center documents it. What gets fleets killed is not having 200 accounts; it is behaving like one entity: coordinated voting (vote manipulation), re-entering banned communities (ban evasion), and repetitive self-promotion or AI-assisted mass posting (spam). Every design decision in this guide exists to keep the fleet on the legal side of that line: many independent humans, not one botnet. If a tactic in this guide ever feels like it crosses into “making one entity look like many,” stop and re-read Section 2.

1. Fleet Rationale & Use Cases

Why 100–200 accounts?

Use case	Why fleet scale matters	Minimum viable fleet
GrowReach AI comment testing	Test comment prompts (V1/V4) against real Reddit filters, CQS gates, and subreddit cultures without burning the main account. Each account = one test subject with its own history.	10–20
Comment seeding	Legitimate value-first comments from different personas in the same thread read as community consensus, not one founder shilling. AI engines (ChatGPT/Perplexity) weight multi-voice agreement heavily.	30–50
AI citation building (GEO/AEO)	200+ comments/month across many subreddits is the threshold where LLMs start treating a brand as “discussed.” 5 comments/month is noise AI washes out. Fleet = volume without any single account looking spammy.	50–100
Karma runway	Aged accounts with 100–500 karma unlock r/SaaS, r/Entrepreneur, r/startups. A fleet lets you rotate which accounts carry GrowReach mentions, keeping the 9:1 ratio per account.	20+
Resilience	Bans happen (even Gojiberry’s founder was banned 3–4x). A fleet absorbs losses; a single account is a single point of failure.	30+
Timezone coverage	Accounts native to AEST/EDT/BST/PDT let you engage US peak hours (2–6 PM GMT+4) with accounts whose timezone matches their proxy — a strong anti-detection signal.	4+ per timezone

What the fleet is NOT for

NOT for vote manipulation — no coordinated upvoting of GrowReach posts across accounts. This is the #1 sitewide-suspension trigger and the fastest way to lose the entire fleet. (See Section 2 and the compliance matrix.)
NOT for ban evasion — an account banned from a sub must never re-enter it via another fleet account. Community Mute exists for this.
NOT for spam — no mass-posting the same link, no AI-generated comment floods, no DM promotion.

2. ToS / Risk Reality (Know the Exact Lines)

What is explicitly ALLOWED

Item	Source / detail
Multiple accounts	Reddit user agreement + help center: allowed, even with the same email. People theme accounts (casual/professional/NSFW).
Each account stands alone	Own age, own karma, own CQS. No cross-account inheritance of reputation.
Aged accounts with real history	Building karma genuinely on NUFS subs is the officially endorsed path (r/NewToReddit wiki).
Community Mute	Using it to keep one account from seeing a sub another account is banned from — explicitly fine.
Deleting your own content	Profile curation is a documented feature; deleting posts/comments after conversations run their course is a real strategy.

What is EXPLICITLY FORBIDDEN (sitewide suspension, no appeal path worth betting on)

Violation	Definition	Fleet consequence
Vote manipulation	Voting on the same content from multiple accounts; organized voting; hinting at votes (“upvote if you agree”); self-upvote rings.	All accounts involved get suspended. Reddit’s detection is network + fingerprint + timing based.
Ban evasion	Being banned from a community, then using another account to continue participating there.	Sitewide suspension of the new account; admins investigate account clusters.
Spam	Repetitive self-promotion; posting the same link across subs; using tools (bots, generative AI) that facilitate mass spam (spam policy, updated May 2026).	Content removal → account suspension → fleet-wide scrutiny.
Buying accounts	Purchased accounts are the end product of karma farms; Reddit suspends them and treats clusters as ban evasion.	Never buy. Every account is created and warmed in-house.
Free-karma subs	r/FreeKarma4U etc. — associated with bad-faith users; major subs auto-ban anyone who posted there.	One account touching these can poison the fleet’s IP/proxy reputation.
Paying “fixers”	Anyone claiming they can fix a suspended/shadowbanned account is a scammer. Only admins can.	No recovery path — prevention is the only strategy.

The risk ladder (how enforcement actually escalates)

Content removal (sub-level) — mods remove a comment/post. No fleet impact.
Sub ban (mod-level) — banned from one community. Fleet impact: that account must never touch that sub again (Community Mute it).
Shadowban (admin-level, invisible) — profile invisible to others; account still “works.” Detect via reddit.com/appeals. Fleet impact: quarantine the account, stop all activity, appeal once.
Sitewide suspension (admin-level) — account gone. Fleet impact: if triggered by vote manipulation/ban evasion, admins may investigate linked accounts (same IP history, same fingerprint patterns, same email domain). This is the only level that threatens the fleet itself.

Fleet rule: the goal is to never let any account reach level 3–4, and to make level 4 non-contagious by construction (Section 6 isolation).

3. Infrastructure

3.1 AdsPower — the profile farm backbone

Each AdsPower profile = one Reddit account, isolated by fingerprint + proxy + cookie jar. Four integration layers (from adspower-kb/00-master-kb.md):

Layer	Role	Used for
Local REST API (`:50325`)	Profile lifecycle, groups, tags, proxies	Foundation — rarely called directly
`ads` CLI / skill	Shell wrapper over the API	Profile farm CRUD — create, proxy, fingerprint, launch, close, audit. Primary agent interface
MCP Server (Playwright)	In-browser automation	Engagement engine — navigate, upvote, comment, screenshot
RPA (GUI process builder)	Fixed workflows across many profiles	Bulk volume lever — 100+ profile runs of a codified workflow (human imports the process definition)

Architecture (current): Hermes on Linux VPS (89.117.36.36) + AdsPower on Windows host. CLI/MCP on the VPS hit the remote Local API via --port/--api-key or env vars (ADS_API_KEY). MCP server spawns via npx -y local-api-mcp-typescript, connects over WebSocket.

Scaling rule: CLI manages profiles, MCP drives engagement, RPA scales volume. At 100–200 profiles, batch operations (create 10, rotate fingerprints, clear cookies) go through the CLI; per-account engagement goes through MCP; fixed mechanical workflows (open → navigate → upvote → screenshot) can be RPA process definitions.

3.2 Decodo residential proxies

One proxy per profile is the gold standard. At 100–200 profiles that’s 100–200 residential IPs — expensive but the only configuration that makes cross-account correlation impossible.
Acceptable fallback: low-sharing proxies — max 3 profiles per IP, and those 3 must be in the same country + timezone (a US-EDT proxy on a UK-profile is a fingerprint mismatch that screams automation).
Country/timezone matching is non-negotiable: profile timezone, proxy country, and account persona location must all agree. Current fleet already spans AEST/EDT/BST/PDT — keep that pattern.
Rotation via update_browser: the Local API’s update_browser endpoint swaps a profile’s proxy. The dashboard’s proxy-IP management plan enforces safety checks before any replacement: same country, same timezone, sharing limit (never 3+ profiles on one proxy), approval gate, dry-run mode, rollback (old proxy ID logged).
Dead-proxy handling: when a proxy dies, replace it with one matching country + timezone, then verify the account still logs in cleanly (a flagged IP will trigger Reddit’s “verify you’re human” or login challenges).
Never reuse a proxy that was used by a suspended account — IP reputation is sticky.

3.3 Email provisioning

Email is the fleet’s biggest operational bottleneck. Every account needs a unique, verifiable email (email verification raises CQS — it’s a real gate).

Option	Verdict	Notes
Gmail per account	✅ Best	Most reliable for Reddit verification; needs unique phone for bulk signup (see below); 2FA per account
Outlook / Microsoft	✅ Good	Less phone-verification pressure than Gmail at scale; unique passwords + 2FA
ProtonMail	⚠️ Mixed	Privacy-friendly but Reddit sometimes flags proton domains in bulk; fine for small batches
Custom-domain catch-all	❌ Risky	Disposable-domain signals; if one account is flagged, the whole domain’s accounts look related
Aliases (+tag) of one inbox	❌ Risky	Reddit correlates; also a single compromised inbox = fleet-wide credential exposure

Provisioning pipeline (per account):

Create email with a persona-derived name (see Section 5) — firstname.lastname+random style, never growreach001.
Unique strong password per account (password manager or vault file — never shared).
Enable 2FA where the provider allows (Gmail/Outlook both do).
Phone verification: Gmail bulk signup will demand phone numbers. Options: (a) one phone per ~5–10 accounts with staggered signup (Google tolerates this at low volume), (b) a small pool of prepaid SIMs, (c) SMS-verification services — use with extreme caution, Google and Reddit both fingerprint known VoIP/SMS-service number ranges. Prefer real numbers, staggered over weeks.
Store credentials in the AdsPower profile’s built-in password manager (per-profile isolation) AND in the fleet vault (encrypted, offline).

Pacing rule: never create more than 5–10 emails per day from one IP/device. Email providers and Reddit both watch signup velocity.

4. Account Creation Pipeline at Scale

4.1 Batch design (100–200 accounts)

Batch	Size	Purpose	Timeline
Pilot	10	Validate the whole pipeline (email → proxy → AdsPower → Reddit → warmup)	Days 1–15
Wave 1	20	First scale test; 2 per timezone cluster	Days 16–30
Wave 2	30	Steady state; 3 per timezone cluster	Days 31–60
Wave 3	40–140	Full scale; only after Waves 1–2 show <5% ban rate	Days 61–90

Hard cap: 5–10 new accounts per day, fleet-wide. This is the single most important pacing number in this guide. Reddit’s new-account filters and CQS scoring are most aggressive in the first days; a burst of 20 signups from one proxy range is a pattern, not a coincidence.

4.2 Per-account creation checklist (one profile = one account)

Complete the signup in one sitting, then close the browser. No marathon first session.
Browse like a new user: search a few topics, open posts, read, vote.
Do not join 50 subs on day 1. 5–8, matching the persona.
Do not set a corporate avatar, brand username, or bio mentioning GrowReach. Fleet accounts are civilians until they’re aged and trusted — and even then, only a small subset ever mentions the brand (Section 8).
Stagger signups across the day and across timezone windows — don’t create 5 accounts at 2 PM GMT+4 from the same proxy cluster.

5. Warmup Protocol with Per-Account Personas

5.1 Why personas matter at fleet scale

A fleet of 200 accounts that all comment like the same person is a fleet of 200 accounts that all get flagged. Personas give each account: a consistent voice, a consistent subreddit diet, a consistent posting schedule — the three signals Reddit’s systems and human mods use to judge “is this a person?“

5.2 Persona template (fill per account)

Field	Example	Rule
Name	”Marcus”	Never brand-derived
Age / life stage	29, software dev	Drives sub choices and comment voice
Location	Austin, TX (US-Central)	Must match proxy country + timezone
Interests (5–8)	gaming, cooking, home labs, dogs, F1, woodworking	Drives NUFS sub selection
Target subs (5–8)	r/gaming, r/CasualConversation, r/AskReddit, r/NoStupidQuestions, r/woodworking, r/formula1	From NUFS list (7-day guide Section “The Subreddit Map”)
Voice	casual, lowercase, tbh/imo, short paragraphs	From 7-day guide comment templates
Posting window	6–10 PM local time	Matches proxy timezone
ICP subs (later)	2–3 of: r/SaaS, r/Entrepreneur, r/startups, r/marketing, r/automation	Only after 500+ karma + 2–3 weeks history (7-day guide rule)

Persona pool: pre-generate 100–200 personas in a spreadsheet/registry (name, age, location, interests, voice, subs, timezone). Each new account draws the next unused persona. Never reuse a persona.

5.3 Warmup timeline (per account — this IS the 7-day guide, applied fleet-wide)

Phase	Days	Activity per account	Fleet-wide pacing
Cold start	1–2	Scroll + vote; 1–2 comments/day; email verified; 2FA on	Max 5–10 accounts in this phase at once
Ramp	3–7	5–10 comments/day across 3–5 NUFS subs; sort Rising/New; reply to responses	10–15 comments/day/account cap; never 50+/hour
Comment-only	8–14	10–15 comments/day; no posts, no links, no brand	Stagger comment times across timezone windows
Posting	15+	1 value-first post/week in persona subs; still no brand	Only after 100+ karma (7-day guide gate)
ICP transition	21+	Start lurking target ICP subs; comment value-only	Only after 500+ karma + 2–3 weeks history (hard rule)
Brand-eligible	30–60+	Small subset (see Section 8) may carry GrowReach mentions	9:1 ratio per account, forever

The Gojiberry pattern (validated by SWARM-PRD): days 1–7 upvote only (~50/day), days 8–14 comment only (~50/day), day 15+ post 3x/week in ~12 subs with story+proof+link format. Our per-account numbers are deliberately lower (10–15 comments/day) because we run 100+ accounts — aggregate volume comes from fleet size, not per-account intensity.

5.4 Warmup quality gates (per account, before advancing phases)

100+ combined karma (7-day guide target) → posting unlocked
500+ karma + 2–3 weeks history → ICP subs unlocked
CQS at Moderate or higher (check r/WhatIsMyCQS) → brand-eligible pool
Zero removals, zero sub bans, zero shadowban flags → keep advancing
Any removal/ban → hold that account at current phase for 7 days, review the trigger (Section 7.3)

Recycling rule: 100 karma in 7 days is the target. Accounts that hit it move to the “established” pool. Accounts that don’t get 2 more days, then get recycled — retired and replaced by a new persona (never the same persona, never the same proxy/email pattern). A stalled account is a signal, not a project.

6. Anti-Detection & Cross-Account Isolation

6.1 The isolation matrix (non-negotiable)

Layer	Isolation rule	Enforcement
Fingerprint	Unique per profile (canvas, WebGL, UA, timezone, WebRTC)	AdsPower fresh fingerprint per profile; rotate periodically via CLI (`new-fingerprint`, batch of 10)
Network	Unique proxy per profile; ≤3 profiles per IP; country+timezone match	Decodo proxy assignment; `update_browser` with dashboard safety checks
Cookies/session	Cookie jar per profile; clear between campaigns (`delete-cache-v2`)	AdsPower per-profile storage; CLI batch clear
Credentials	Unique email + password + 2FA per account	Vault + AdsPower password manager
Voting	Never vote on the same content from 2+ fleet accounts	Hard rule — see 6.2
Banned subs	Account banned from a sub → Community Mute that sub on that account; no other fleet account may enter it	Registry of banned subs per account
Timing	No two fleet accounts act on the same thread within minutes of each other	Rotation scheduler (Section 7.2)
Device	One AdsPower profile per browser instance; never two profiles in one browser	AdsPower enforces; operator discipline

6.2 The vote-manipulation firewall (fleet-critical)

No fleet account upvotes another fleet account’s content. Ever. Not posts, not comments. This is the exact behavior Reddit’s vote-manipulation detection is built to catch, and it’s the one that gets whole clusters suspended.
No fleet account comments on another fleet account’s post unless the comment is genuinely additive AND the accounts have no shared IP history (different proxies, different timezones). Even then: never within the first hour, never more than 1–2 fleet comments per thread, and never from accounts that share a proxy cluster.
The “10 upvotes ASAP” hack from the Gojiberry blueprint is OFF-LIMITS for the fleet. It worked for a founder with a WhatsApp group of real friends. A botnet-shaped version of it is the textbook vote-ring signature. If a GrowReach post needs early momentum, it gets it from the main account’s real network — not the fleet.
What the fleet CAN do legitimately: comment seeding (value-first, persona-consistent comments from different accounts in threads where GrowReach is genuinely relevant), which is the AI-citation play. Comments, not votes.

6.3 Behavioral anti-detection

No copy-paste across accounts. Every comment is unique — the V4 unified prompt (classifier + generator) already enforces per-subreddit templates and SKIP decisions; run it per account with the account’s persona voice injected.
No identical posting patterns. Accounts differ in: comment volume, sub mix, time-of-day, emoji use, comment length. The persona registry drives this variance.
No simultaneous sessions. One account active at a time per proxy cluster; 15+ min between switching accounts on the same machine (7-day guide rule, scaled).
No cross-account linking. Never log into two fleet accounts from the same browser session; never use the same recovery email/phone across accounts.
Human failure modes are fine — typos, occasional downvotes, taking a day off. Perfection is a bot signature.
VPN caution: Reddit’s CQS considers “network and location signals.” A proxy that hops countries mid-session is a red flag; Decodo residential IPs are stable, but verify the IP geolocation matches the profile timezone on assignment. VPN policy: pick one (on or off) per profile and stay consistent — flipping VPNs = “network and location signals” chaos.

6.4 Shadowban trigger list (observed, from a NewToReddit mod)

These are the behaviors that get accounts shadowbanned. The fleet must never exhibit them:

New accounts under stricter scrutiny than established ones
Many identical posts/comments, especially off-topic
Lots of off-site links — especially the same link to a business (the #1 GrowReach-fleet risk)
Initiating many chats/DMs, especially refused/blocked ones
Vote manipulation or ban evasion (multi-account voting, alt-in-banned-sub)
Nuisance reporting (invalid reports)
Receiving lots of removals

Fleet rule: Mods cannot shadowban you — only admins can. If a profile gets shadowbanned, do NOT create a replacement from the same IP/device — it will likely get shadowbanned too (ban evasion). Quarantine, appeal once, retire if denied.

7. Karma Farming at Scale (NUFS/SNUFS, Rotation, Pacing)

7.1 Subreddit strategy

Primary: NUFS list (official, live — see 7-day guide Section “The Subreddit Map”). These subs volunteered to be new-user friendly; they are the safe karma grounds. Do not abuse them — the mods explicitly warn against spamming NUFS subs; spread activity across the list.
Secondary: SNUFS list (r/TrueOffMyChest, r/asklatinamerica, etc.) — only for accounts with 50+ karma, and only with content-warning awareness (higher downvote risk).
Persona subs (from Section 5) — the long-term karma base; genuine interest = genuine comments = sustainable karma.
ICP subs (r/SaaS, r/Entrepreneur, r/startups, r/marketing, r/automation, r/micro_saas) — the destination, not the farm. Accounts enter only at 500+ karma / 2–3 weeks (hard gate).

7.2 Rotation & pacing (fleet-wide scheduler)

Parameter	Value	Why
Comments per account per day	10–15 (ramp phase), 5–10 (steady state)	Below spam thresholds; sustainable
Comments per account per hour	Max 5	Never 50+/hour (7-day guide hard rule)
Subs per account per day	3–5	No single-sub concentration
Min delay between comments (same account)	3–7 minutes, randomized	Human typing cadence
Min delay between accounts on the SAME post	10–15 minutes (hours apart preferred)	Never looks like a coordinated swarm
Max accounts per thread	2–3, never same proxy cluster	Looks like community, not swarm
Max target-post engagements per account per day	5	Prevents same-account concentration
Weekly volume cap per account	~100 comments	Long-term sustainability
Accounts active simultaneously	1 per proxy cluster	IP-level pacing
Comment time-of-day	Persona’s local window (e.g., 6–10 PM)	Timezone consistency signal
Time-of-day spread (fleet-wide)	Activity spread across 4–8 hours, never one burst	No “shift change” pattern
New accounts per day (fleet-wide)	5–10	Signup velocity cap (Section 4)
Daily fleet comment budget	500–1,500 (at 100–200 accounts)	Aggregate volume without per-account spikes

Rotation mechanics: the scheduler assigns each account a daily comment quota and a sub list; accounts rotate through their persona subs on a 3–5 day cycle so no sub sees the same account daily. Timezone windows (AEST/EDT/BST/PDT) stagger activity so the fleet looks like people in different places, not a single shift.

7.3 Comment quality (the actual karma engine)

Use the 7-day guide comment templates (AskReddit story format, NoStupidQuestions explainer, Advice empathy-first, AITA judgment, CasualConversation small talk) — they’re proven.
Run every comment through the V4 unified prompt (safety classifier first: SKIP on hate/politics/violence/spam/illegal; sensitive categories gated by subreddit guide). A SKIP is a win — it’s a ban avoided.
Answer first, then elaborate, 2–4 sentences, question at the end (Reddit comment fundamentals — opposite of LinkedIn).
Reply to every response to your comments (conversation karma compounds).
Never mention GrowReach during farming. The farm phase is pure value. Brand mentions are a later, gated, small-subset activity (Section 8).

7.4 Downvote & negative-karma management

One downvoted chain can put a new account negative → locks it out of more subs. Avoid controversial topics while karma is low (7-day guide hard rule).
If a comment goes negative: delete it, stop the bleeding, take a break from that sub. Never argue with downvoters; never complain about downvotes.
Dogpiling is real: a negative comment attracts more downvotes. Delete early, delete often.
Accounts that repeatedly go negative get quarantined (paused 7 days) and reviewed — a pattern of downvotes across accounts in the same sub suggests the sub’s culture doesn’t match the persona’s voice; adjust the persona’s sub list.

8. Brand-Eligible Subset (GrowReach Mentions)

The fleet exists to serve GrowReach, but only a small, gated subset ever carries brand mentions:

Gate	Requirement
Karma	500+ combined
History	2–3+ weeks of genuine comments
CQS	Moderate or higher
Record	Zero removals/bans/shadowban flags
Ratio	9:1 forever — 9 value contributions per 1 brand mention
Disclosure	”Full disclosure: I’m the founder of GrowReach” style, early, never hidden (11-account analysis: all successful accounts disclose)
Framing	”I built this to solve X” — never “check out my product”

Target: 10–20% of the fleet (20–40 accounts at full scale) in the brand-eligible pool. The rest stay civilian — they build the AI-citation substrate (brand discussed across many voices) without ever touching the brand. This split is what makes the fleet look like a community that happens to know GrowReach, not a marketing department.

Comment seeding play (the legitimate core use): when a thread genuinely asks for LinkedIn-engagement tool recommendations, 2–3 brand-eligible accounts (different proxies, different timezones, staggered timing) leave value-first comments — each with the Sandwich Method or 5-Block Reply structure, each naming GrowReach inside a 3–4 tool list (Taplio, PhantomBuster, Shield, GrowReach — the tool-stack technique). Never more than 2–3 fleet comments per thread. This is what AI engines scrape into citations.

9. Monitoring: Shadowban/CQS Checks & the Metrics API

9.1 Per-account health checks

Check	How	Cadence
Shadowban	https://www.reddit.com/appeals — if an appeal form appears, you’re shadowbanned/suspended	Every 2 days per active account (7-day guide rule)
CQS	r/WhatIsMyCQS	Every 3–5 days during warmup; weekly after
Filtered vs removed	Open own post/comment on desktop — banner tells which filter got it	On any suspected removal
Karma trend	Metrics API (below)	Daily (automated)
Ban status	Sub ban messages; dashboard ban detection	Continuous (automated)

9.2 Metrics API — r.10xers.co/api/metrics (live, verified 2026-08-10)

The API returns stats + profiles:

stats:  total_profiles, active_profiles, suspended, total_karma,
        total_comments_today, total_posts_today, last_updated
profiles[]: profile_id, profile_no, alias, username, status, platform,
        country, country_flag, timezone, tz_label, age_days,
        is_suspended, last_checked, auto_refresh_status, ...

Fleet dashboards to build on top of it:

Health board — active/suspended counts, karma trend, comments/day, last_checked staleness (profiles whose auto-refresh fails need manual attention).
Quarantine list — accounts paused for review (downvote patterns, removals, CQS drops).
Brand-eligible pool — accounts passing all Section 8 gates, with their 9:1 counters.
Proxy/IP registry — proxy ID per profile, sharing count (never >3), dead-proxy queue, country/timezone match verification.
Subreddit × account matrix — which accounts are active in which subs (from SWARM-FLOWS: the Sub Map screen). Prevents two accounts from the same proxy cluster appearing in the same sub, and prevents banned-sub re-entry.

9.3 Alert thresholds (automate these)

Alert	Threshold	Action
Suspension spike	>2 accounts suspended in 48h	Stop all fleet activity. Review common factors (proxy range, fingerprint batch, email domain, signup batch). Resume only after root cause found.
Shadowban	Any account	Quarantine immediately; appeal once; do NOT create a replacement from the same proxy/email pattern (ban-evasion risk).
CQS drop	Any account drops a tier	Pause 7 days; review recent comments for removal triggers.
Karma stagnation	Account <50 karma after 14 days	Review persona/sub fit; adjust sub list.
Proxy failure	auto_refresh_status != success	Replace proxy (same country+timezone), verify login.
Comment removal rate	>10% of an account’s comments removed in 7 days	Pause account; review voice/sub fit.

The fleet kill-switch: if a suspension spike hits, the operator pauses ALL accounts for 48–72 hours (no activity, no logins), then resumes at 25% volume. Reddit’s enforcement waves pass; a fleet that goes dark and comes back slow survives.

9.4 The escalation ladder (when something goes wrong)

Situation	Response
Comment removed by AutoMod	Read the removal reason. Adjust. Don’t repost.
Post filtered for review	WAIT. Mods approve within hours/days if it fits. Don’t repost.
Subreddit ban	Appeal via mod mail (playbook below). If denied, find another sub. NEVER create an alt to return.
Sitewide suspension	Appeal at reddit.com/appeals. If denied, the profile is dead — retire it, don’t fight it.
Shadowban	Appeal at reddit.com/appeals. If denied, retire the profile. Do NOT create a replacement from the same IP.
Negative karma spiral	Delete the offending comments, stop engaging that sub, wait. Negative karma is hard to come back from.

9.5 The ban appeal playbook (from a mod who processes them)

Take a break first — don’t appeal immediately; let yourself AND the mods cool off.
Work out what went wrong — read all removal/ban messages, read the sub rules, find the interpretation that makes sense in the context of your ban (not the one you think is “most correct”).
In the message: recognize you broke a rule → apologize → indicate you won’t break it going forward. Priority is a successful appeal, not “being right.”
Be polite — your message is visible to ALL mods. Most modmail is combative; being the polite one stands out. Don’t be a “rules lawyer” or “sealion” — those get ignored and muted.
Reply to the ban message or use mod mail — never DM individual mods.
Be patient — mods are volunteers; it can take days.

10. Compliance Matrix

Activity	Allowed?	Risk	Rule
Multiple accounts	✅	None (explicitly allowed)	Even same email OK; keep credentials separate anyway
Same email for multiple accounts	✅	Low	Allowed per help center; prefer unique emails for isolation
Verified email + 2FA per account	✅	None	Required — raises CQS
Genuine commenting on NUFS subs	✅	None	The endorsed karma path
Value-first comments in ICP subs	✅	None	After 500+ karma gate
Brand mention with disclosure, 9:1 ratio	✅	Low	Only brand-eligible subset; Sandwich Method
Comment seeding (2–3 fleet accounts/thread)	✅	Medium	Staggered timing, different proxies, value-first
Coordinated upvoting of one post	❌	Critical — sitewide suspension	Never. The firewall (6.2).
Voting on same content from 2+ accounts	❌	Critical	Never, even “harmless” upvotes
Re-entering a banned sub on another account	❌	Critical — ban evasion	Community Mute; registry
Buying accounts	❌	Critical	Never; all accounts in-house
Free-karma subs	❌	High	Instant ban from major subs; poisons IP reputation
Copy-paste comments across accounts	❌	High	Spam filter trigger; V4 prompt per account
Same link posted across subs	❌	High	Classic shadowban trigger
AI-generated comment floods	❌	High	Spam policy (May 2026) explicitly covers generative-AI-assisted spam
DM/chat promotion	❌	High	Spam policy territory
Asking for upvotes	❌	High	Vote manipulation, per Reddiquette + Disrupting Communities
50+ comments/hour from one account	❌	Medium	Bot signature
Controversial topics while karma low	❌	Medium	Downvote spiral → negative karma → restrictions
Paying “account fixers”	❌	High	Scams; only admins can fix
Deleting own negative comments	✅	None	Documented strategy; stops downvote bleeding
Community Mute for banned subs	✅	None	Explicitly fine
Profile curation (hide history)	✅	Low	Makes history harder (not impossible) to see

11. 90-Day Fleet Rollout Plan

Phase 0 — Foundation (Days 1–15)

Finalize persona pool (100–200 personas in registry)
Email provisioning pipeline live (5–10/day capacity, phone pool ready)
Decodo proxy inventory: 100–200 residential IPs, country/timezone-tagged, sharing ≤3
AdsPower: batch-create CLI scripts validated (create profile + fingerprint + proxy in one command)
Metrics API extended: quarantine list, brand-eligible pool, proxy registry, sub×account matrix
V4 prompt wired per-account with persona voice injection
Gate: pilot 10 accounts created, warmed to 100+ karma, zero bans → proceed

Phase 1 — Pilot Validation (Days 16–30)

10 pilot accounts complete full warmup (7-day guide, fleet pacing)
2 accounts reach brand-eligible status (500+ karma, 2–3 weeks, CQS Moderate+)
First comment-seeding test: 1 thread, 2 fleet accounts, staggered, value-first
Shadowban/CQS check cadence automated (every 2 days)
Gate: ban rate <5%, shadowban rate 0%, karma trajectory on plan → proceed

Phase 2 — First Scale Wave (Days 31–60)

Wave 1: +20 accounts (2 per timezone cluster) — total ~30
Wave 2: +30 accounts — total ~60
Rotation scheduler live: daily quotas, sub lists, timezone windows
Brand-eligible pool grows to 8–12 accounts
Comment seeding at 2–3 threads/week; AI-citation check (search ChatGPT/Perplexity for “best LinkedIn engagement tool” — is GrowReach appearing?)
Gate: ban rate <5% sustained, 0 suspension spikes, seeding threads show no mod pushback → proceed

Phase 3 — Full Scale (Days 61–90)

Wave 3: +40–140 accounts (paced 5–10/day) — total 100–200
RPA process definitions for mechanical bulk workflows (open → navigate → upvote → screenshot) if MCP throughput is the bottleneck
Brand-eligible pool at 20–40 accounts; 9:1 counters enforced
Fleet comment volume: 500–1,500/day across all accounts
Monthly fleet review: ban/suspension post-mortems, persona/sub-fit adjustments, proxy health
Gate: fleet stable at target size, <5% ban rate, AI citations appearing → steady state

Steady state (Day 90+)

Replace accounts at ~2–5%/month attrition (bans, shadowbans, CQS decay)
Continuous persona refresh (new personas for replacement accounts)
Quarterly compliance audit against Section 2 and Section 10

12. KPIs

Fleet health KPIs

KPI	Target	Measurement
Active accounts	90%+ of fleet	Metrics API `active_profiles / total_profiles`
Suspension rate	<5% per quarter	`suspended / total` over 90 days
Shadowban rate	0% (any = incident)	Appeals check cadence
Ban rate (sub-level)	<5% per quarter	Ban messages + dashboard
CQS distribution	70%+ Moderate or higher	r/WhatIsMyCQS per account
Account age at brand-eligibility	30–60 days	Registry

Karma & activity KPIs

KPI	Target	Measurement
Time to 100 karma	≤14 days per account	Metrics API age_days + karma
Time to 500 karma	≤45 days per account	Metrics API
Comments per account/day	5–15 (phase-dependent)	Metrics API `total_comments_today`
Fleet comment volume	500–1,500/day at full scale	Metrics API
Comment removal rate	<10% per account/week	Dashboard
Karma per comment (fleet avg)	≥1.0	Metrics API
Comment-to-karma conversion (NUFS subs)	1 comment ≈ 2–5 karma	Metrics API + manual sample
Accounts at 100+ karma	70% of fleet	Metrics API
Accounts at 500+ karma	25% of fleet	Metrics API

Business KPIs (why the fleet exists)

KPI	Target	Measurement
AI citations of GrowReach	1+ by day 60, 5+ by day 90	Manual ChatGPT/Perplexity checks (“best LinkedIn engagement tool”, “Taplio alternative”)
Threads seeded per week	2–3 (Phase 2), 5–10 (Phase 3)	Campaign registry
Brand-eligible accounts	20–40 at full scale	Registry
9:1 ratio compliance	100% of brand-eligible accounts	Per-account counters
Referral sessions from Reddit	15,000+ by day 90 (strategy guide target)	GA4 with UTM schema
Trial signups from Reddit	50+ by day 90	Product analytics
Cost per account (email+proxy+infra)	Tracked; proxy is the dominant cost	Finance sheet

The one KPI that matters most

Suspension rate. Every other KPI is meaningless if the fleet dies. If suspension rate ever exceeds 5% in a quarter, stop scaling, find the common factor, fix it, resume. The fleet is a long-term asset — 200 aged accounts in 12 months is worth more than 200 fresh accounts today.

13. Sources & References

7-day karma guide: guides/reddit-karma-7day-guide.md (543 lines — NUFS/SNUFS lists, CQS, shadowban checks, comment templates, ban-evasion rules). The per-account playbook; this guide assumes it.
AdsPower KB: adspower-kb/00-master-kb.md (4 integration layers, auth, rate limits), 01-local-api.md, 02-cli-skill.md, 03-mcp-rpa.md, 04-integration-plan.md (layer × use-case matrix), 05-profile-recommendation.md (adspower-operator profile split).
Proxy management: adspower-dashboard/proxy-ip-management-plan.md (update_browser flow, safety checks, Webshare/Decodo API).
Swarm engine: adspower-dashboard/SWARM-PRD.md (Gojiberry blueprint, data fabric, safety contract), SWARM-PLAN.md, SWARM-FLOWS.md (sub map, timezone windows, health screens).
Comment generation: reddit-rpa-prompts/reddit-comment-system-prompt-v4-unified.md (classifier + generator, SKIP categories, per-sub templates).
Metrics API: r.10xers.co/api/metrics (live) + scripts/analyze_reddit_metrics.py.
Strategy: growreach-reddit-strategy/reddit-marketing-strategy-guide.md + account-analysis/ (11-account analysis: disclosure, tool-stack mentions, 9:1 ratio, r/micro_saas insight).
Reddit official: help center (spam policy 2026-05-19, ban evasion, vote manipulation, CQS), r/NewToReddit wiki (fetched live 2026-08-10).

Explorer

Reddit Profile Fleet Guide