Residential proxy

Our network is 100% built on consent.

Every IP in our pool comes from a real person who knowingly agreed to share their device's internet connection. This is done through apps we partner with. In exchange for using a premium feature or an ad-free experience, a user gives permission for their device to be used as a proxy node, but only when it's idle and connected to Wi-Fi.

This is a clear, opt-in process designed to comply with privacy laws like GDPR and CCPA. We don't touch their personal data. For you, this means you're using a legitimate, ethically sourced network, which keeps your data operations clean and your company's reputation safe.

The difference is all about trust and origin.

• Datacenter proxies: These IPs come from servers in a commercial data center. They exist in large, sequential blocks. Advanced anti-bot systems on sites like Google or Amazon spot these server IPs instantly and either block them or throw up CAPTCHAs. They're cheap for a reason.
• Residential proxies: These are real IP addresses assigned by Internet Service Providers (ISPs) to homes. To a target website, a request from our network looks exactly like a request from a regular person browsing the internet. It's nearly impossible to tell our traffic from a normal user, which means dramatically fewer blocks and more reliable data.

It's a common myth that they're "slower." While a single request might have slightly higher latency than a datacenter proxy, the overall job gets done much faster.

• With datacenter proxies, you might send 1,000 requests and get 400 blocks and 200 CAPTCHAs. Your scripts then have to handle all those errors, retry failed requests, and manage a list of burned IPs. The whole process drags on.
• With our residential proxies, you send 1,000 requests and 998 of them succeed on the first try.

The job gets done faster, with fewer headaches.

No special connector needed. We were built for flexibility.

You get a standard HTTP(S) proxy endpoint that works with virtually any software or programming language. If it can send a request through a proxy, it can use our service. This includes:

• Languages: Python (with requests or Scrapy), Node.js (with Axios or Puppeteer), Java, Go, etc.
• Tools: cURL, Selenium, Playwright, and all major scraping tools.
• Data warehouses: For platforms like Snowflake or BigQuery, you simply route your API calls through our proxy endpoint in your ETL scripts.

Our documentation has code snippets to get you started in minutes. We stick to the universal API approach because it works with everything and doesn't lock you into a specific stack.

We guarantee 99.9% uptime for our gateway in our Service Level Agreement (SLA). If availability ever dips below that, you get service credits for your next billing cycle. Our team monitors the network, and when a major target domain starts causing problems, we rotate the IP pools automatically to keep your success rate high and your operations running smoothly. Support is available on business days, during Polish business hours (CET/CEST).

All traffic between your system and our gateway is fully encrypted using TLS 1.3. Your activity is yours alone: our multi-tenant architecture keeps each client's data and configuration completely isolated. We do not log the content of your requests or the data you get back. Only the metadata needed for billing and support is stored, like timestamps and bandwidth used, for a period you agree with us. If you want an extra layer of security, you can also whitelist specific IP addresses so that only your servers can use your plan.