> For the complete documentation index, see [llms.txt](https://docs.shieldproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shieldproxies.com/isp-proxy-guide/custom-quantity-vs-subnet.md). # Custom Quantity vs Subnet #### ISP Proxy Purchase Options: Custom Quantity vs Full Subnet Customers can purchase ISP proxies either as **individual IPs** or as a **full subnet** (up to 256 IPs). *** **Custom Quantity** Custom quantity orders allow customers to purchase any specific number of IPs (e.g., 10–200) from a subnet range. Each IP is fully private and dedicated to the buyer, though other users may own different IPs within the same range. **Benefits:** * Flexible and cost-efficient * Ideal for smaller or short-term projects * Lower commitment than purchasing a full subnet *** **Full Subnet** A full subnet provides ownership of all 256 IPs within the range. This option gives complete control and exclusivity over the entire block. **Benefits:** * Full control and consistency across all IPs * Clean reputation and improved stability * Best for enterprise-level or automated operations *** #### **Summary** Custom quantity is perfect for flexibility and lower cost, while full subnets deliver complete exclusivity and control. **All ISP proxies are private and dedicated to each user.** --- # 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://docs.shieldproxies.com/isp-proxy-guide/custom-quantity-vs-subnet.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.