Proxies for BAS
A pool of private IPv4 and SOCKS5 for BAS.
Proxy plans for BAS
Every plan includes IPv4 and SOCKS5 together, at no extra cost.
Threads are simultaneous connections. The more threads, the higher the parallel load your software can handle.
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 1,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Pool of 12,000-15,000 IPs
Address rotation
Unlimited traffic
Up to 3,000 threads
Proxy catalog for your task
Why BAS needs proxies
BAS, or BrowserAutomationStudio, is a visual builder for creating bots without deep coding. In multi-threaded scenarios every thread runs from one address, so sites quickly answer with a captcha and speed drops.
BAS launches a separate browser per thread, so the address attaches to the thread and lives alongside it. That suits work needing a standing exit per profile, and it demands address headroom wherever thread counts run high.
Features of proxies for BAS
BAS (BrowserAutomationStudio) runs bots across many browser threads, and each thread must exit from its own IP, otherwise the platform sees one source and cuts the whole scenario. BAS threads need a pool, not one address.
The pool hands over private IPv4 by HTTP, HTTPS or SOCKS5, as IP:PORT bound to your address or IP:PORT:LOGIN:PASS. Each thread gets its own exit along with its browser, so address count follows concurrent threads rather than the queue.
What proxies you need for BAS
| Protocol | HTTP, HTTPS or SOCKS5 |
|---|---|
| How it is set | per thread, alongside the browser |
| What to count | concurrent threads |
| Format | IP:PORT or IP:PORT:LOGIN:PASS, access always by binding |
| List refresh | every 15 minutes |
| Authorisation | by binding your own IP in settings, up to 2 addresses |
How many proxies BAS threads need
A browser per thread means the number of exits you need equals the number of concurrent threads, not the number of jobs queued up. Headroom matters because some addresses may be busy with your own other threads at launch time, and the load then skews.
Which format to supply depends on how authentication is arranged in the template. You can bind up to two of your own addresses and change them without limits.
One note on long scenarios. The list refreshes every 15 minutes, so if a thread outlives that, pin its address explicitly rather than re-reading the list mid-session: switching exits inside a session behind a login reads as a hijacked account. That logic is unpacked on the page about multiaccounting.
- You need as many exits as concurrent threads
- Headroom keeps threads from sharing one address
- For long sessions the address is pinned explicitly
- Switching exits inside a login session reads as a hijack
How to connect proxies in BAS
To make the pool work, bind the IP of the machine running your proxy software in the settings, a server or a home PC, no binding means no access. The primary output format is IP:PORT, with an additional IP:PORT:LOGIN:PASS for programs that require a login and password.
In BAS proxies are set via the Proxy node or the resource manager: the address list is loaded in IP:PORT format, type HTTP or SOCKS5, and handed out across scenario threads.
Before launch the setup is checked on a couple of threads. How many addresses you need for your BAS thread count is visible on the free test before buying.
How to buy proxies for BAS
The process is simple. Register in the dashboard and request a free test up to 2 hours, bind your IP and message the operator in a ticket to check the setup with BAS on your own tasks.
When everything fits, pick a package by number of threads and term, pay in cryptocurrency, and access opens right after payment. The test is provided once before purchase, and support replies in a ticket.
FAQ
Will these proxies work with BAS?
BAS accepts proxies as a list in HTTP, HTTPS and SOCKS5, which is our IP:PORT format. The exact fit for your threads is visible on the free test.
How many threads can I run?
The number of simultaneous threads and bindings depends on the chosen package, and the pool of 12,000-15,000 IPv4 gives threads separate addresses.
Which protocol should I choose, HTTP or SOCKS5?
For most scenarios in BAS both fit; SOCKS5 is handier for non-standard connections. You can test both and keep the one that runs smoother.
See also: proxies for Selenium, proxies for Puppeteer, proxies for Python scripts, proxies for ZennoPoster, proxies for AMS Enterprise, proxies for A-Parser, proxies for ChatGPT, proxies for anti-captcha and checkers, full catalog
© WinGate · source of the material · wingate.me/en/proxy/bas-proxy