Nodetonet is a mobile proxy and tunneling platform that lets you route traffic through real Android phones on live carrier networks, expose local services to the internet, and run everything through one panel on prepaid credit — no subscription, no seat counts, no idle waste. This page is about the people who built it, why they built it, and the values the product is organized around.
TL;DR: prepaid credit, real mobile IPs, one panel for proxies + VPN + HTTP tunnels, bilingual English/Turkish support, small team that writes code and answers support tickets.
The problem we set out to solve
Every developer eventually needs to put a localhost service behind a public URL. The market for that was already crowded — ngrok-style tunnels had been a commodity for years. But the model had hidden costs: fixed monthly subscriptions, per-seat pricing, edge limits that capped how many tunnels you could open at once. Four side projects meant paying for four projects whether they were active or not. And if you also needed a residential or mobile proxy for scraping or ad verification, you went to a completely separate vendor and bolted it onto your stack.
We thought both problems had the same solution. A single service where you pay only for what is actually running, and where pairing a phone as a proxy exit is a checkbox rather than a separate procurement cycle. That meant combining three things most platforms keep apart:
- Mobile proxies — each paired Android phone becomes an exit node on its real carrier network, producing a genuine CGNAT-backed 4G/5G IP.
- HTTP tunnels — expose a local port over a secure HTTPS URL, with your own domain if you want one.
- VPN — route your own device's traffic through the same mobile carrier IPs without any proxy configuration.
How Nodetonet works
The architecture is simpler than it looks from the outside. Every mobile proxy starts with an Android phone running our agent app. You download the app, pair it to your account with a token, and the phone appears in your panel as a device. From that point:
- Your client (scraper, browser, automation tool) connects to a proxy endpoint — host, port, and username/password credentials your panel generates.
- Traffic flows through our edge servers, which forward it to the paired device over a persistent WebSocket connection.
- The device exits onto its carrier network, so the destination sees a real mobile carrier IP issued by CGNAT.
You can pool multiple phones into a token group for rotating proxy behaviour — new IP per request or on a timer. Or pin to one device for a sticky session by appending -session-XXXX to your username. Carrier and city targeting work through username modifiers on the same endpoint, so you never change connection strings to switch from a Turkcell IP to a Vodafone one. Both HTTP/HTTPS and SOCKS5 are supported from every device.
What makes us different
| Dimension | Most platforms | Nodetonet |
|---|---|---|
| Pricing model | Monthly subscription, per-seat or per-GB metered | Prepaid credit; idle proxies cost nothing |
| Proxy + tunnel combo | Separate products, separate bills | One panel: mobile proxy + VPN + HTTP tunnel |
| Mobile IP source | Third-party residential pool | Your own paired Android devices, real carrier IPs |
| Reseller support | Often enterprise-only | WISECP white-label built in; per-client controls |
| Language | English only | Full English + Turkish UI and support |
Per-client controls go deep: each customer you create gets their own username/password credentials, an optional IP allowlist, domain allow/deny rules, a data quota, an expiry date, and a thread-concurrency cap. You can run a reseller operation from day one without touching our API — everything is in the panel.
Team
We are a small distributed team split between Turkey and Europe. The panel and control plane run on Node.js, the proxy data plane on a compiled backend, and the Android agent is written in Kotlin. EU data centers host the infrastructure; backups run daily off-region. Everyone on the team writes code, and everyone takes a turn on the support inbox — there is no separate "tier 1" that only reads scripts.
We keep the team deliberately small. The decisions that matter most for a developer-tool product — pricing granularity, billing transparency, sensible defaults — are faster and cleaner when the people deciding them also ship the code.
Values we try to hold to
- Prepaid over subscription. Subscription billing is great for the vendor and bad for the customer who forgot to cancel a plan they stopped using. Prepaid means we earn each top-up. That is a healthier alignment.
- Transparency about limitations. Our comparison pages list our genuine limitations alongside competitor differences. When we do not have a feature, we say so rather than writing around it.
- Local plus global. Full English and Turkish UI, with pricing in USD, Stripe integration, and local payment options for Turkish customers. Bilingual support that we wished had existed when we started.
- Honesty about scale. We are not a 10-year-old company with SOC2 certifications and a 500-person sales team. We are a focused product on its way up, and we try to communicate with customers accordingly.
Security and compliance baseline
All panel traffic runs over TLS. Session tokens and API keys are hashed at rest. Per-client SOCKS5 and HTTP credentials are isolated — one client's key cannot reach another client's proxy. Audit logs track every credential use. For the full breakdown, see the security page. If you find a vulnerability, email security@nodetonet.com — it goes directly to the engineering team, not a ticket queue.
Get in touch
The fastest path to a human: email support@nodetonet.com for account or technical questions, or join the Discord community where the team is active daily. We also post updates and tips on X / nodetonet. We answer in both English and Turkish — no chatbot, no canned first response.
If you want to see the product before talking to anyone, create a free account — no card required. Explore the panel, pair a device, and browse the API. You only need a $1 credit top-up to actually run a tunnel or proxy. For a self-guided tour, our getting-started guide walks every step, and the first token and Android pairing post covers the phone setup in detail.