@studio.fleet
Le setup qui tourne seul la nuit
son original

Plug your iPhones into one Mac and drive the whole shelf from a single dashboard. Live screens, remote taps, and schedules that keep running after you close the laptop.
@studio.fleet
Le setup qui tourne seul la nuit
son original
iPhone 14
Free while you set it up, no card, cancel in one click
A shelf of phones is easy to lose track of. Which one is mid-run, which one dropped off, which one nobody has touched in a week.
Every phone reports its own state. You see what is running, what is idle, and what stopped, without unlocking a single screen.
Daily, weekly, or one off, in the timezone you pick. Runs queue per device so two jobs never fight over the same phone.

iPhone 13 finished a run
succeeded2m ago
iPhone SE started its 14:30 job
running6m ago
iPhone 12 came back online
reconnected11m ago
iPhone 14 queued behind a run
queued14m ago
Activity
Runs report as they go. When one fails you get the step it failed on and the log around it, not just a red dot the next morning.
The fleet
Ten to fifteen phones per machine in practice. Past that, add a second machine and it joins the same workspace.
iPhone SE
Mon, Wed, Fri
28%
iPhone 12
Daily · 20:00
84%
iPhone 13
Daily · 09:00
62%
A device runs one job at a time. Anything else due waits its turn rather than fighting for the same screen.
An office desk, a cupboard, a colocated Mac mini. The agent dials out, so nothing needs opening on your network.
Long-running hardware fails in boring ways. Cables come loose, Macs sleep, phones drop off Wi-Fi. The scheduler assumes all of it.
Where USB bandwidth, not the machine, becomes the limit.
If an agent drops mid-run, the work becomes available again on its own.
Anyone can fire a job once. Keeping a shelf of phones honest for weeks is a different problem.
Remote control
Its live screen, and your taps and swipes going back the other way. No screen sharing app in the middle.
Versioned tasks
Each automation is versioned. When a new version ships, existing schedules keep running the one they were created with.
Recovery
Leases expire on their own, so a Mac that slept mid-run does not leave a job stuck forever.
Windows
A run that missed its window is skipped and the schedule advanced, instead of firing a whole night of jobs at 6am.
History
Duration, outcome, and the lines the task wrote as it went. Enough to tell a flaky phone from a broken automation.
Setup
The phones stay yours, on your desk, signed with your own Apple account. Nothing to ship anywhere.
USB into any Mac. One cable per phone, a powered hub if you have a lot of them.
One command, then paste your workspace token. Your phones show up in the dashboard on their own.
Pick a device, pick an automation, pick when. It keeps running whether or not the browser is open.
Where things live
Unlock codes are written to the agent machine and never sent to us.
Every row is fenced to one workspace at the database level, not just in app code.
Screen streams go from your Mac to your browser without passing through us.
Questions
A Mac, Xcode, and at least one iPhone you can plug in. You also need an Apple Developer account to sign the automation runner onto your devices.
Ten to fifteen in practice, and a powered USB hub matters more than the Mac does. Past that, add a second machine and run a second agent.
No. Video goes straight from your Mac to your browser. We hold schedules, logs, and account data, not the stream.
Runs due while the agent was offline are picked up when it comes back, as long as they are still inside their window. Past that they are skipped rather than fired late.
Not yet. Automations ship as versioned plugins we maintain. Bringing your own is on the roadmap once the sandbox story is solid.
They stay yours and stay plugged in. You lose the dashboard and the scheduler, not the hardware, and nothing is installed on the phones that we control.
Connect your first phone today and see the whole thing running before you decide anything.