We don't publish customer names. People who run scrapers, fraud-prevention testing, or rotating proxy pools generally don't want their company on a marketing page next to their use case. So instead we publish anonymized profiles — the kinds of people who run Nodetonet today, what they do with it, and how they set it up. If one of these sounds like you, you'll feel at home.
TL;DR: Nodetonet customers share three traits — they want to pay only for what they use, they need real carrier IPs or the option to add them, and they want one panel for proxies, VPN and tunnels rather than three separate vendor contracts.
How Nodetonet is actually used
Before the profiles, a quick map of the product so each story makes sense. Nodetonet is a self-hosted platform that turns Android phones into mobile proxies and Windows machines into HTTP tunnels, all managed from one panel. You pair a phone with a token via the Android agent app; the phone's 4G/5G IP immediately becomes a proxy endpoint. Billing is prepaid credit — no monthly subscription, idle proxies cost nothing. Protocols supported: HTTP/HTTPS and SOCKS5. Device pools, called token groups, do round-robin or least-connection selection with automatic failover. Per-client controls — auth, IP whitelist, domain allow/deny, quota, expiry, thread limits — live under the Proxy Clients section. Reseller accounts run on WISECP for white-label billing.
Now, the people who use it.
The ad-verification operator running hundreds of rotating tunnels
A small operator in Western Europe verifies advertising delivery for brand-safety clients. Their setup uses several hundred rotating proxy slots, each backed by a pool of paired Android phones spread across European mobile carriers. They hit publisher pages, capture the ads served, and feed results back to clients.
The carrier IPs are the whole point — datacenter or even residential proxy IPs get served different inventory or blocked outright, so they need real mobile addresses sitting behind carrier-grade NAT. The geo-targeting username modifiers let them steer by country and carrier from the same endpoint, without re-configuring their scraper. They also chain a residential upstream for the rare publisher that has carrier ranges on an allow-list rather than a block-list.
They chose Nodetonet over renting a residential pool because the math favored owning the devices: once the hardware and SIMs are paid for, traffic is essentially free, and the panel's token group logic handles failover automatically when a phone drops offline. Their operations team manages everything in English; their in-country staff uses the Turkish panel interface.
The fintech startup testing its own anti-fraud system
A Series-A fintech company uses Nodetonet to stress-test its own fraud-prevention logic. Their security team needs to simulate logins, signups and transactions from a spread of mobile carrier IPs — exactly the population a real fraudster would use, so that the rule engine is calibrated against realistic traffic rather than datacenter noise.
They run a small fleet of paired phones, swap the exit IP on each test run using sticky session suffixes when they need the same IP across a multi-step flow, or let the rotating pool pick fresh addresses for single-shot checks. They feed pass/fail metrics back into their rule engine and adjust thresholds accordingly. The SOCKS5 endpoint routes their custom test client directly; the HTTP endpoint feeds their Selenium suite.
Before Nodetonet they were buying residential proxies per gigabyte and paying for a separate testing tool. Consolidating into one prepaid-credit platform halved the tooling cost and removed the vendor-integration work. They read the per-client auth guide to isolate each test environment under its own credentials.
The indie developer with four side projects
A solo developer runs four personal projects simultaneously: a webhook receiver, a Telegram bot, a personal staging mirror, and a Discord automation. Each project has its own HTTP tunnel pointed at a different local port. Three of them get traffic maybe once a day.
He used to pay a flat monthly fee to a competing tunnel provider for four reserved subdomains. With Nodetonet's prepaid-credit model, tunnels he stops and doesn't run cost nothing — when a project sleeps for a week, the bill sleeps with it. The custom domain feature covers the one project that needs a stable public URL, with an automatically issued Let's Encrypt certificate. He discovered Nodetonet via the migration guide and set up in under an hour.
The QA team testing a mobile app on real carrier networks
A QA group at a mid-size e-commerce company tests their consumer app under realistic carrier conditions. They have paired phones on three different mobile networks across two countries. Their CI pipeline triggers a Nodetonet tunnel via the REST API, runs an Appium suite that routes traffic through the carrier IP, and tears the tunnel down at the end of each job.
The real-carrier IP matters because their app has a feature that behaves differently on cellular versus Wi-Fi — specifically, a video-quality adaptation that reads the connection type. They couldn't reproduce the bug with a datacenter proxy; they could reproduce it immediately through a paired phone on Turkcell. The device health dashboard shows which phones are online before each test run, so the pipeline can abort early rather than fail mid-suite.
They also use audit logs to trace which CI job used which tunnel, making it straightforward to match test failures to the exit IP that was active at the time.
The digital agency running web scraping for SEO clients
A digital marketing agency in Turkey runs concurrent proxy slots for SEO position tracking across regions and devices. They scrape search results, compare rankings against their clients' competitors, and deliver weekly reports.
They chose Nodetonet specifically because the panel is bilingual — the English and Turkish interfaces are equally complete, which matters when half the team reads Turkish and half reads English. They also lean on the upstream chaining feature: on targets where mobile IPs alone aren't enough, they chain a residential provider as an upstream, so the same Nodetonet panel covers both traffic types without a second vendor integration. The geo-targeting modifiers let them hit Istanbul SERP results from a local carrier IP, which is essential for accurate local-rank data.
They use reseller accounts to give each SEO client a separate credential set with its own quota and expiry, billed from a single prepaid balance.
The webhook developer who needed a stable, trusted URL
A freelance developer built a Stripe + Telegram notification bridge for a client. The Stripe webhook endpoint needed a permanent URL with a valid TLS certificate — Stripe validates the certificate on every event delivery. A free tunnel tool worked locally but reset the URL on every restart, breaking the Stripe configuration and requiring a manual fix each time.
They moved to Nodetonet for the custom domain with auto-issued Let's Encrypt cert, so the Stripe webhook URL is stable and trusted indefinitely. The prepaid model means they pay for the one always-on tunnel they actually use, nothing else. They set up tunnel health monitoring to get notified if the agent drops offline, so they can restart it before Stripe starts queuing events.
The reseller running a white-label proxy service
An entrepreneur runs a white-label proxy resale business using Nodetonet's WISECP integration. Their end customers never see the Nodetonet panel — they get their own branded login. The reseller manages all device pairing, token groups, and client quotas from the Nodetonet admin side; WISECP handles the customer-facing billing and plan management.
This setup lets a single operator serve many end customers from one shared device fleet, with per-client controls (quota, expiry, thread limits, IP allow/deny) keeping each customer's traffic isolated. The rotating proxy logic automatically balances load across online devices in the pool, so individual device outages don't affect customers. They read the token groups and automatic failover guides to tune the pool behaviour.
What all of them have in common
None of these customers are large enterprises with procurement departments. They're agencies, indie developers, QA teams, fintech engineers, freelancers. What ties them together:
- Prepaid, not subscription. They want to pay for what they use, not for what they might use. Idle proxies or tunnels should cost nothing.
- Real carrier IPs, or the option. Whether they run their own devices, chain an upstream provider, or both, they need to exit from IPs that a residential or datacenter pool can't convincingly fake.
- One panel, one bill. Separate contracts for tunnels, proxies and VPN add management overhead. They prefer a single platform that covers all three.
- Honest geo-targeting. They care which carrier and city the exit IP comes from — not just which country — because their targets care too.
If that describes your situation, the fastest way to check fit is to create a free account, add a small amount of prepaid credit, and run your first request through a test device. The panel speaks English and Turkish; support is on Discord and email. You can also explore what the platform covers on the features overview or read the getting-started guide before signing up.
How to get started
Onboarding is self-serve and takes under 30 minutes for most setups:
- Create your account and top up prepaid credit — no minimum beyond a test amount.
- Follow the Android agent install guide to pair your first phone, or the Windows PC agent guide to host an HTTP tunnel.
- Create a token, pair your device, and make your first proxy request. Check what exit IP the target site sees with our free What is my IP tool.
- When you're ready to serve multiple customers, read the per-client auth guide and the token groups guide.
Questions before you start? Reach us at support@nodetonet.com or on Discord.