One of the most overlooked specs in multi-device VPN recommendations is how the device limit is counted. Two plans can both claim “supports multiple devices”, yet one counts concurrent connections, another counts devices ever bound to the account, and a third issues device slots that reset each billing cycle. When a family shares a single account, the three models behave completely differently: with the first, you're fine as long as not every device is online at once; with the second, replacing a phone once can cost you a slot.

Below we break this into three questions: how device limits are actually counted, whether one account can be shared by a family, and what happens when you exceed the limit. Then we cover setup steps for family sharing, a buying checklist, and how unlimited-device plans are allocated in real use. Descriptions of counting models here follow each provider's published terms and what the client device list actually shows.

Unlimited devices No cap on the number of devices under one account — each family member just installs the client.
110+ Countries / regions covered, with routes available in all the commonly used ones.
160+ Routes in total, spanning IEPL dedicated lines, relay and direct connections.
7 days No-questions-asked refund, so you can test whether the device count and routes fit before committing.

Three counting models for device limits

A device limit isn't just a number in the terms — it's a set of rules. The number is only the outcome; what shapes family use is the counting model behind it. There are three common approaches, and each is judged differently.

Model 1: Concurrent online devices

The server only looks at how many active connections exist at the same moment. Connect a phone, disconnect a laptop, and the slot is released. Families rarely have every device online at once, so this model is the friendliest for household use. Watch how “online” is defined: a client left running in the background with its connection still up usually counts as online.

Model 2: Cumulative bound devices

The first device you sign in from gets recorded in the device list, and it keeps occupying a slot even after being offline for months. Replacing a phone, reinstalling the OS, or signing in once from a virtual machine all consume slots, and you have to unbind them manually in device management. This is the model most likely to trip you up when devices change at home.

Model 3: Device slots that reset each cycle

A batch of slots is issued per subscription cycle and resets when the cycle begins. It sounds generous, but adding one extra device mid-cycle — or forgetting an old device in the list — can push you straight over the limit. Whether the reset date lines up with the billing cycle is another thing to confirm in the terms.

Counting model How it's judged Real-world result for family sharing What to watch for
Concurrent online devices Number of active connections at one moment Fine as long as not every device is online at once; disconnecting frees the slot Whether background connections count as online
Cumulative bound devices Record of devices signed in historically New phones and OS reinstalls consume slots; manual unbinding required Is self-service unbinding available, and does it take effect immediately?
Device slots per cycle Slots reset each subscription cycle Adding a device mid-cycle easily exceeds the limit Whether the reset date matches the billing cycle

To quickly tell which model you're on, run a small test: sign in on three devices, keep only one online, disconnect the other two, then open the device list and see whether the count drops. If it drops right away, it's a concurrent-connection model; if it doesn't change, it's cumulative binding.

Can one account be shared by a family?

The short answer: sharing within a household isn't the problem — how the plan counts devices and what the terms say is. To judge this, first separate two kinds of sharing.

Sharing login credentials vs. sharing a subscription link

Sharing login credentials means family members get the same username and password and each sign in through their own client. Sharing a subscription link means importing one subscription URL into clients on several devices. The first is account-level sharing, the second is configuration-level sharing, and they trip over different things.

The cost of sharing login credentials is mutual interference. On a plan that counts concurrent connections, a new device coming online can push out the oldest connection — the symptom is another device suddenly dropping. Traffic under the account is a single pool, so there's no way to tell who used how much. And once the password changes, every device has to sign in again.

The cost of sharing a subscription link is exposed credentials. The link itself is an account credential: anyone who has it can import and use it without knowing the password. Once it leaks outside the household, traffic gets consumed along with it, more people share the same exit routes, and a drop in performance is inevitable.

The safer way to do this inside a household: family members at the same address each use their own devices, with one person handling subscription imports and the device list; don't send the account or subscription link to anyone outside the household, and don't paste the subscription URL in public. That avoids the “who forwarded the link?” problem and saves you from repeatedly investigating unfamiliar entries in the device list.

Bottom line: Sharing within a household works, as long as you pick the right counting model. With concurrent-online counting, or a plan with no device cap at all, family sharing needs no extra steps; with cumulative binding, you have to budget for phone swaps and OS reinstalls in advance.

What happens when you go over the device limit

What you see when you exceed the limit depends on how the plan is built. There are three common behaviors:

  • New device can't connect: the client reports that the device limit has been reached, and devices already online are unaffected.
  • The oldest connection gets pushed out: the new device connects successfully while another device drops and has to reconnect.
  • All connections are reset: every device has to sign in again, or re-import the subscription.

Note that these limits generally apply at the connection layer: it's the new connection that gets rejected, and the account and subscription themselves are usually unaffected. The real risk comes from sharing a subscription link publicly — that's a credential leak, a completely different matter from “one extra device connected”.

Another common misconception is using “sign in by turns” to get around the limit: repeatedly signing in and out across several devices in a short window is easily flagged as abnormal behavior, and the result is a less stable connection rather than a saved slot. If you do hit the cap, the right order is to disconnect devices you're not using first, then connect the new one; on a cumulative-binding plan, unbind the old device in device management first.

Don't use “sign in by turns” to get around the device limit. Signing in and out repeatedly on the same account in a short window is easily flagged as abnormal behavior, and the result is a less stable connection rather than a saved slot.

Setting up family sharing

Once the counting model lines up, setting up family sharing isn't complicated — just work through the steps below.

  1. First count the devices at home that need to stay online long-term: phone, tablet, laptop, desktop and TV box each count as one, and always-on devices should be included first.
  2. Confirm the plan's counting model and find the device management page: do the terms say “concurrent online” or “cumulative binding”, and can you unbind devices yourself?
  3. Have one person handle subscription imports: open the client on each device and import the same subscription, rather than leaving the link sitting in chat logs or notes.
  4. Assign routes by device type: always-on devices like TV boxes stay on one fixed route, while phones and laptops switch as needed.
  5. Turn on split routing: set local sites and LAN traffic to direct connection, so only traffic that needs the route goes through the exit and pointless usage is avoided.
  6. Clean up the device list regularly: on a cumulative-binding plan, unbind devices you no longer use to free slots for new ones.

If you have a lot of devices at home, you can also deploy the client on a router so every device on the LAN shares one exit. In that case the server usually sees only the router's single connection, and only one device shows in the device list; the trade-off is that a router reboot takes the whole household offline, and the setup bar is higher. Whether router deployment is allowed is something to confirm in the terms before buying.

Unlimited devices: how it works in practice

A VPNAK account has no device cap: each family member installs the client on their own devices and imports the same subscription — no need to queue up over who connects first, and no need to unbind an old phone before switching. On the network side there are 110+ countries and 160+ routes, including IEPL dedicated lines, relay and direct connections, so the choice of commonly used regions is generous.

Signing up only needs a username and password — no email address required. Payment supports Alipay, WeChat and USDT, and clients cover five platforms: Windows, macOS, iOS, Android and Linux. Traffic is protected with bank-grade encryption, and there's a 7-day no-questions-asked refund, so you can test whether the device count or routes suit you before committing.

Platform Client type Tip for family sharing
Windows Desktop client Install separately on each computer, import the same subscription
macOS Desktop client Install separately just like on Windows, no extra slot needed
iOS Mobile client Each family member installs it; after a phone upgrade, import directly on the new device
Android Mobile client Same as above — no need to unbind the old phone first
Linux Desktop client Suits an always-on mini PC; just don't duplicate it with a router deployment

How traffic is divided is the variable that matters more for family sharing. Monthly plans reset on the activation date each month, and when you upgrade mid-term the price difference is prorated by remaining days; traffic packs last until used up and never expire. Traffic under an account is a single pool that family members consume together, so picking a tier by usage intensity is more practical than picking by device count.

Monthly plan Monthly traffic Suits this usage intensity
¥9.9 / month 60GB One or two devices, mainly web browsing, chat and light video
¥18 / month 250GB Everyday phone + computer + tablet combo, occasional video
¥28 / month 500GB Several devices online long-term, including always-on ones like TV boxes

If you just need to top up occasionally, traffic packs last until used up and never expire: ¥158 / 300GB, ¥358 / 1000GB, ¥658 / 3000GB. For family sharing, a traffic pack works well as a supplement to a monthly plan — unused data won't be wiped at the end of the month.

Checklist before buying a multi-device VPN

Run through the items below one by one and you'll have a good idea whether a plan suits a whole family.

  • ✅ The terms spell out the counting model: “concurrent online devices” or “cumulative bound devices”.
  • ✅ There's a device management page where you can unbind old devices yourself, with no support ticket required.
  • ✅ It's explicitly unlimited, or the slots on offer cover the always-on devices in your home.
  • ✅ Clients exist for Windows / macOS / iOS / Android / Linux, so every device can be set up individually.
  • ✅ The refund policy is clear — a 7-day no-questions-asked refund, for example, so you can back out if the device count doesn't fit.
  • ❌ It only says “supports multiple devices” without stating the model, and there's no device list to check.
  • ❌ Changing devices means contacting support to unbind, or waiting through an undefined cycle.
  • ❌ The subscription link is treated as something to forward freely, with no sense that it's a credential.

Bottom line: For family sharing, favor a plan that counts concurrent online devices or has no device cap at all. If a plan counts cumulative bindings, budget for phone swaps and OS reinstalls in advance, and confirm that self-service unbinding is available.

Common questions about device limits and shared accounts

Will sharing one account with my family be flagged as abnormal?

It depends on the terms. Family members at the same address each using their own devices is within what most plans accept by default; sending the account or subscription link to people outside the household is what triggers both the device cap and risk-control checks. Choosing a plan that's explicitly unlimited and allows household use saves you this judgment call.

Will my account be banned for exceeding the device limit?

The usual handling is to reject the new device's connection or push out the oldest one — the limit applies at the connection layer and generally doesn't affect the account itself. The real risk is sharing a subscription link publicly, which is a credential leak and a completely different matter from “one extra device connected”.

After switching phones, does the old device still count?

It depends on the counting model. With cumulative binding, the old device keeps occupying a slot until you unbind it manually in device management; with concurrent-online counting, it stops using a slot once it goes offline. With an unlimited-device plan there's nothing to handle — just import the subscription on the new phone.

Does unlimited devices mean I can share it with anyone?

No. Unlimited devices solves the device-count question inside a household; it doesn't mean the subscription link can be made public. The link is an account credential, and once it leaks, traffic gets consumed along with it and route performance suffers. Keeping use within your family members is the safer approach.