Apple cluster control means running many iPhones from one computer: screens viewed together, tasks dispatched by group, results collected in one place.
This one answers: What Does Apple Cluster Control Cost per Year.
Someone running a mobile game studio was scaling from thirty devices to eighty and asked me to help budget it.
He had costed one thing: the per-device price of the software. I said that would miss the expensive part.
We laid a year out on the table. It came to three lines.
Line one: licensing, per device and per feature
This is the visible one, the one on the quote.
The industry norm is per device, with features priced separately. EasyClick splits it in two: a USB device licence covering debugging, script execution and script recording in cluster control; and a USB mirroring licence covering the phone screens themselves. Each is authorised separately, charged per phone, with nothing extra from the author.
So the first thing to settle is which actions you actually need. Running scripts only is one line. Watching screens and running scripts is two.
Line two: hardware and signing, where the routes diverge most
This is where costs differ by an order of magnitude.
On the proxy IPA route you carry signing. Free options such as TrollStore generally stop at iOS 16.6.1 and drop on reboot. An individual developer account is 688 CNY a year for 100 devices. Third-party certificates cost less per device but many only work on iOS 15 and up. Free AppleID signing covers three devices.
On Bluetooth or OTG hardware you carry boards: ESP32C3 for Bluetooth, ESP32S3 for OTG, plus firmware flashing and MAC labelling. Boards are not expensive, but they fail, so budget replacements.
On direct data cable, neither of these exists. No signing, no boards, console 10.7.0 or newer with iOS 17 or newer.
Line three: time, the line nobody quotes
This one appears on no quote sheet, and it comes back every year.
A route that saves on signing may cost you half a day a month re-signing. A cheap board route may cost you failure triage and re-pairing. The cheapest quote of all may drop devices once you pass a dozen, and you will spend the time working out whether it is the cable, the power or the software.
A simple test: ask how many places you would check when something breaks. Console and a cable is two. Console, boards and Bluetooth pairing is three. The number of variables sets the troubleshooting time directly.
What you pay once, and what you pay every year
Once: the phones, the cables, powered hubs, the rack.
Once per device: the device licence. Add devices, add licences; otherwise it does not move.
Every year: signing if you use proxy IPA, board replacements if you use hardware, and model API usage if you use the AI agent，that last one is metered by your own usage, and re-running a saved workflow consumes no tokens.
Every year regardless: maintenance time.
Rough shape at three scales
Under thirty devices: licensing dominates, hardware can be zero with direct wiring, and maintenance is an hour or two a month.
Thirty to a hundred: licensing scales linearly. This is the range where power and cooling have to be solved properly, with powered hubs and spacing decided up front. Maintenance starts being measured in weeks.
Above a hundred: group the devices and manage them in batches. This is where the console earns its place，grouping and batch dispatch，while the AI layer, split out as iEasyRun since 10.6.0, strings the steps together and reduces how often a person has to step in.
Where cheap ends and expensive begins
Not at the quoted number. At what the route makes you pay on top.
For the same device count, a route without signing saves the 688 CNY or a certificate, plus the time spent re-signing. A route without boards saves the boards and the failures. A route that supports iOS 12 through 27 saves the cost of retiring and replacing older handsets，and at eighty phones, that one line dwarfs everything above it.
Ask what your chosen route costs you on top, then look at the quote. The other order gets the maths wrong.