NetNut

NetNut routes the residential rotating pool through a hybrid architecture: an ISP-direct component via DiviNetworks sits alongside a P2P component. The ISP-direct portion routes through servers at ISP network connectivity points that NetNut controls directly via DiviNetworks — no third-party device availability dependency exists for that component. The P2P component operates through the standard peer-sourcing model. The rotating pool is not fully ISP-direct, a distinction relevant to teams evaluating this architecture for network stability reasons.

Per-request and per-session rotation are both documented. Sticky sessions are available. Sticky session TTL is not published in the FAQ. Unlimited concurrency is documented. Rotation configuration uses proxy URL parameters — API-level rotation configuration details are not found in the FAQ. Country targeting is available on all plans. City and state targeting are plan-gated to the Master plan at $4,000/month — this is not a configuration limit, it is a billing-tier product restriction.

IP allowlist authentication is available on Production plan and above — it is not available on Starter. API access is documented but plan-gated to Master only. Bandwidth increases beyond plan limits require contacting an account manager — no self-serve top-up is documented. Service pauses at plan limit with no auto-billing at penalty rates. Support channels include WhatsApp, Telegram, Messenger, email, and live chat — live chat is available on Production plan and above; Starter plan is email-only.

NetNut's structural differentiator is the ISP-direct sourcing model. B2B commercial agreements with ISPs via DiviNetworks replace consent-based SDK sourcing models. The practical implication: the ISP-direct component does not depend on end-user devices being online, which is the primary source of availability variability in P2P residential networks. The failure rate is stated at less than 1% on the FAQ — this is a self-reported figure, not an independently verified benchmark.

The compliance posture is less documented than the architecture. EWDCI membership is not documented in evidence. ISO 27001 certification is not documented. KYC vetting is applied to peers, partners, and customers — stated on the About page. There is no dedicated GDPR compliance page in evidence. For teams for whom the ISP-direct sourcing model itself satisfies ethical sourcing concerns — because it uses B2B commercial agreements rather than user consent — the compliance framing shifts. For teams that require specific certifications, the documentation gap is real.

NetNut's pricing structure is subscription-only with a $300/month minimum. This is not a trial-friendly entry point. The 7-day trial requires KYC verification and sales contact — an instant self-serve trial is not available. Teams evaluating whether the ISP-direct architecture delivers meaningful network stability improvements for their specific targets will need to commit to the trial process before getting data.

The rotating residential pool is reported at 85M+ IPs across 200+ countries — self-reported, no independent audit referenced. The ISP static pool is reported at 1M+ IPs in 50+ countries. Mobile proxies cover 5M IPs across 100+ countries with 3G/4G/5G coverage and carrier targeting; total carrier count is not published. Datacenter proxies include 150K+ IPs in 200+ countries in shared and dedicated formats. Country-level targeting is available on all residential plans. City and state targeting are available on the Master plan only — a $4,000/month subscription tier.

Rotating and sticky sessions are both confirmed. Sticky session TTL is not published. Unlimited concurrency is documented. ASN and ZIP targeting are not documented. IP allowlist authentication is plan-gated to Production plan and above. API access is plan-gated to Master plan — lower tiers have no programmatic API access. HTTP(S) protocol is documented. SOCKS5 documentation is not differentiated separately in evidence.

The static ISP pool is reported at 1M+ IPs in 50+ countries. Static ISP proxies have 24/7 availability stated and a documented 99.9% uptime. ISP static coverage at 50+ countries is substantially narrower than the residential 200+ country footprint. No public status page or incident tracker is documented in evidence.

Rotating residential plans are subscription-only, ranging from Starter at $300/month (20 GB) through Master at $4,000/month (1 TB). PAYG is not available — every plan requires a monthly bandwidth commitment. City and state targeting, IP allowlist, sub-user management, and API access are all plan-gated to Production plan ($1,200/month) or Master plan ($4,000/month) depending on the feature. Unused monthly bandwidth does not roll over. Bandwidth increases require account manager contact — no self-serve top-up is documented.

The 7-day free trial is available for registered companies that pass KYC verification — an instant self-serve trial is not documented. The trial requires sales contact. Custom and enterprise plans require sales contact above documented tiers. The cost jump from Production ($1,200/month) to Master ($4,000/month) to unlock city targeting and API access is a structural pricing cliff — teams that need those features cannot access them at mid-tier spend levels.

You gain an ISP-direct routing architecture that reduces dependency on peer-device availability for the ISP-direct pool component. The 1M+ ISP static pool provides a large static IP set for use cases that require dedicated IPs. A failure rate of less than 1% is stated on the FAQ. Multi-channel support including WhatsApp, Telegram, and Messenger is documented. A dedicated account manager with remote integration sessions is available on the Master plan.

You give up PAYG — there is no option below $300/month. City targeting requires $4,000/month. API access requires $4,000/month. IP allowlist requires at least Production tier. Live chat requires at least Production tier. The rotating pool is hybrid ISP+P2P, not purely ISP-direct. EWDCI membership and ISO 27001 are not documented. The trial requires KYC and sales engagement — instant self-serve testing is not available. Unused monthly bandwidth does not roll over. Bandwidth overages require account manager contact rather than self-serve top-up.

• ISP-direct routing architecture is a specific technical requirement for your use case — you need the reduced peer-device variability that the DiviNetworks ISP-direct component provides
• Your monthly residential spend exceeds $300/month and the subscription model fits your budget cycle
• The 1M+ ISP static pool in 50+ countries is a primary product requirement for your use case — static dedicated IPs at that pool scale are the core product
• Country-level targeting is sufficient for your residential use case — city and state targeting are not required
• Your team operates at Master plan spend and needs a dedicated account manager with remote integration support

NetNut's constraints are structural, not incidental:

• You need city or state targeting on residential proxies without spending $4,000/month — that targeting level is hard-locked to the Master plan tier
• You need API access to manage proxies programmatically at any plan below Master — API access is plan-gated to Master only
• Your budget is below $300/month or variable — PAYG does not exist; the minimum monthly commitment is $300
• You need to test the network quickly before committing — the 7-day trial requires KYC verification and sales contact; instant self-serve trial is not available
• Your compliance review requires EWDCI membership or ISO 27001 — neither is documented in public evidence for NetNut

If NetNut's plan gates, minimum commitment, or certification gaps don't fit:

• Oxylabs — ISO 27001:2022 and SOC 2 Type 2 with city/state/ZIP/ASN targeting available on standard plans without a $4,000/month requirement; fits if compliance certification and targeting depth are both required
• SOAX — ISP-level targeting on residential proxies, transparent subscription tiers from $90/month, and no advanced feature plan-gating; fits if ISP targeting is the requirement without the ISP-direct architecture
• Infatica — full targeting depth including ASN with PAYG available and no $300/month floor; fits if targeted flexibility and a lower entry point are the primary constraints

Use NetNut if the ISP-direct routing architecture is a specific technical requirement, if your team spends at a level that justifies the $300/month minimum, and if the 1M+ ISP static pool is a primary product need. Skip it if city targeting, API access, or IP allowlist are required without committing to $1,200–$4,000/month — those features are plan-gated at tiers that exceed what most small and mid-scale operations can justify.