Phone farm cost estimator

Start with the number of accounts in the planned operation and the number of physical phone connections you intend to use. Those are independent inputs. The estimator never divides account count by a fixed accounts-per-phone ratio.

Enter current purchase or vendor quotes for every approach you want to compare. A first-year estimate is the entered one-time cost plus twelve months of the entered recurring cost. Only the public ShadowPhone subscription prices are supplied automatically; all other amounts come from you.

Enter zero when a quoted line item is genuinely zero, such as phones already owned. Leave a field blank when you do not yet have a quote; the corresponding result stays incomplete rather than pretending the missing cost is free.

A DIY operation means the operator chooses, buys, connects, and maintains the phones. Enter the phone count you plan to support based on your workflow, hardware testing, staffing, and risk tolerance. A subscription allowance or Android profile count is not evidence of operating capacity.

One-time inputs. Use current quotes for supported phones, powered hubs, USB data cables, charging, mounts, and setup work. If hardware is already owned, enter zero for its purchase line while still including replacement and maintenance costs where relevant.

Monthly inputs. Add connectivity, electricity, maintenance, labor, and any DIY software. Connectivity design is operator-controlled; a SIM, VPN, or proxy does not automatically create a unique public IP or prevent account correlation.

Cloud-phone vendors package instances, runtime, storage, bandwidth, and add-ons differently. Use a current quote for the account scope, runtime pattern, region, and retention needs you actually plan to purchase. Do not infer one account per instance unless the vendor terms and your operating plan require it.

Put setup or migration charges in the one-time field. Put all recurring instance, runtime, connectivity, storage, and support charges in the monthly field. Recheck the quote before purchase because provider pricing and inclusions can change.

Cloud and physical-device execution environments have different operational tradeoffs. Meta does not publish a universal enforcement or reach outcome for either path, so this estimator compares entered costs rather than assigning a detection premium.

An antidetect stack can include a browser subscription, profile allowances, team seats, proxies, bandwidth, and automation tooling. Enter a current quote covering the selected account scope and every required add-on instead of using a generic per-profile or per-gigabyte market assumption.

This remains a browser-based operating model rather than Android app execution. That distinction may matter to your workflow, but it does not provide a measurable account-survival adjustment for a cost formula. Compare capabilities and policy fit separately from the financial estimate.

ShadowPhone provides software for supported workflows on connected Android phones. The operator supplies supported physical phones, connectivity, USB and charging equipment, and the local infrastructure needed to run them. The estimator adds those user-entered costs to the applicable subscription price.

Starter — $97/mo. Subscription limits: 1 phone connection and 25 Instagram accounts.

Growth — $247/mo. Subscription limits: 5 phone connections and 75 Instagram accounts.

Agency — $497/mo. Subscription limits: 10 phone connections and 500 Instagram accounts.

These account and phone-connection allowances are billing limits, not a per-phone capacity promise. GrapheneOS profiles separate app data and cookies on the same physical phone; they still share that phone's hardware and default network egress unless the operator configures networking differently.

The cards show only the amounts you entered. They do not label a winner, estimate a breakeven month, or assume that one approach's missing quote is zero. Compare first-year cost only after every approach has complete inputs.

Financial totals are only one decision factor. Separately compare workflow coverage, hardware support, data handling, authentication, provider terms, operational control, and the time required to maintain the setup.

See related operating-model context in ShadowPhone vs GeeLark and physical phones vs emulators.

Labor and downtime. Include setup, monitoring, troubleshooting, updates, and recovery work in the monthly operating total if those hours matter to the comparison.

Replacement and financing. Add expected device replacement, battery service, cable and hub replacement, financing charges, and taxes using your own planning horizon and quotes.

Provider scope. Confirm whether a quote covers seats, profiles, instances, runtime, bandwidth, storage, support, and taxes. A low headline price can omit required line items.

Account outcomes. Do not add a fabricated ban, survival, or reach percentage to the financial model. Platform outcomes depend on content, behavior, account history, networking, and enforcement—not a fixed architecture multiplier.