Develofly Autopilot
Autopilot › Features › Parallel runs

One bot, many rows at once.

Feed a bot a spreadsheet and run many rows at the same time — each row in its own browser, as many threads as your plan and your computer allow.

Rows in, rows at once

When a bot has a data file, it runs once per row. The Threads setting in a project's Run settings decides how many of those rows run at the same time: one after another, or many side by side, each in its own browser. A price check over 500 products stops being an afternoon and becomes a coffee break.

The limits are your plan — and your computer

Free runs 1 thread. Pro and Agency have no thread limit in the app — the limit is your computer: each thread is a real browser and uses real memory (the app counts about 350 MB per browser thread), so if you ask for more than your computer's processor cores and free memory can handle, Autopilot puts a note under the Threads setting — and a warning in the run log — suggesting a safer number. Threads are saved per project, so a heavy collector and a gentle monitor each keep their own setting.

Each thread keeps its own place

A thread keeps the bot's browser profile for the whole run, so logins and cookies stay steady per thread. Give a bot a profile pool and each thread takes its own profile — one identity per thread. If you give the bot a proxy list, threads take turns through it (thread 1 uses proxy 1, thread 2 uses proxy 2, and so on), and a row that is retried moves to the next proxy. A row that fails gets its extra attempts in a fresh session, and its failure — with a screenshot of the page at that moment, if you've left that on — is recorded in the results like any other row.

Pairs with Data in, results out (the rows themselves) and Proxies (one address per thread).

Run settings with Threads set to 3, the safer-number note, and the Agency plan's unlimited-threads note

Threads set to 3. The note underneath is the app being honest about this computer: 3 threads may be more than it can handle, and about 1 would be safer here. The plan itself sets no limit.

A run starting on 3 threads, with each thread taking its own browser profile from the pool

A run starts on 3 threads, and each thread takes its own browser profile from the pool — Book Scout, Catalog Checker, Shelf Scanner — so each row's login stays its own.

The run log mid-run: rows from three threads interleaved, finishing out of order

Mid-run: the log interleaves all three threads, and rows finish out of order as their pages load — row 3 done before row 2, because they really are running side by side.