SIKRID Legion Control — One Dashboard to Run 300+ Phones

Why we built it

If you've ever tried to run a TikTok script on ten phones at once, you know the problem: ADB drops, IPs collide, half the accounts hit captcha at the same time, and you have no idea which phone is doing what. Doing this with 300 phones isn't ten times harder — it's a whole new problem class.

Legion Control is what we wrote to solve that problem for ourselves. It's the thing we open every morning before the kettle finishes boiling. It started as our internal tool — we made it a product because customers kept asking for the dashboard, not just the phones.

What you actually see when you log in

The first page is an overview — how many phones are online right now, how many jobs are running, how many alerts you need to look at. Like the dashboard in a car: not everything, just the things that matter when you're moving.

From the sidebar you jump to each module. We have separate screens for the things that need different rhythms — posting is once a day, feed watching is continuous, going Live is event-driven, billing is monthly. Mixing them all into one giant queue made every screen worse, so we split them.

The modules in plain Thai

• Devices — the address book of your farm. Every phone has a row: which IP it sits on, which TikTok account it owns, when it last checked in. If a phone falls off the grid, this is the first place you look.
• Auto Post — drag in a clip, write a caption, pick the phones that should post it, set the time. The system staggers the uploads so 100 phones don't shove the same clip onto TikTok at the same second.
• Feed Watch — your accounts watch TikTok like a real human does. Scroll a bit, watch for a bit, swipe past the boring ones. Without this, an account that only posts and never watches looks like a poster bot — and the algorithm treats it as one.
• Auto Comment — comments come from a template pool you control. Add a Thai female suffix here, a male one there. The system picks variations so no two phones leave the same comment in a row.
• Live Comment — drop into a creator's Live, hang around, comment, send stars. Useful for boosting your own Live or for engaging the niche communities your brand cares about.
• Following — follows by list, with a guard that stops ten of your phones from chasing the same target at once. That accidental swarm is what trips bans, and we got tired of cleaning up after it.
• Proxy — your proxy wallet. Drop in HTTP or SOCKS5 addresses, the system pins each one to a phone or rotates them per session. The phones never see each other on the wire.
• Captcha — when TikTok throws a slider or a puzzle at one of your phones, the system pings our solver service and pastes the answer back. You top up credits like phone airtime.
• Schedules — cron jobs without the cron syntax. Warm accounts in the morning, run engagement at lunch, post at night.
• Billing — usage-based, in Thai baht, PromptPay or card. You see what you spent, on what, this month. No surprise bill.

Under the hood — three layers, not one

We tried hard to make this a one-piece system early on, and it kept breaking. The internet in a farm isn't stable enough for the cloud to talk to every phone directly. So we split it: a cloud brain that holds all the state, a small agent program on a Windows PC inside the farm, and the phones themselves.

• Cloud — the source of truth. Where your jobs, accounts, schedules and bills live. Built on Next.js + Postgres so it's boring and stable, which is exactly what you want from the brain.
• Agent — a small program on the Windows PC in your farm. It picks up jobs from the cloud over a websocket and pokes the phones through USB. If the cloud loses internet for ten minutes, the agent keeps the current jobs alive.
• Device APK — the helper that runs on each phone. Uses Android's Accessibility service to tap, type and scroll the way a finger would. Not a script that pokes at coordinates — a program that actually reads the screen.

What it solves on a real day

Before Legion, our morning routine looked like this: walk to the rack, count phones that lost ADB overnight, plug things back in, reboot the half that hung. Two hours of janitor work before any real work started.

After Legion, the same morning is: open the dashboard, see the red dots, click reconnect on the ones that need it, batch a restart on the few that are truly stuck. Twenty minutes, coffee in hand.

That gap — two hours to twenty minutes — is the whole product. Not the fancy graphs, not the AI captions. Just less janitor time, more strategy time.

Who it's for

If you're running fewer than about 50 phones, you don't need this — you can manage with a notebook and a kanban board. The pain that justifies a system like Legion starts somewhere between 50 and 100 devices, when you stop knowing each phone by name.

Above 100, you don't really have a choice. You either build a Legion of your own or you stop scaling. We chose to build one and sell access to it so other people don't have to.

FAQ