What we run
The hardware is ours. We buy the phones, rack them, cable them, power them, keep them on the network, watch them and replace them when they fail. On your side there is nothing to install and nothing to host: no agent, no VPN, no inbound firewall rule. Anyone you invite to your organization opens the console, picks a device and controls it: tap, swipe, type, launch apps, upload files.
Each device is yours for the whole subscription rather than pooled and time-shared between customers, so logins and app state persist between sessions. Video reaches your browser peer to peer over WebRTC; the hub passes the signalling and never touches the video.
Why it exists
HelioFleet was built out of running racks of real iPhones ourselves. The phone is never the hard part. Keeping it paired, powered, streaming and reachable from a browser every day, without someone walking to the rack, is the hard part, and it is work that a team which needs a few real phones has no reason to learn. HelioFleet packages that work so a team can have a dedicated iPhone in a tab the same day it asks for one.
The teams it is built for run client social media accounts on real phones, check creatives, click paths and App Store listings on a real screen, verify their own funnels, and test iOS apps on real hardware.
How it is run
HelioFleet is run by the people who built it. The same people who rack the phones read [email protected], and a report of a device that is not working goes to them, not to a queue.
Access is by request rather than self-serve signup, which keeps the number of devices in the racks matched to the customers on them. Billing is per device through Stripe, monthly or yearly, with no setup fee and no minimum term. The live count of devices available right now is on the homepage, read from the same figure the checkout enforces, and it is shown as zero when it is zero.
What we commit to in writing is in the Terms and Conditions and the Privacy Policy, including what happens to a device and its data when a lease ends and a plain statement of what the video relay can and cannot see.
What is not built yet
HelioFleet is early, and some things are deliberately not built. They are listed here so they are found before a purchase rather than after one.
- No self-serve signup. Access is by request, and a person creates each tenant.
- No model selection from the console. Devices are assigned from our pool, usually iPhone SE, and a hard model or iOS version requirement is a support conversation.
- No SIM or mobile data. Devices are on Wi-Fi with a shared IP today; SIM and mobile data per device is planned.
- No in-place subscription decrease. Device counts go up in place; going down is a cancel and resubscribe at the end of the cycle.
- No automation endpoint for customers. The console is the whole product; a session is a person in a browser tab.
Contact
Questions, device reports and anything else go to [email protected]. To get a tenant for your team, request access; the FAQ answers most of what people ask first.
