The tasks, the schedules and the admin are the same in all three. What changes is who runs the hub, what code you receive and whether you need a computer at all.
Hosted hubs are new. Where something isn't there yet, the table says so.
| A · FULL SOURCE | B · HOSTED HUB | C · PHONE APP | |
|---|---|---|---|
| PHONES | At your place, on USB | At your place, on USB | One phone, anywhere with internet |
| COMPUTER ON YOUR SIDE | Windows 11 or Linux, runs everything | Windows 11 or Linux, runs the edge package | Not needed |
| WORKER | On your machine | On your machine, inside the edge package | Built into the app |
| HUB AND DATABASE | Yours | Ours | Ours |
| CODE YOU RECEIVE | Full source: hub, worker, phone app, tooling, docs | Edge package only | The app |
| APPS | All supported | All supported | Reddit, Threads, X, TikTok, Telegram |
| ALERTS AND AI | Yes, on your own keys | Coming to hosted hubs | Coming to hosted hubs |
| UPDATES | You pull them from git | We ship them | The app updates itself |
| YOU NEED | Someone comfortable with Node.js, Python and a terminal | A computer that stays on, phones on a powered USB hub | An Android 11+ phone and a pairing code |
| BEST FOR | Teams with an engineer who want full control | Operators who have phones and don't want to run servers | A first try, or a phone far from any PC |
No — start with the phone app. Yes — read on.
No — a hosted hub keeps that on our side. Yes — read on.
Yes — take the full source. Not sure — ask us; you can start with one phone and move up later.
Tell us how many phones you run and where they are. We'll suggest a setup.
Request access