Changing or Upgrading Your Plan
How to move to a different plan, what happens to unused paid time, and what changes (and what does not) when you switch product.
How to change your plan
Open a support ticket from the dashboard naming the plan you want to move to. Support moves the subscription across, and the unused time on your old plan is credited toward the new one. Billing requests are handled Monday to Friday during business hours, so allow for that if you need the capacity on a particular day.
If what you need is more data on the plan you already have, a bandwidth top-up is self-serve and applies at once. For a one-off shortfall it is usually the better tool anyway.
Unused time on the old plan
Moving mid-cycle does not forfeit what you have paid. The remaining value of the old plan is applied as credit against the new one and appears on the invoice for the change as a proration or credit line; understanding your invoice shows how those lines read. The amount depends on how far through the cycle you are. If a figure looks wrong, reply on the ticket before paying.
What changes, and what stays
| Same product, different size | Different product | |
|---|---|---|
| Endpoints | Unchanged | New: static products list a host and port per proxy, gateway products use a fixed hostname |
| Proxy credential | Unchanged | Unchanged. You have one credential per account, and it works on every product you hold an active plan for |
| Allowance or proxy count | Grows or shrinks to the new plan | Set by the new plan |
| Rotation, sessions, targeting | Unchanged | Differ by product |
| IP whitelist, API keys, webhooks | Unchanged | Unchanged; they belong to the account, not the plan |
After a same-product change, check that the Proxies page shows the new count or the Dashboard shows the new allowance, and that any IPs you rely on are still listed. If something is missing, say so on the same ticket.
After a change of product, every script, browser profile and scheduler pointing at the old endpoints needs the new host and port. Your existing credential keeps working; only the address changes. Rotation and session behavior differ between products, so read choosing the right proxy type before you commit rather than after.
Buying a second plan of the same type
Another plan of a proxy type you already own adds to what you have: same-type subscriptions stack, and the enforced allowance is the sum across every active subscription of that type. Two Rotating Datacenter plans give you both allowances, and the dashboard reports the combined figure. Quantity-based products provision per subscription, so a second plan delivers its own proxies on top of the ones you hold.
A second subscription is also a second renewal date and a second invoice line. If the goal is simply more of the same, changing the existing plan keeps the account tidier.
Before you open the ticket
- Check the Dashboard meter, and Analytics for history. Running out of data points at a top-up or a larger allowance; being blocked by targets points at a different proxy type, not a bigger plan.
- Note your renewal date on the Plans page; it decides what the proration looks like.
- List where your endpoints are configured if you are changing product, so nothing is still pointing at the old host a week later.
- Name the exact plan from /pricing in the ticket.
Renewal, cancellation and reactivation are covered in subscription management.