The shelf

Now multiply that by the shelf.

You just watched one phone post. Every phone here is doing the same, on its own accounts, on its own schedule, out of the same library.

The system

One hand on all of it. Yours.

Rented farms and proxy pools come with a clause: they can cut you off. This doesn’t. The phones are in your building, the logins are in your hands, and the only thing that stops the fleet is you.

Held byNobody. It runs.12/12 running
The farm operator
Can't reach it.
The proxy vendor
Never had the logins.
The cloud host
Nothing of yours on it.
  1. 01The phones live where you put them.
  2. 02Every login stays with you.
  3. 03Any script you can read, you can stop.

Plug in and RUN

Swap scripts instantly like loading a new cartridge. Our pre-built automation modules drop right into your workflow—no setup, no configuration. Just plug in and go.

  1. Premade automations

    Ours, or the ones you build yourself.

  2. Plug into any phone

    No setup. No configuration. It goes in whole.

  3. Then it runs without you

    Every account, every device, every hour.

Isolation

Every account thinks it has the phone to itself.

Switching container does not switch account. It changes what the app on the other side believes it is running on: a different handset, a different OS, a different serial and IMEI, reached over a different route.

Switch one. Watch the phone change.

Containers

iPhone 03 · isolated app identities on this device

12 of 24
12/24
iPhone 15 Pro, Natural Titanium

iPhone 15 ProNatural Titanium

What studio_main reports to Instagram

Model
iPhone 15 Pro
iOS
17.2
Serial
F2LX9K3QH7GD
IMEI
356938035643809
Route
res-us-1US

Runs on

stock iOSVanillajailbrokenJailbroken

Containers run on a stock iPhone and on a jailbroken one, and on GrapheneOS as the phone’s own user profiles. Same fleet, same isolation.

One handset, twelve identities

The phone on the shelf never changes. What changes is what each container reports about it: a different model, a different OS build, a different serial and IMEI, reached over a route of its own. They share no storage, no login and no device fingerprint, so an account has no way to see the eleven beside it.

Content Library

Your content,
organized

One library behind the whole fleet. Upload images, video, reels and carousels once, sort them into folders, and every phone posts from the same shelf instead of from whatever happens to be on it.

  • Images, video, reels and carousels in one place
  • Folders and tags instead of a shared drive
  • Pushed straight to a device's pasteboard
  • Bulk upload, bulk assign, bulk replace

Access

Applications only.

AutoGrowth is sold by demonstration, one to one. Tell us what you run and we will show you the system against it.

Apply for access

Demonstrations run by appointment.

Can I run the full system with my own phones?
Yes. AutoGrowth runs on phones you own, on your own Mac. The companion app carries the fleet, the scripts and the containers. Nothing of yours sits on shared hardware.
iPhone or Android?
Both. iPhones and GrapheneOS Pixels pair through the same Companion, sit on the same board and are driven the same way.
Do they have to be jailbroken?
No. A stock phone runs scripts, workflows and containers. Jailbreaking is optional and unlocks the deeper container system, in the same manager.
How many accounts per device?
Several. Our own container system runs multiple accounts on one phone without swapping logins.
What happens when a automation gets stuck?
With AI recovery on, the phone sends its screen and data to our AI system, which reads what is covering it and clears it.
How do I get access?
Currently AutoGrowth is only available to a select few users. We are accepting new users slowly, so please join the waitlist. If you are in an affiliated group that has a bypass access key, you can skip the line and use that.