Using Webshare and Geonode Together: The Best of Both Proxy Providers

Why use two providers?

Webshare and Geonode are strong in different places. Combining them lets you buy each product where it's best value, and gives you redundancy if one network has a bad day on a target.

Who does what

Adjust after testing on your targets.

A shared proxy helper

Keep one module that knows both providers, so the rest of your code asks for a job type, not a provider:

import os, random

WS_DC = [l.strip() for l in open("webshare_dc.txt") if l.strip()]

def ws_dc():
    ip, port, u, p = random.choice(WS_DC).split(":")
    return f"http://{u}:{p}@{ip}:{port}"

def gn_res(session=None):
    # Build from Geonode's documented username format (dashboard endpoint generator)
    return os.environ["GN_RES_URL"] if session is None else os.environ["GN_RES_STICKY_URL"].format(session=session)

HARD = {"bigshop.example", "travel.example"}  # domains that need residential traffic

def proxy_for(host, session=None):
    return gn_res(session) if host in HARD else ws_dc()

Failover

Add a fallback per route: if a domain's success rate on its primary provider drops below a threshold for a period, switch it to the other provider automatically and alert someone. Switch back after a cool-down and re-test.

Monitoring

Track per domain and per provider:

• Success rate (content-verified).
• Latency (p50 and p95).
• Bandwidth or requests used.
• Cost per 1,000 successes.

Review monthly and move domains between providers when the numbers change.

Costs and credentials

• Keep credentials for each provider in a secrets manager, separated by project.
• Set spend alerts on both.
• Use Geonode's non-expiring balance for irregular residential needs and Webshare's subscriptions for steady per-IP needs.

When one provider is enough

If nearly all your targets are lenient, Webshare alone may do. If nearly everything needs residential, Geonode alone may do. Two providers make sense when your work is mixed or critical.

Rollout plan

Avoiding double spend

Assign each job to one primary provider, size plans to that job, and keep the secondary provider's capacity small (a modest non-expiring balance or a small list) for failover. Review both invoices together each month.

Documentation

Write down which domains go where and why, with the date of the last test. When a teammate wonders why a domain uses a particular provider, the answer is in one place.

Signs your two-provider setup is working

• Cost per 1,000 results falls or holds steady as volume grows.
• Incidents at one provider cause slowdowns, not outages.
• Domain routing changes are rare and data-driven.

A real-world example

A company runs 80% of its scraping requests through Webshare datacenter lists, 18% through Geonode residential and 2% through Geonode's Scraper API. When Geonode residential had a brief slowdown on one target, the router shifted that target to Webshare residential for an hour, then shifted back. When Webshare's list hit its thread limit during a spike, overflow went to Geonode datacenter traffic. Neither event caused a missed delivery.

Before you commit to any provider, it helps to see the wider market: our guide to the best proxies in 2026 compares proxy types by job, and cheap proxies explains how to keep costs down without buying IPs that get blocked.

Key takeaways

• Using both lets you buy each product where it's best value and adds redundancy.
• Typical split: Webshare for datacenter and account IPs, Geonode for residential and scraping APIs.
• Hide providers behind one routing function and keep routes in config.
• Add failover and per-provider monitoring.
• Review routing and invoices together monthly to avoid double spend.

FAQ

Is it worth the extra complexity to use both?

For mixed workloads, usually yes: the savings and redundancy outweigh a small amount of routing code.

Can I use both in one browser automation setup?

Yes. Playwright and Puppeteer let you set the proxy per context or browser.

How do I decide which provider gets a domain?

Test both on the domain and choose the lower cost per successful result.

Do I need separate accounts for each provider?

Yes, one account with each provider, managed from your own routing layer.

How do I keep costs visible across two providers?

Track cost per 1,000 results per provider and review both invoices together.

Can I start with one provider and add the other later?

Yes. Put proxy selection behind one function from day one, and adding a provider later is simple.