Pixel phone farm

Three factors make a supported Pixel the current ShadowPhone requirement: GrapheneOS compatibility, an unlockable and relockable boot process, and a published security-support lifecycle.

GrapheneOS only runs on Pixel. GrapheneOS is a hardened Android distribution that supports multi-profile sandboxing, verified boot, and hardware attestation. It only officially supports Google Pixel devices. Since ShadowPhone relies on GrapheneOS profiles to isolate Instagram accounts, Pixel is a hard requirement, not a preference.

Hardware condition matters for uptime. Test USB-C data, battery health, thermal behavior, cameras, factory-reset protection, and ADB stability on a sample unit before buying a batch. Pixel 6-generation and later devices use Google Tensor hardware, not Qualcomm Tensor chipsets.

Support life is part of the purchase price. Used prices vary by region, condition, carrier lock, and return policy. Compare the live quote against the device's published support end instead of choosing the lowest sticker price.

GrapheneOS ties support to the OEM's firmware and security-update window. For current dates, use the official device-support FAQ, not a used-price ranking:

Pixel 8-generation and later devices receive a seven-year minimum support guarantee from launch and are GrapheneOS's recommendation for new purchases. Treat every earlier model as a dated migration decision, not a universal bargain.

GrapheneOS transforms a Pixel phone from a single-account device into a multi-account isolation platform. Each GrapheneOS profile gets its own:

• Sandboxed app environment (separate Instagram installation, cookies, and local storage)
• Profile-scoped app state and identifiers such as Android ID
• Per-profile app permissions and configuration
• Isolated file system and preferences

A supported Pixel can host multiple isolated Android profiles, each with separate app data. That is useful for account organization, but it is not equivalent to separate physical phones: apps can still observe the shared device model, and GrapheneOS says apps can detect the OS through its privacy and security behavior. See the device environment explainer for the distinction.

Stock Android also has user profiles, while GrapheneOS adds a hardened security and verified-boot model on supported Pixels. Profiles on either system normally share the phone's network path; GrapheneOS does not automatically create per-profile network isolation. ShadowPhone requires GrapheneOS for its supported profile-management workflow.

ShadowPhone uses a server-side Brain and local Executor architecture. The Brain runs in the cloud and handles scheduling, targeting logic, AI content generation, and workflow orchestration. The Executor runs on your desktop and communicates with your Pixel phones via ADB over USB.

Device visibility. The dashboard shows every connected Pixel, its current profile, account assignments, workflow status, and health metrics in real time. You see which phones are active, which accounts are warming up, and which workflows are queued.

Profile management. ShadowPhone handles switching between GrapheneOS profiles on each device, ensuring the right account runs in the right isolated environment. Account-to-profile mapping is persistent, so an account always returns to the same device environment.

Workflow distribution. The registered workflow modules (follows, likes, DMs, story views, comments, Reels interactions, content posting) are distributed across your Pixel fleet based on scheduling rules, warmup status, and action limits. The Brain handles pacing so no single account or device exceeds safe thresholds.

Fleet scaling. Adding a new Pixel to your farm means connecting it via USB, flashing GrapheneOS if needed, creating profiles, and assigning accounts. ShadowPhone picks up the new device automatically and integrates it into your existing workflow distribution.

Build the budget from current quotes rather than fixed used-device prices:

Compare total cost of ownership using live quotes, expected support life, replacement terms, power, connectivity, and operator time. Physical and hosted approaches expose different infrastructure signals; neither guarantees better account outcomes.

ShadowPhone's current executor is built for GrapheneOS on supported Pixels. Other Android brands are outside that supported deployment path:

• Samsung: Not listed for official GrapheneOS production support and not supported by the current ShadowPhone deployment.
• OnePlus: Not listed for official GrapheneOS production support and not supported by the current ShadowPhone deployment.
• Xiaomi: Not listed for official GrapheneOS production support and not supported by the current ShadowPhone deployment.
• Generic Android: Do not assume ADB access alone makes a device compatible; the current product expects GrapheneOS on a supported Pixel.

This is a product-compatibility boundary, not a claim that Pixel hardware eliminates enforcement risk. Use the official GrapheneOS supported-device list and ShadowPhone's current requirements as the source of truth.

ShadowPhone plans scale with your Pixel fleet:

• Starter ($97/mo): 1 phone, up to 25 accounts. Best for testing the model and running a small operation.
• Growth ($247/mo): 5 phones, up to 75 accounts. The standard for growing agencies and theme page operators.
• Agency ($497/mo): 10 phones, up to 500 accounts. Full fleet management with dedicated support and advanced analytics.

Every plan includes the 7-day free trial. When scaling, add phones incrementally. Start with 1-3 devices, prove the workflow, then expand. The scaling guide covers the operational details of growing from a starter setup to a full agency farm.

For physical infrastructure at scale, the power management guide and networking guide cover rack organization, USB hub selection, thermal management, and network topology.