How Geonode fits a sneaker setup
Sneaker setups use proxies in distinct roles, and each role has a natural Geonode product:
| Role | What it needs | Geonode product |
|---|---|---|
| Raffle entries | A unique IP per entry, right country | Rotating residential |
| Account creation and logins | Trusted IPs, consistent per account | Sticky residential |
| Checkout tasks | Speed and a stable IP for the whole flow | ISP proxies |
| Monitors | Many cheap requests | Rotating datacenter |
The appeal of Geonode for cooks is flexibility: residential bandwidth is billed per GB and doesn't expire, so raffle seasons that come in waves don't waste a monthly plan, and ISP and datacenter products sit under the same account. Our pillar guide on sneaker proxies covers the theory; this guide is the Geonode-specific setup.
Raffles with rotating residential
Raffles check for duplicate entries using several signals, including IP. Rotating residential gives every entry a fresh consumer IP from the target country.
- Targeting: match the raffle's country, and state or city if the retailer checks location against the profile.
- Session: rotate per entry for simple form submissions; use a short sticky session if the entry involves several pages or a login.
- Bandwidth: request-based entries use very little. Browser-based entries use more, so block images where your tool allows.
Generate a list of endpoints in the Geonode dashboard, one line per entry, in the host:port:username:password format most bots accept.
Accounts with sticky residential
Account creation and logins are scrutinised. Use a sticky residential session per account, long enough to complete the flow (Geonode lists sticky sessions of up to 24 hours), from the region the account will shop in. Create accounts gradually and keep each account's location consistent over time.
Checkout with ISP proxies
For FCFS releases, speed and stability matter most. Geonode ISP proxies are static IPs registered to ISPs, with unmetered bandwidth, available shared or dedicated. For hyped releases, dedicated IPs avoid competing with other customers on the same addresses. Ask which regions and subnets are available, and test against your target sites the night before.
Many cooks combine a general provider's ISP proxies for regular drops with specialist sneaker batches for the most hyped releases. That's a sensible approach: use Geonode for raffles, accounts, monitors and everyday checkout, and add specialist batches when your results justify it.
Monitors with datacenter traffic
Monitors poll product pages or endpoints constantly. Rotating datacenter traffic spreads those requests across many IPs cheaply on sites that allow it. Keep monitor proxies completely separate from checkout proxies.
Proxy tip: You can try every step in this guide with a small balance: Geonode bills residential bandwidth per GB with no expiry, so testing costs very little. See our complete Geonode guide for the full product overview.
Setting up in your bot
- In the Geonode dashboard, generate endpoints for each role with the right country and session type.
- Export them in
host:port:username:passwordformat. - In your bot, create proxy groups by role and site: "Raffle Resi UK", "Accounts Resi US", "ISP US East", "Monitor DC".
- Import each list into its group.
- Run one proxy test per group against the actual site, not a speed test site.
- Assign groups to tasks.
If your bot supports IP whitelisting and your server has a fixed IP, you can whitelist it in Geonode and drop credentials from the list. See sneaker proxy setup guide.
Pairing with a server
Run your bot on a server in the same region as your ISP proxies and near the retailer's infrastructure. For residential exits, target the state or city nearest your server when location doesn't otherwise matter. See sneaker bot server location.
A season budget with Geonode
- Residential: count expected raffle entries and account logins for the season, estimate data per entry, add 30%, and buy that balance once. Leftovers carry into the next season.
- ISP: buy monthly proxies for regular drops and account maintenance; add specialist dailies for big releases.
- Datacenter: a small amount for monitors.
- Track cost per checkout after every release.
See cheap sneaker proxies for more budgeting tips.
Rules and risks
Bots and multiple entries usually break retailers' terms, and retailers cancel linked orders and close accounts. Proxies don't change that. Choose providers with clear sourcing, protect your credentials, and be wary of scams in the sneaker scene. See sneaker proxies for safety advice.
A first-release checklist with Geonode
- Residential endpoints generated for raffles, targeted to the raffle's country
- Sticky residential endpoints for account logins
- ISP proxies imported and tested against the target site the night before
- Datacenter traffic set up for monitors, kept separate
- Bot server in the same region as the ISP proxies
- Results logged after the release, per proxy group
Once that works for one release, scale the parts that produced results and drop the parts that didn't.
FAQ
Which Geonode product is best for sneaker checkouts?
ISP proxies, for speed and a stable IP throughout checkout. Use dedicated IPs for hyped releases.
Can I use Geonode residential proxies for raffles?
Yes. Rotating residential with country targeting gives each entry its own IP, and non-expiring bandwidth suits seasonal raffle activity.
Do Geonode proxies work with my sneaker bot?
Most bots accept proxies in host:port:username:password format, which Geonode's dashboard generates. Check your bot's documentation for site-specific advice.
Should I use Geonode for monitors?
Rotating datacenter traffic works for monitors on sites that allow it. Keep monitors separate from checkout proxies.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.