Proxy App - suggestions

kasan · Jun 19, 2026

Hi guys im developing a proxy panel for vps/mobile, for mobile its routed to "panel" cause mobile have problem with out to the world... even with public ip. VPS can work in dual as routed or direct connection. For now i have working panel, with vps agent and android app. Can you give me any advice, what you think it should have to actually be useful for you. It will be free / open source.
For now my main problem is focused on "rotating" ip on mobile - its cased because on older android you need to use adb on app... for doing that reconnect / network reset.
Initially i thought there will be no users system, but in the end i made it so each device can have separate credentials, so you can basically treat it like "users per device" and track them separately.
transport layer: ws/wss and routing tcp packets
stack: python/ android kotlin and blablalb
any suggestions and criticism are welcome
edit: of course you can use api insted of panel....

proxygo · Jun 19, 2026

hard to answer as the country im in is trying to ban them

wolfofdevstreet · Jun 19, 2026

why open source it?

iproxyonline · Jun 20, 2026

From my own experience: build it so YOU actually want to use it daily yourself. Run your own real proxies through your own panel for whatever you actually do (scraping, social accounts, whatever). When the platform genuinely solves YOUR own problem, you’ll already know what’s missing and what’s bloat without having to ask. Then you can offer it to people with the same problem as you, they almost certainly need same thing.

On features selection: easiest way is just to look at pricing of existing commercial mobile proxy products. Commercial products only keep features that have real demand. If a feature shows up prominently in 3-4 different products plans, the overlap is your actual must-have list.

turelink · Jul 1, 2026

If I was going to use it daily, I would want 4 things first: last rotation time, current carrier or ASN, device health, and a dead simple API for reconnect. After that, logs matter a lot. If a user cannot tell why one device stopped rotating, the panel becomes support work fast.

faster · Thursday at 6:40 PM

kasan said:
Hi guys im developing a proxy panel for vps/mobile, for mobile its routed to "panel" cause mobile have problem with out to the world... even with public ip. VPS can work in dual as routed or direct connection. For now i have working panel, with vps agent and android app. Can you give me any advice, what you think it should have to actually be useful for you. It will be free / open source.
For now my main problem is focused on "rotating" ip on mobile - its cased because on older android you need to use adb on app... for doing that reconnect / network reset.
Initially i thought there will be no users system, but in the end i made it so each device can have separate credentials, so you can basically treat it like "users per device" and track them separately.
transport layer: ws/wss and routing tcp packets
stack: python/ android kotlin and blablalb
any suggestions and criticism are welcome
edit: of course you can use api insted of panel....

View attachment 529957

I'd probably add a few things that would save me time when managing multiple devices. An automatic health check with auto-reconnect if a device goes offline, scheduled or API-triggered IP rotation, and a one-click "Test Proxy" button that verifies the exit IP and connectivity would be really useful. I'd also expose more details in the dashboard, like uptime, last successful rotation, current ASN/carrier, and proxy latency. Finally, a simple webhook or notification when a device disconnects or fails to rotate would make it much easier to monitor without constantly checking the panel.

Proxy App - suggestions

kasan

Newbie

Attachments

proxygo

Elite Member

wolfofdevstreet

Junior Member

iproxyonline

Regular Member

turelink

Elite Member

faster

Elite Member

Main Menu

Marketplace

Making Money

BlackHat World