Skip to main content
AutoGrowth runs social accounts on real phones. You own the phones, they sit on a desk plugged into a Mac you own, and they tap through Instagram, TikTok, X and Threads the way a person would. Nothing goes through a social platform’s API, and no account is driven from a server somewhere. There are three pieces, and you use all three:

Who this is for

People running more than a handful of social accounts, who already have phones or are willing to buy them. A fleet of one phone works; the product is built for fleets of dozens. You need:
  • A Mac that stays on and awake. The phones connect to it by cable.
  • iPhones, or GrapheneOS phones. Stock Android is not supported — see Android phones.
  • Good USB cables and, past a few phones, powered ports.
  • An AutoGrowth organization. One person is its owner.
Running automations also requires Autogrowth MAX, a one-time lifetime license offered by invitation. Watching and controlling phones does not.

What it is not

AutoGrowth is not a scheduler that posts from the cloud. If the Mac is asleep or the Companion is closed, nothing runs — the phones are the product, not a convenience. What AutoGrowth does not do is the full honest list.

Where to start

How AutoGrowth works

The mental model: what runs where, and what stops when.

Install the Companion

Get the app onto your Mac and sign it in.

Connect your phones

Cable, Trust, and the first phone appearing in the list.

Your fleet

The Fleet page, its statuses, and what each one means.

Beyond the dashboard

MCP server

Connect an AI assistant to your fleet over MCP.

REST API

The developer API, its scope and its limits.