Account Creation mode

A machine in Account Creation mode doesn’t stream: it is the dedicated machine (run by the operator) that builds accounts for all streaming machines, continuously (24/7), then delivers them encrypted. Since centralization, streaming users no longer pick a mode: they request, the creator produces and delivers.

Operator-only page

Account creation is centralized: it is handled by the Botify operator on a dedicated machine. As a streaming user you have no creation machine to install — accounts reach you automatically. This page describes the creator’s internal workings.

Why a dedicated machine

• IP consistency — an account must be created through the same proxy it will use to stream. The creation machine therefore creates each account through the exact proxy requested.
• Load — a signup (with captcha) is heavy; isolating it avoids penalising streaming.
• Privacy — accounts never stay local: they leave encrypted for their recipient.

The account creator

The Créateur (Creator) screen supervises account production. It runs continuously (24/7) once started, with no intervention: it consumes the requests from all streaming machines and delivers accounts to them.

• Automatic operation — no more “workers” or “max/day” settings here: the number of accounts created in parallel scales on its own with demand, and the daily cap is set by each streamer (Accounts page), not on the creator.
• Captcha key — it comes from each streamer (see below): the creator automatically uses the client’s key for the accounts it creates for them. Nothing to enter on the creator side.
• Hourly planner — a chart shows, hour by hour, the real number of accounts planned for the day, based on received requests (spread across each proxy’s local peak hours, never exceeding each machine’s individual cap).
• Demandes en attente (Pending requests) — table of the needs reported by streaming machines (per machine + proxy: requested / delivered / remaining).
• Accounts delivered today — counter of the total delivered over the day.

Captcha service (provided by the streamer)

A captcha is required at every signup. Since centralization, each streaming machine provides its own captcha-solving key: it is sent encrypted with each request, and the creator uses it to create that client’s accounts (the client pays for their own usage).

On the streaming side, each user:

1. Creates an account with the captcha service and funds their balance (prepaid, a few euros).
2. Copies their API key.
3. Pastes it into Botify → Settings → CapSolver. The balance is displayed; below $0.10 (or with no key), a red alert appears and that machine’s requests are paused.

Budget roughly ~$0.002 per account created. Without a key/balance on the streamer side, no account is created for that machine.

Guarantees

• An account is only created if it’s valid: after signup, it is tested through its SOCKS5 proxy. A non-working account is neither counted, nor delivered, nor deducted from the quota.
• No over-creation: the need is recalculated server-side; when a proxy is full, creation stops.
• Per-machine cap: the run honours each machine’s own daily cap and retries failures until it delivers that maximum of valid accounts, or until demand is exhausted.

Machine fleet (supervision)

On the creation machine (central creator), the dashboard shows all running machines, across all users (each row shows its owner).

• Header: machines online · workers playing (fleet) · accounts created today (fleet).
• Two tables (the roles don’t share the same columns):
  • Streaming: State · Playing · Streams · “Mes sons” (My Tracks) · Accounts · Received (today) · Last sync — “Received (today)” = accounts created and sent to that machine today.
  • Creation: State · Creating · Created today · Last sync.

Freshness: streaming and creation push their telemetry regularly. “Online” = recent sync.

See Distribution for the full flow.