Shared vs dedicated static residential IPs: choose by isolation and store count

Confirm first: you need static, not rotating

If you already want a fixed exit, this page only helps you choose shared static vs dedicated static. If rotating vs static is still unclear, read Rotating vs static residential first: same exit for the term + authorized store long login → static; public sampling / multi-region checks → rotating.

A sticky session is only a short option on rotating—not a monthly fixed static IP. Below assumes you lean static and only compares Shared vs Dedicated. After you pick by isolation strength, store count, and budget, confirm plans on Static residential or Pricing. Lawful, authorized commercial and technical use only. Not supported for use in mainland China.

What shared static is

Shared static gives a fixed exit for the subscription term; resources are managed on a shared-pool side; billed mainly per IP / month. On-site published about $1.50/IP/month—console wins.

Fit: authorized single-store or fixed-identity scenes where isolation need is not extreme; also a starter to verify “is a fixed exit enough.” Term, renewals, and region live in the console—before bulk orders, browse Locations (stock changes).

What dedicated static is

Dedicated static is also a fixed exit for the term, oriented to a dedicated fixed IP: managed by region and term; billed mainly per IP / month. On-site published about $5/IP/month—console wins.

Fit: higher isolation, long core business, clearer per-store or per-environment exclusive exits. Region selection, bulk manage, and renewals follow on-site pricing cards (no availability % or SLA promises). Isolation language only means “higher isolation orientation / dedicated fixed exit”—not a platform-risk-control guarantee.

Shared vs dedicated side-by-side

Prices and stock follow site + console; this table is not a success-rate or isolation guarantee.

How cross-border stores choose

Common scenes

Authorized single store long backend. Lawful store that must stay logged in: start with shared static to verify a fixed exit is enough—confirm region/term in console, smoke one real flow, then decide whether to upgrade dedicated.

Multi-store, one exit per store. Parallel authorized stores lean dedicated static; plan exits per store so unrelated businesses do not crowd one exit. Do not “hope” unrelated accounts share one IP.

Same brand, multi-region stores. US/JP/SG/UK targets usually need matching exit regions: pick on Locations, then assign IPs per store; city-level stock changes—confirm in console before bulk.

Core dedicated + test shared. Long core business on dedicated; trial or short test stores on shared—tier by risk instead of lifting every store to dedicated monthly cost.

Assorting / competitor page checks only. Independent public page checks do not need long same-login identity—do not force static; return to Rotating vs static or Rotating.

Large public sampling traffic. Large rotate requests belong on rotating GB bills—not something static monthly rent replaces. Cost deep-dive: Billing GB vs IP. Store map: Ecommerce.

Multi-store fixed-connection planning

Simple rule: one store (or one stable business environment) maps to a clear exit plan; do not crowd unrelated accounts onto one exit and hope.

Start small: smoke one real store flow on shared or dedicated, then expand IPs per store. Static watches resource term and renewals—not “remaining GB.” Regions/stock: Locations; order/renew via Static console. Sticky is not a substitute: Sticky vs static.

How to read price

• Shared static about $1.50/IP/month; dedicated static about $5/IP/month (USD, console wins).
• Math is “how many fixed exits × months,” not “who is cheaper than rotating”—different rhythms: long fixed identity → static; public sampling / multi-region → rotating (~$0.40/GB boundary only, console wins).
• Huge sampling bills: Billing GB vs IP—do not force static monthly rent to carry large rotate sampling.

Rough-estimate “IP count × months” on Pricing, confirm in console, then scale. Payment context: USDT/USDC available; Visa/Mastercard applying / pending.

Pre-order checklist

1. Target region: confirm selectable scope in Locations + console (stock changes; ask sales/support if unsure).
2. Shared or dedicated: from the tables—shared, dedicated, or mix (core dedicated + test shared).
3. IP count: plan per store / environment; smoke first, do not buy full capacity at once.
4. Protocol: HTTP or SOCKS5 per product—copy host/port/auth the console returns (HTTP / SOCKS5).
5. Client: browser, script, or automation with console credentials.
6. Smoke: one real store flow before raising IP count.
7. Docs: Docs EN quickstart.

FAQ

Shared vs dedicated static—when must you go dedicated?

Both are fixed exits for the term, both bill per IP / month. Shared about $1.50/IP/month, shared-pool managed—milder isolation start/routine authorized scenes. Dedicated about $5/IP/month—dedicated fixed-exit orientation for higher isolation, long core business, per-store exclusive. When you need clearer separation so stores influence each other less, lean dedicated or split per store. Price/stock: console. Product: Static.

For cross-border store / long backend login, is shared enough?

For a lawfully operated single store that must stay logged in, shared static can verify whether a fixed exit is enough. Multi-store parallel or clearly higher isolation → upgrade dedicated or split per store. Do not use proxies for unauthorized account ops. Region/term: console.

How to plan multi-store fixed connections? How many IPs per store?

One store (or one stable environment) → clear exit plan; do not crowd unrelated accounts on one exit. Exact counts vary—no universal “industry standard count.” Smoke one real store flow, then expand per store. Regions: Locations.

When static monthly traffic is huge, is it cheaper than rotating?

Watch task rhythm, not unit price alone. Long fixed identity → static (IP × month); large public sampling / multi-region independent requests → rotating (per GB). Forcing static for sampling, or rotating for whole-month fixed login, wastes budget. Deep math: Billing GB vs IP; class: Rotating vs static.

Is shared “many people fighting one IP”—unstable?

Shared static is managed on a shared-pool side; the exit is fixed for the term, but isolation orientation is weaker than dedicated. No availability % promise and no “never influence each other” claim—console + your real flow smoke-test win. Need stronger isolation → dedicated.

How is it billed?

Static residential mainly per IP / month: shared ~$1.50, dedicated ~$5; rotating mainly per GB (~$0.40/GB as boundary). USD; console wins. See Pricing and Billing GB vs IP.

Can sticky replace shared or dedicated static?

No. Sticky is a short same-exit option on rotating; static is monthly fixed identity. Sticky vs static.

Mainland China? Who wins on price?

All proxy services on this site are not supported for use in mainland China. Published prices are USD; orders and bills follow console + Pricing. USDT/USDC available; Visa/Mastercard applying / pending.

Next steps

1. Tick the decision table: shared, dedicated, or “core dedicated + test shared.”
2. Open Pricing; estimate IP count × months; confirm plan and region in console.
3. Order Static; class still unclear → Rotating vs static.
4. Connect via Docs EN quickstart; smoke one real store flow, then expand per store.

Pick shared or dedicated → estimate IP count on Pricing →

Unsure? On-site support or [email protected]. Choose by isolation and store count first, then smoke one real connection.