Solutions
Enterprise proxy solutions
For teams that need scale and a clear commercial conversation. Tell us what you need to do, and we will say what we can supply.
Capabilities
What enterprise customers can ask for
Large static pools
ISP and datacenter plans up to 1,000 IPs, and IPv6 packs up to 15,000 addresses.
Residential volume
GB plans up to 300 GB and unlimited-traffic residential plans by day, week or month.
Mobile capacity
Dedicated mobile proxies on Turkish carriers, quota and unlimited.
Custom location requests
Ask for countries, cities or carriers beyond the catalog; we confirm what is possible before you commit.
Protocol flexibility
HTTP and SOCKS5 across the products where they are confirmed.
- Contact sales
Direct sales channel
A WhatsApp line for quotes, availability and onboarding questions.
Process
How an enterprise engagement works
Describe the workload
Targets, countries, expected traffic, protocols and duration.
Receive a recommendation
We suggest products, pack sizes and billing periods — and tell you if another approach fits better.
Pilot, then scale
Start with a small order to validate success rates before committing to volume.
In depth
The details that decide the outcome
Capacity planning against the real pack limits
Start from the largest single plan available per family, because that is the ceiling you can order without a custom conversation: static ISP and datacenter plans reach 1,000 IPs, gaming plans 250, IPv6 plans 15,000 addresses from a /64, and residential rotating plans 300 GB per plan. Unlimited-traffic residential plans are sold by the day, week or month instead. Anything above those ceilings is a question for sales; do not assume that several plans combine into one pool or that a volume discount exists beyond the lower unit prices already shown on the larger packs.
Size static pools from concurrency and per-IP pace. As an illustration, suppose a target tolerates about one request every two seconds per IP and you need 20 requests per second overall. That requires 40 IPs, and a 25 percent margin for IPs that are blocked or being rested raises it to 50, which maps to the 50-IP ISP plan. These numbers are examples only; measure the real tolerance of your target in a pilot before you buy for production.
For metered residential traffic, estimate bytes per successful request multiplied by volume. If an average page transfers 0.5 MB (example) and you need 200,000 pages a day, that is roughly 100 GB a day, or about 3,000 GB over 30 days, ten times the largest 300 GB plan. At the 300 GB plan’s rate of 30 TRY per GB, the daily unlimited plan at 5,000 TRY breaks even at about 167 GB per day, and the monthly unlimited plan at 75,000 TRY at about 2,500 GB per month. Above those volumes the unlimited plans cost less per byte, if their terms suit your use.
| Family | Largest single plan | Planning note |
|---|---|---|
| ISP Proxy | 1,000 IPs | Static and Turkey-based; HTTP or SOCKS5 chosen at checkout; 1, 3, 6 or 12 months. |
| IPv4 Datacenter Proxy | 1,000 IPs | Unlimited traffic as listed; monthly only; confirm location with sales. |
| IPv6 Proxy | 15,000 IPs | From a /64 subnet; HTTP/HTTPS listed, SOCKS5 and location not confirmed. |
| Residential rotating | 300 GB per plan | 30-day usage period; country targeting as stated by the provider. |
| Unlimited residential | Day, week or month | Protocol details not published; ask sales about any fair-use terms. |
| Gaming (Knight Online, Metin2, Silkroad) | 250 IPs | Static Turkish IPs; HTTP or SOCKS5 at checkout; no ping guarantee. |
Designing a pilot with measurable success criteria
A pilot turns a vendor claim into a number you own. Define the workload first: the target sites, the request mix, the countries, the protocol and the daily volume. Choose one or two candidate products, order the smallest plan of each that can carry a realistic test, and run the same client code against every candidate for a fixed period, such as seven days (an example). Keep a control, for instance the same job from your own network or from a second product, so that a bad result can be attributed to the proxy rather than to your code.
Write the pass criteria before you start, or the results will be argued afterward. Measure useful responses, not HTTP 200: a block page or a CAPTCHA can return 200. Track block signals separately (403, 429, challenge pages), latency at the median and the 95th percentile, bytes per successful request, and cost per 1,000 successful requests. As an example threshold, you might require at least 90 percent useful responses, a 95th-percentile latency under 3 seconds and a cost per 1,000 below your budget; your own numbers will differ.
- Before ordering: get anything the order page does not state, such as datacenter location, protocol where checkout has no selector, or rotation timing, confirmed in writing.
- Day 1: verify every proxy with the Proxy Checker and record exit IPs and latencies as your baseline.
- Days 1 to 7: run the real workload at a low rate, raise it in steps, and log every failure with its reason code.
- End of pilot: score each candidate and the control against the written criteria, not against impressions.
- Decision: scale the winner, change the product mix, or stop; a pilot that ends a bad fit cheaply has done its job.
Security and compliance questions to ask any proxy provider
A proxy provider sits on the path of your traffic, so due diligence is worth more here than in most purchases. Ask where the IPs come from and, for residential and mobile pools, how the owners of those connections consented to the arrangement. Ask whether connection or request logs are kept, what they contain and for how long. Ask who the contracting entity is, which law governs the contract, how abuse reports are handled and what happens to your account when one arrives. Ask for answers in writing rather than accepting a marketing page.
Your own side matters just as much. Store proxy credentials in a secrets manager or environment variables, never in source control, and give each team or environment its own order so you can retire one without touching the others. Remember that the leg between your client and an ordinary HTTP proxy is not encrypted: plain-HTTP traffic and the proxy login travel in the clear, while HTTPS traffic stays encrypted end to end through the tunnel, so keep sensitive data on HTTPS. If personal data is involved in your collection, consult your own legal counsel about the privacy laws that apply to you.
| Question | Why it matters | Status on this site |
|---|---|---|
| How is the residential and mobile IP supply sourced? | Consent and legality of the underlying connections. | Not documented here; coverage claims are the provider’s statements. Ask sales. |
| Are traffic or connection logs kept, and for how long? | Your targets and volumes may be sensitive. | Not published on this site. Ask in writing. |
| What are the refund, replacement and service-level terms? | They define your remedy if a plan underperforms. | Not published on this site. Check the order terms on the panel and ask sales. |
| Which authentication options exist? | Credentials and IP whitelisting limit who can use your IPs. | Username and password; whitelisting on some products in the panel. |
| Which certifications or audits apply? | Some buyers need them for vendor approval. | None are claimed on this site. Ask sales what can be provided. |
| What are the acceptable-use rules? | They decide what traffic can get an account suspended. | Lawful use is required; see the terms of service and the panel’s terms. |
A procurement checklist for larger purchases
Buying through a storefront and an order panel is simple, but a procurement review still needs answers. Confirm the commercial basics first: prices are in Turkish lira, excluding taxes, with no currency conversion, so your finance team needs to budget the exchange rate and any tax itself. Billing periods differ by family (monthly for datacenter, IPv6 and residential GB; 1, 3, 6 or 12 months for ISP and most gaming plans; 1, 3 or 6 months for static mobile), and the 5, 10 and 100 GB rotating mobile packs are one-time packs rather than monthly plans.
Finally, decide how you will manage the relationship. There is no public API documented on this site, so ordering and credential retrieval go through the customer panel; if automation is a requirement, say so at the start and ask sales what can be arranged. For custom locations, cities or carriers beyond the catalog, sales confirms what is possible before you commit. Start with a pilot-sized order, keep the order page and any written confirmations in your vendor file, and review usage and cost at every renewal rather than only at signing.
- Legal entity and invoicing: ask who issues the invoice and which details it carries; none are published on this site.
- Payment methods and renewal behavior: read them on the order page and confirm anything you rely on with sales.
- Written confirmations: location of datacenter IPs, protocol where checkout has no selector, exclusivity of IPs, rotation timing on rotating mobile.
- Remedies: refund and replacement terms, and any service-level commitment, in writing.
- Technical acceptance: the pilot criteria and a named person who signs them off.
- Exit plan: the shortest commitment that still serves the project, and who removes the credentials from your systems at the end.
FAQ
Enterprise questions
Is there a minimum contract?
Standard plans are ordered individually. Terms for large or long engagements are discussed with sales.
Can you guarantee a success rate?
No provider can; success depends on the target, your tooling and request patterns. We recommend a pilot.
Do you provide an API?
No public API is documented on this site. Ask sales if you need automation.
Can we get a written quote or custom terms for a large order?
Quotes, longer engagements and custom locations are handled through sales on WhatsApp or phone at +90 850 550 34 60. Standard plans are priced on the order pages in Turkish lira, excluding taxes. Terms beyond what the order pages show are not published on this site, so ask for them in writing.
Should production and testing use the same order?
We suggest separate orders. Each order has its own credentials and billing period, so an expiry, a leaked login or a block affecting one environment does not take down the other. It also makes cost reporting by team straightforward.
What if our volume is larger than the biggest plan?
Tell sales your target countries, expected traffic and protocol. Do not assume that several plans merge into one pool or that extra discounts apply; ask what can be arranged and confirm it in writing. For metered residential traffic, compare the unlimited day, week and month plans against several GB plans, as in the capacity section above.
Enterprise
Need volume, custom locations or a procurement-friendly setup?
Talk to sales about large IP counts, long contracts and dedicated onboarding. Tell us the target countries and traffic profile and we will propose a fit.