u/No_Storm2316

Mobile SOCKS5 from India 6 phones, unlimited bandwidth, working well for me

Hi there I set up some mobile proxies for my own scraping using 6 Android phones on Jio/Airtel.

They’ve been working surprisingly well, so I thought maybe others here could use them too. I’ve been testing everything myself and now trying to see if this can become a small business.

What it is:

  • 6 real 5G Android phones on Indian carriers
  • SOCKS5 rotating proxies
  • Sticky sessions available
  • Unlimited bandwidth (with some fair-use nuances)

Format:
socks5://API_KEY:x@DOMAIN/IP_ADDRESS:PORT

What works well:

  • Anti-bot systems like Cloudflare/Akamai trust real mobile ASN more than datacenter IPs
  • For sites where residential proxies get flagged fast, mobile IPs usually last longer
  • Real Indian mobile IPs, not resi resellers

What’s lacking right now:

  • Only 6 phones currently, so the pool is still small
  • India-only for now (US latency around 80–150ms can be hire as well)
  • Not magic, not the fastest just real mobile IPs from actual devices

If people actually want this, I can scale it pretty fast:

  • 10 more proxies in 1 day
  • Around 50 proxies in 5–7 business days

Pricing:
Still figuring this out honestly.
Right now I’m just doing $20/month flat while testing.

If anyone wants to try it, DM me and I’ll send a trial key.
No card needed.

Works with:
Python requests, Scrapy, Playwright, curl, etc.

I’m the one running everything myself, so support is direct too.

reddit.com
u/No_Storm2316 — 9 days ago

First client, HTTPS support, and finally making Snowpad testable

7 days ago I posted Day 11 about building Snowpad — a mobile proxy network powered by real phones in India.

This week was less “cool architecture screenshots” and more “okay now make this thing usable.”

What happened between Day 12 → Day 18:

  • Got my first initial client call/discussion
  • Realized I need to move way faster on reliability + onboarding
  • Went to college/admin side to ask for pending funding/payment (still learning how awkward business gets 😅)
  • Opened proxy server testing access instead of keeping everything local
  • Added HTTPS support to the proxy gateway
  • Focused heavily on logs + proxy stability instead of frontend polish

Big lesson this week:
Nobody cares how clever the infra is if testing the product feels painful.

Last post, people from r/proxies told me they wanted:

  • Free trial traffic
  • Transparent logs
  • Real carrier verification
  • Actual success-rate stats

So I stopped over-engineering dashboards and started fixing the operational side first.

Current setup:
Phone → FRP tunnel → Gateway → Single rotating SOCKS5 endpoint

Still rough:

  • Frontend is unfinished
  • Payment gateway flow still messy
  • Logs need better filtering/search
  • Reliability under load still being tested

But now:

  • HTTPS works
  • External testing works
  • Real users are trying it
  • And I finally have someone willing to pay if I make it stable enough

This week’s focus:

  • Make logs genuinely useful
  • Improve proxy rotation reliability
  • Clean up onboarding
  • Turn “interesting prototype” into “usable product”

Stack:
Go, Flutter, Next.js, Postgres, FRP tunnels

One SOCKS5 URL. Real mobile IPs. Phones rotate automatically.

Roast me publicly:
What’s the biggest red flag you see in this idea/product right no

reddit.com
u/No_Storm2316 — 12 days ago

Day 11 of building Snowpad a platform where real phones share their mobile data as SOCKS5 proxies. Not datacenter IPs pretending to be mobile. Actual 4G/5G connections from Jio and Airtel devices in India.

What shipped this week:

  1. The core loop works end-to-end: Phone runs frpc → FRPS on VPS → Gateway exposes single SOCKS5 endpoint → Client curls through it and gets a real Indian mobile IP
  2. Web dashboard with OTP email verification (Brevo), Google OAuth, forgot/reset password — full auth flow, no Clerk dependency
  3. Gateway cross-checks FRPS API for real-time port state instead of stale heartbeat data. Phones get new ports on every reconnect, pool updates within 30s
  4. frpc stability: added tcp_mux, 15s heartbeat, 60s keepalive, and auto-restart (up to 3x) when the process crashes. Android foreground service no longer silently dies
  5. Separate key systems: 32-char hex Snowpad keys for gateway auth, sp_xxx web keys for dashboard API. Proxy endpoints resolve the real key server-side

What I learnt from r/proxies feedback:

My earlier post asked what proxy buyers trust. The top answers were:

  1. Trial traffic without commitment not "sign up for $50 min"
  2. Verifiable carrier/ASN data prove it's actually Jio/Airtel, not a datacenter pretending
  3. Success-rate benchmarks not just "it works" but how well on specific targets
  4. Transparent usage logs per-request, not "you used 4.7GB trust me"
  5. So that's exactly what I'm building next week.

This week's goal (Day 12-18):

Free trial: 100MB no-credit-card, instant via dashboard

Per-request usage logs with ASN, carrier, city, response time

Success-rate dashboard showing real stats on common targets

Pitch to 5 proxy buyers from r/proxies thread

Stack: Go (gateway + API), Flutter (Android operator app), Next.js 16 (dashboard), Neon Postgres, FRP tunnels, Brevo email

One SOCKS5 URL, all phones rotate automatically. That's the whole pitch.

Roast welcome. What's the one feature that would make you try it?

#buildinpublic #indiehackers #proxy

u/No_Storm2316 — 20 days ago

I’m building a mobile proxy network starting with India and I’m trying to understand what serious proxy buyers actually care about.

Not launching or selling yet. Just doing customer discovery.

From reading this sub, the biggest concerns seem to be:

  1. providers reselling unknown IP pools
  2. quality dropping after the first few GB
  3. unclear bandwidth usage/billing
  4. no proof of IP source
  5. unreliable success rates
  6. expensive minimum top-ups
  7. weak dashboard/API

If you were evaluating an India mobile/residential proxy provider, what would you need to see before trusting it?

Would it be:

  1. trial traffic?
  2. source/provenance docs?
  3. carrier-level targeting?
  4. success-rate benchmarks?
  5. transparent usage logs?
  6. lower minimum top-up?
  7. API examples?
  8. something else?

I’m especially interested in people doing scraping,
SEO/SERP checks, ad verification, or QA/localization.

reddit.com
u/No_Storm2316 — 26 days ago