Test from a connection you control.
Scripts, integration tests and CI/CD jobs often need a real network path—not a shared datacenter hop of unknown origin. Pair your own Android phones and give each pipeline its own proxy and exit IP.
- SOCKS5 and HTTP/S
- REST API + webhooks
- Rotate from dashboard or API
Built for developers
Sourcing you can see
The IP is your own phone’s connection. Nothing is pooled, rented or resold.
Fewer CAPTCHA challenges, typically
Real mobile and residential connections typically meet fewer CAPTCHA challenges than datacenter addresses. Results still depend on the site and how you use the connection.
A fleet for pipelines
Keep a small set of phones online—each with its own proxy—so staging, QA and CI jobs can target a stable mobile or home exit when you need one.
Wire your first pipeline in three steps.
- 01
Pair devices for each job
Install the app on one or more phones, pair with a PIN, and leave them powered and connected for the environments that need them.
- 02
Create proxies and credentials
Choose Cellular or WiFi Residential per proxy, then issue credentials, ports or IP allow-lists for your runners.
- 03
Point your code at the proxy
Use curl, your test harness or CI secrets to send traffic through SOCKS5 or HTTP/S and assert on the exit IP you expect.
Three steps on every device
Install the app, pair once, then use the credentials in any SOCKS5 or HTTP/S client.
- 01
Install the Android app
Download the app on a phone you own and sign in with your FalconProxy account.
- 02
Pair with a PIN
Register the device in your dashboard, then enter the 6-digit PIN in the app to link it.
- 03
Use the credentials
Create a proxy, copy the SOCKS5 or HTTP/S credentials, and point your tool or browser at them.
Exit modes
Choose Cellular to exit through your SIM’s mobile network, or WiFi Residential to exit through the home broadband your phone is on.
Protocols
Clients connect with SOCKS5 or HTTP/S using the host, port and credentials from your dashboard. Rotate the exit IP from the dashboard, API or signed URL when you need a fresh address.
Try it free, then pay per device
Try it free: 2 hours with 1 device and every feature, no card required. After that, $10 per device per month, with lower unit pricing as you add devices. See pricing or read the API docs.
Pay per device, and less as you grow.
One plan with everything included. Try it free: 2 hours with 1 device and every feature, no card required. After the trial, $10 per device per month with lower unit pricing as you add devices.
Automate from your own backend
Use Bearer keys against the REST API to create users, assign proxies, read usage and rotate IPs. Signed webhooks notify your systems when you change users or proxies through the API—for example when a user is created, suspended or a proxy is rotated.
Use it responsibly. Use your devices for lawful testing and development on your own services and permitted targets. See the Acceptable Use Policy. Read the Acceptable Use Policy.
Questions, answered.
No. FalconProxy turns a phone you already own into the proxy. You pay per device for the relay, dashboard and API; the IP is your own connection.
Yes. Many teams keep a dedicated phone per environment or job type so each pipeline gets a predictable exit. You manage every device from one organization in the dashboard.
The free trial gives you 2 hours with 1 device and every feature, no card required. After that it is $10 per device per month, and less at higher volumes.
Any client that supports SOCKS5 or HTTP/S proxies, such as curl, Python requests, Node, Go, browsers, Playwright and Puppeteer. Use the REST API to rotate IPs and toggle proxies from your own automation.
Signed webhooks fire for changes you make through the REST API—such as user lifecycle updates and proxy rotations—not for every background device event. Configure endpoints in the dashboard and verify signatures on your side.
Jobs that depend on that proxy fail to connect until the phone is back on the network with the tunnel running. Plan spare devices or retries for long-running pipelines.
There is no small-team cap: add devices as your plans require and pay per active device slot. Contact us for custom terms on very large fleets.
Yes, on systems you own or are permitted to test. Do not use the service to attack, scrape without permission or evade security controls—see the Acceptable Use Policy.
Ready to create your own proxies?
2-hour free trial, no card—pair your phone in minutes.
Already have an account? Log in