DEV Community

Cover image for ISP proxy pricing: the per-IP unit and how to size it
proxymint
proxymint

Posted on Originally published at proxymint.com

ISP proxy pricing: the per-IP unit and how to size it

Originally published on proxymint.

ISP proxy pricing explained: why static ISP IPs bill per IP per month, what moves the bill, terms and refunds, a sizing method, and the jobs ISP fits best.

TL;DR

  • ISP proxies are billed per IP per month, not per GB. The bill tracks how many static addresses are held; traffic through them does not change the price.
  • The per-IP rate falls as the order grows. proxymint prices the whole order at the rate for its size, and every volume band is on the pricing page.
  • The count of identities sets the bill. One address per account or login location that has to hold, plus one or two for testing.
  • Terms bill the same monthly rate. A 3 or 12 month term is billed up front at the monthly rate and suits addresses the team will keep.

Key takeaways

  • Price the job, not the IP. Count the identities that must hold a fixed address; that count is the order.
  • Order the exact quantity. The per-IP rate falls across volume bands, and the pricing page lists the rate for each quantity.
  • Size by identities, not throughput. A static IP is an identity, not a throughput pipe; size the order by identities and keep each address at a steady, modest request rate.
  • Test inside the 7-day window. Per-IP products refund in full inside 7 days on a first purchase, so start with a small set and scale once the target accepts it.
  • Match the tier to the requirement. ISP fits addresses that must hold; broad scraping fits rotating residential, and lenient bulk work fits datacenter.

Read the full guide on proxymint, with the commands, tables and sources.

Top comments (0)