GORAFARM / PLATFORMHOW IT WORKS

Four layers.
One job each.

Phones do the tapping. The worker drives them. The hub decides what happens next. The admin shows you all of it, for every farm you run.

Each layer can live where it suits you: everything on your own machine, the hub on our site, or a single phone talking to our hub through the Farm Phone app.

01 / ARCHITECTUREThe stack

L1 · USB / ADB · HTTPS

Phones

Real Android devices with real apps. On USB, the worker drives them through ADB and Android's own UI automation. With Farm Phone, a single phone takes its commands from the hub over HTTPS instead — no cable, no computer.

Every phone's screen can be opened in the browser and watched live.

L2 · QUEUE

Worker

A Python service next to the phones. Three parallel slots, one task per phone, the queue checked every 8 seconds. Each task works from a map of the app's screens recorded on real devices, and stops instead of guessing when a screen doesn't match the map.

L3 · SCHEDULE · LIMITS · DATA

Hub

The brain of a farm: a server with its own database and web panel. It turns each profile's weekly plan into queued tasks every 5 minutes, enforces the limits, runs the AI steps, keeps the journal and sends the alerts.

L4 · YOU

Admin

admin.gorafarm.com puts every farm behind one Telegram login: each hub's panels, its switches and its phone screens in one place.

02 / ONE TASK, START TO FINISHA task's life

What happens between a plan on the calendar and a line in the journal.

  1. EVERY 5 MIN

    Planned

    The hub queues the next tasks from each profile's weekly plan, inside its active hours and outside the farm's quiet window.

  2. EVERY 8 S

    Picked up

    A free worker slot claims the next task for a free phone. Limits are checked before anything moves.

  3. ON THE PHONE

    Run

    One task on one phone, start to finish. Consequential steps run as a dry run until you switch them to live.

  4. AFTER

    Recorded

    Result, log lines and AI cost go into the journal. An unknown screen is captured so it can be explained and mapped.

  5. IF NEEDED

    You hear

    A failure, a cooldown or a parked phone sends a Telegram alert. Otherwise you get one digest a day.

03 / SCHEDULE AND LIMITSPaced, per phone

PLAN
A weekly plan for every profile
CLOCK
Its own time zone and active hours
QUIET WINDOW
A farm-wide pause at night, set by you
CAPS
Daily, rolling 24-hour and hourly
PUSH-BACK
When an app warns, the phone cools down or parks until a person looks
NEW STEPS
Start as a dry run; go live when you say so

04 / SEEING AND KNOWINGNothing happens out of sight

Live screens

Open any USB phone's screen in the browser while it works.

Telegram alerts

Failures, cooldowns and parked phones, the moment they happen.

Daily digest

One message a day: what needs hands, or that all ran smooth.

Journal

Every task with its result and log, every AI call with its cost.

Cockpit

Ask why a profile went quiet and get the reason, not a guess.

Unknown screens

Captured on the spot and explained by AI, so the map can be fixed.

05 / AIAI where it helps, on your key

  • Captions and images drafted for posts and checked before they go out.
  • Replies and comments written in the profile's voice, then checked.
  • Screen triage explains a screen the map didn't know.
  • Cost per task every call is logged with what it cost. Bring your own key.

Choose where each layer lives.

See the three setups What it runs