Residential IP proxy with full transparency.
What it is
iogrid Proxy is a residential-IP proxy network whose providers run the iogrid daemon on their home PCs and Macs and have consented to share bandwidth on a per-category basis. Your traffic exits from a real ISP-issued IP in the geography you ask for.
Unlike legacy networks, every byte is logged at the coordinator against a category and customer ID. Providers can audit what is running through their connection and block by category, by customer, or by destination at any time without uninstalling anything.
How it works
Connect over SOCKS5 / HTTPS CONNECT
Point any HTTP client that speaks SOCKS5h or HTTP CONNECT at proxy.iogrid.org:443. Authenticate with your API key. Pass region and session preferences as connect headers.
Router picks a provider
The workload-router picks an opted-in provider matching geo, category eligibility, recent uptime, and reputation. The session is sticky to the same provider for up to 30 minutes.
Request egresses from a real residential IP
Your request traverses a WireGuard tunnel into the provider's home network and out their ISP. Bytes in and out are metered at the coordinator for both billing and the per-byte audit log.
Pricing
| Per GB | $0.30 – $0.60 |
| Geo-targeting (country) | Included |
| Geo-targeting (city) | Included |
| Session stickiness | Up to 30 minutes |
| Audit log retention | 90 days, downloadable |
| $GRID discount | 20% off list price |
Reference: Bright Data retail $5–20/GB, Honeygain/Pawns $5–15/GB. iogrid is deliberately 10–30× cheaper because provider payouts can be in free VPN or $GRID, not just cash.
What you can do with it
E-commerce price monitoring
Pull product pages from a residential IP that does not trigger the rate limits and CAPTCHA walls reserved for datacenter ranges. Geo-target the country for region-specific pricing.
SEO / SERP scraping
Query search engines from real consumer IPs across regions. Session stickiness lets you carry cookies through a multi-page result without rotating partway.
Ad verification + brand safety
Render ad placements as they appear to actual users in a target country. The audit log gives you a cryptographic record of which IP saw which creative, useful for compliance reporting.
Get started
Any HTTP client that speaks SOCKS5h works without changes. The SDK adds session management, retries, and audit-log lookup.
# SOCKS5 with a session pinned to a US-East provider
curl -x socks5h://USER:PASS@proxy.iogrid.org:443 \
-H "X-Iogrid-Region: us-east-1" \
-H "X-Iogrid-Session: campaign-q4-watch-42" \
-H "X-Iogrid-Category: e_commerce" \
https://www.example.com/product/42import { IogridClient } from '@iogrid/sdk';
const iogrid = new IogridClient({ apiKey: process.env.IOGRID_API_KEY! });
const w = await iogrid.createWorkload({
type: 'BANDWIDTH',
priority: 'HIGH',
bandwidth: {
targetUrl: 'https://www.example.com/product/42',
method: 'GET',
preferredRegion: 'us-east-1',
category: 'e_commerce',
sessionId: 'campaign-q4-watch-42',
},
labels: { campaign: 'price-watch-q4' },
});FAQ
- What categories are allowed?
- E-commerce, SEO, ad verification, AI training data, threat intelligence, brand protection, and travel aggregation by default. Lead-generation scraping on LinkedIn-style surfaces, social-media intelligence, and political influence operations are blocked at the gateway. Providers can opt in to additional categories.
- What does the per-byte audit log show?
- Per-request: timestamp, customer ID, destination domain (not URL), category, byte counts, and the eligible-categories signature. The coordinator cannot decrypt customer HTTPS payloads — the log is a routing record, not a content log.
- How is this different from Bright Data or Honeygain?
- Same architecture, but providers see and can revoke their participation per category, per customer, and per destination. Pricing is 10–30× under Bright Data ($5–20/GB retail). Providers can also choose free VPN or charity payouts instead of cash.
- Will my IPs get banned?
- Residential IPs are not pre-flagged the way datacenter ranges are. That said, abusive traffic patterns can earn a per-destination ban — the audit log helps you spot it before it happens, and the scheduler avoids over-using a single provider.
- Is the protocol authenticated end-to-end?
- Yes. Customer-to-coordinator is TLS. Coordinator-to-provider is WireGuard. Provider-to-destination is whatever the destination negotiates (typically HTTPS). No party other than you and the destination sees the request body.