← back to blog

how to run multiple Bluesky accounts and avoid suspensions

how to run multiple Bluesky accounts and avoid suspensions

if you want to run multiple Bluesky accounts in 2026, the fundamentals are the same as any modern social platform. real device per account, real residential mobile IP per account, real warm-up before posting. but Bluesky has its own quirks that make multi-account harder than people expect: a federated AT Protocol architecture that exposes more telemetry than centralized platforms, a moderation-label system that lets users tag accounts as bots, and a rapidly evolving anti-abuse stack since the network went fully open in 2024.

cloud phones solve the device half of this. each cloud phone is a real Singapore Android device with its own arm64 fingerprint, IMEI, ANDROID_ID, and clean install state. paired with a Singapore mobile IP and a fresh email per account, you get isolation that survives Bluesky’s per-account checks.

why Bluesky multi-account is harder than Twitter clones

Bluesky runs on the AT Protocol, which is more transparent than Twitter or Threads. every post, repost, and like is queryable by anyone via the public AT Protocol endpoints. that means anti-abuse researchers, including Bluesky moderation, can correlate behavior patterns across accounts at a level that closed platforms cannot match.

three signals matter most. first, posting cadence. accounts that post on identical timestamps across multiple handles get clustered. second, repost graphs. accounts that always repost each other in the same order build a fingerprint. third, IP and PDS (Personal Data Server) hosting. running multiple accounts from the same IP on the same PDS makes the cluster trivially detectable.

cloud phones address two of those: device-side fingerprint and IP. you still have to vary content cadence and avoid mutual-amplification rings on your own.

the right setup: one cloud phone, one email, one IP

per account, you need: one cloud phone in Singapore on a Singapore mobile IP, one fresh email (avoid throwaway services that share infrastructure with bot operators), one invite code (Bluesky removed mandatory invites in early 2024 but kept them as a quality signal), one persona plan (name, handle, avatar, bio, niche).

if you want context on cloud phone basics, see how to share a cloud phone with your team and how to rotate mobile IP on a cloud phone.

step-by-step: registering a Bluesky account on a cloud phone

1. log in to cloudf.one. pick a phone that has not been used for Bluesky. confirm the IP via ifconfig.me. it should be a Singapore mobile carrier ASN.

2. open Google Play. install the Bluesky Social app (developed by Bluesky, PBC).

3. open Bluesky. tap “create new account.” enter the email, choose a handle ending in .bsky.social for the first account (custom domain handles come later), set a password.

4. confirm the email via the verification message. set a profile photo and a 50 to 100 character bio. pick something specific to your persona, not “user1234.”

5. follow 30 to 50 accounts in your niche. let the home feed populate. do not post for 24 hours.

6. day 2 onward: post once a day, repost twice a day, like 10 posts a day. behave like a normal user finding their voice on a new network.

the invite-code system and what it signals

Bluesky removed mandatory invite codes in February 2024, but invites still carry weight inside the moderation model. accounts that join via an invite from a long-standing trusted account inherit a small reputation boost. accounts that sign up via the public flow get a neutral score and have to earn trust through behavior.

if you have access to invites from real users, use them. otherwise, use the public sign-up flow and accept that the first 30 days are a probation period.

why custom domain handles matter

Bluesky lets you set your handle as a domain you control (e.g. xavier.cloudf.one instead of xavier.bsky.social). custom domain handles are a strong trust signal because they require DNS control. for serious multi-account work, register one domain per persona cluster (e.g. one for your news personas, one for your reviewer personas) and assign subdomain handles to each account.

DNS verification happens via a TXT record. once verified, your handle becomes the domain, and the moderation model treats your account as more trustworthy.

scripting Bluesky: the AT Protocol is open

unlike Threads or Signal, Bluesky has a fully documented public API. the AT Protocol docs describe every endpoint. you can post, repost, follow, and read timelines via REST or WebSocket without scraping.

this sounds tempting for automation, but it cuts both ways. Bluesky moderation can replay your API calls and see the cadence, content, and graph in real time. mass-posting via the API gets caught fast.

if you must automate, the safest pattern is ADB-driven UI taps against the official Android app on a cloud phone, exactly like how to set up ADB on cloudf.one describes.

# example: open Bluesky and tap compose via ADB
adb -s 192.168.x.x:5555 shell am start -n xyz.blueskyweb.app/.MainActivity
sleep 3
adb -s 192.168.x.x:5555 shell input tap 950 1900   # compose fab

cap each phone at 3 posts per day. mass posting triggers the spam-label moderation flow.

moderation labels and how they kill bulk accounts

Bluesky’s moderation system uses labels: tags that other users or moderation services attach to accounts. common labels include !hide (account is hidden from feeds), spam, impersonation, and custom labels from third-party moderation services. once an account picks up a spam label from a respected service, it gets filtered out of most feeds.

the labels are public and the AT Protocol exposes them via the labeling endpoints. a multi-account program that picks up labels on 5 of 50 accounts loses reach on 5 accounts immediately and hurts the trust score on the cluster.

prevention: never post identical content across accounts, never reply to your own posts from a second account in the first 60 seconds, never follow yourself across accounts in the same hour.

scaling 5, 20, 100 Bluesky accounts

5 accounts: manage by hand from one cloudf.one tab per phone. 20 accounts: spreadsheet with phone ID, handle, custom domain (if any), niche, last-post date, label status. 100 accounts: orchestrator script that picks the next phone in the rotation, runs the ADB posting workflow, and polls the AT Protocol labeling endpoint to detect new labels.

the unique constraint at scale: content variation. Bluesky’s open API makes content-similarity detection across accounts trivial for moderators. if 50 of your accounts post the same article in the same hour, all 50 get clustered and labeled.

try Bluesky multi-account on real Singapore phones

you can register for a free trial and get a cloud phone for an hour to confirm Bluesky registration works on a Singapore mobile IP. once confirmed, scale to a paid plan and add accounts at a sustainable rate.

frequently asked questions

do I need an invite code for Bluesky?

no. Bluesky removed mandatory invites in February 2024. invites still carry a small trust boost if they come from a long-standing account, but they are not required.

can I run multiple Bluesky accounts on one phone?

the official Android app supports one logged-in account at a time. for multi-account, you need one cloud phone per account. switching accounts on the same phone is possible but creates a device-fingerprint cluster that moderation can detect.

will Bluesky detect cloud phones as suspicious?

real cloud Android phones pass Bluesky’s checks because they are real arm64 hardware on real mobile IPs. emulators get filtered. our real device vs emulator detection deep dive covers the technical reasons.

is the AT Protocol API safe to use for automation?

the API is fully public and supported, so you will not get banned just for using it. but moderation can see cadence and patterns in real time. if you mass-post via the API, expect labels within 24 hours. UI-driven automation on a cloud phone is safer.

what happens if my Bluesky account picks up a spam label?

the account stays alive but gets filtered from most feeds. the label can be appealed to the labeling service, but appeals are slow. prevention is cheaper than recovery: post like a human, follow at human pace, vary content across accounts.