> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/legacy-products/proxy-builder/getting-started/proxidize-proxy-builder-legacy-overview-and-how-it-works.md). # Proxidize Proxy Builder (Legacy) Overview & How It Works Proxy Builder is legacy documentation for existing users only. Proxy Builder is no longer offered to new customers. If you are new to Proxidize, use the managed cloud products instead. A complete guide to how the Proxidize Proxy Builder works, what it's made up of, and how to get started building and managing your own mobile proxy network. ### **What is Proxidize Proxy Builder?** Proxidize Proxy Builder is a complete, end-to-end solution for building and managing your own 3G, 4G/LTE, and 5G mobile proxies, without relying on a third-party proxy provider. Most proxy users rent access from providers, meaning they share infrastructure, have no control over uptime or quality, and are subject to someone else's pricing. Proxy Builder flips that model entirely. Rather than buying proxies from someone else, you build and own your proxy infrastructure using your own hardware. Your proxies, your network, your control, with full visibility into performance, costs, and scale. Using your own hardware *(whether that's Android phones or a Linux-based server with USB modems)* you can have mobile proxies up and running in minutes, managed entirely from a cloud dashboard accessible from anywhere in the world.\ The platform is built to scale with you, so whether you're starting with a single phone or deploying hundreds of modems, the infrastructure grows with your needs. **See it in action:** *** ### **What Can You Build With It?** Proxy Builder currently supports two types of setups: * **Android Agent:** Use Android smartphones as mobile proxy sources. Simple to set up, no additional hardware required beyond the phone and a SIM card. * **Linux Agent:** Use a Linux-based server paired with USB LTE modems to create a scalable, high-capacity proxy network. Both are managed through the same cloud dashboard, giving you a single place to monitor and control your entire proxy fleet. *** ### **How It Works** #### Proxy Builder is made up of two core components: **hardware** and **software**. **Hardware** Depending on your setup, your hardware will be either: * **Android phones** with active SIM cards, or * **A Linux server** connected to a USB hub with multiple LTE modems Each device or modem acts as an individual mobile proxy endpoint, using real cellular connections that are indistinguishable from regular mobile network traffic. **Software** **Cloud Router** The Cloud Router handles communication between your hardware and the Proxidize platform, no manual router configuration, no port forwarding, no ISP restrictions to work around. Your proxies connect through one of many globally distributed cloud routers, making them accessible from anywhere in the world. ![](/files/0d6b141d53f753d502a1d896fff4a554f0c2dbf6) **Cloud Dashboard** The Cloud Dashboard is your central control panel for everything. From here you can: * Monitor all connected devices and proxies in real time * View detailed analytics and usage reports * Configure and manage individual proxies or entire fleets * Set up customizable alerts for device and connection events * Rotate IPs, manage endpoints, and control proxy settings remotely ![](/files/c23960842a60a1b4ca42fbcbe7520806d86d4af8) *** ### **Plans & Pricing** Proxy Builder plan details are kept for existing users who still need them. See the archived breakdown on the [Proxidize Proxy Builder (Legacy) Platform Plans](/legacy-products/proxy-builder/getting-started/proxidize-proxy-builder-legacy-platform-plans.md) page. *** ### **Getting Started** The fastest way to get started depends on your hardware: * **Using an Android phone?** Start with the [Android Agent: Device Compatibility & Requirements](/legacy-products/proxy-builder/hardware/android-agent-device-compatibility-and-requirements.md) article, then follow [Onboard an Android Device to Proxy Builder (Legacy)](/legacy-products/proxy-builder/setup-and-onboarding/onboard-an-android-device-to-proxy-builder-legacy.md). * **Using a Linux server and modems?** Check [Linux Agent: System Requirements & Supported Modems](/legacy-products/proxy-builder/hardware/linux-agent-system-requirements-and-supported-modems.md) before getting started. If you need more legacy setup help, continue with [How-to Guides](broken://spaces/iAQa47xivOtQQ7mQZOnQ/pages/83f1b8942301c82f0ce6ac2b7ccbd4fca614ee08) or review the [Proxy Builder Platform Deprecation Notice](/legacy-products/proxy-builder-platform-deprecation-notice.md). *** ### Need Help? If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at ****. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.proxidize.com/legacy-products/proxy-builder/getting-started/proxidize-proxy-builder-legacy-overview-and-how-it-works.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.