How are simultaneous device limits actually counted across phones, computers, tablets, and TVs? This article puts several services to the test on what happens once you hit the device cap, breaks down whether a family can realistically share one account, and weighs the real trade-offs of connecting through a router instead.
Most subscription services don't cap the total number of devices you've ever installed the client on — they cap how many devices are actively holding an encrypted connection at the same moment. In other words, a phone with the app installed but no active connection doesn't use a slot; a laptop, a tablet, and a smart TV each establishing their own tunnel each use one slot, regardless of brand, model, or operating system. It's purely about connection count.
This rule leads to a common misunderstanding: people assume the device limit adds up every device you've ever signed in on, so logging out of an old device won't free up room for a new one. In practice, it's the opposite — most services work on a real-time basis, releasing the slot the moment an old connection drops, so a new device can connect right away. What actually matters is how many devices are online at the same time during peak use, not how many gadgets are sitting in the house.
How a service handles going over the device limit varies a lot, and it's a big factor in real-world experience. Three common approaches show up:
| Behavior | What actually happens | Impact on family use |
|---|---|---|
| Blocks the new connection | The (N+1)th device gets an error on connect, saying the device limit has been reached | You have to manually disconnect another device before the new one can go online — the clunkiest experience |
| Kicks the oldest connection | The new device connects successfully, and the system automatically drops whichever device connected first | Older devices get disconnected out of nowhere, which is confusing to troubleshoot |
| No cap at all | No limit on device count — every device connects independently without affecting the others | No need to coordinate who goes first, which fits multi-person, multi-device households well |
For family use, the third approach is by far the most practical — there's no coordination overhead over who gets to connect first. That's also why, per CKVPN's plan details, device count is unlimited: one subscription lets phones, computers, tablets, and TVs in the same household connect at once without stepping on each other.
If a service doesn't cap device count, there's no technical barrier to a family sharing one subscription account: everyone signs in with the same credentials on their own device, or imports the same subscription link, without interfering with each other. But "technically possible" doesn't mean "no planning needed" — a few things are worth sorting out ahead of time:
Bottom line: as long as the service doesn't cap device count, a family sharing one account is a workable approach, and it's more cost-effective than everyone subscribing separately — as long as there's a basic household agreement on data usage pacing up front.
Another common approach is skipping per-device clients altogether and configuring the subscription directly on a home router, so every device in the house connects through it. This typically counts as just one device slot — from the upstream service's perspective, the only device establishing a connection is the router itself. Everything else in the house shares that single tunnel through the router, and the connection layer has no visibility into how many actual devices are behind it.
This sounds like a clean way to work around device limits, but there are a few noticeable trade-offs in practice worth knowing up front:
Overall, router-based access fits best when device slots are genuinely tight and configuring every device separately isn't appealing. If the service itself has no device cap, installing a client on each device directly is actually the easier path — a problem on one device only affects that device, troubleshooting is more straightforward, and there's no need to keep tweaking router firmware settings.
Whether connecting per-device or through a router, these details directly affect stability in multi-device setups:
Most services distribute server configurations through a single subscription link that the client periodically refreshes. When server lists change, there's no need to re-add anything manually — just refresh the subscription. In multi-device setups, every device imports the same subscription link and shares the same server list, but each device's currently selected server is independent and doesn't affect the others.
On some devices — especially routers and smart TVs — the system DNS setting can get overridden by the local network, causing domain lookups to bypass the encrypted tunnel entirely, known as a DNS leak. To check for this, look in the client for a "take over system DNS" option, and confirm the routing rules haven't mistakenly put key domains into the direct-connect list. This is usually handled by default on computer and phone clients, but router firmware often needs manual confirmation.
When multiple devices are online at once, the type of server matters more. IEPL dedicated lines run on private international carrier links, separate from public internet traffic, so capacity stays more stable under multi-device load. Relay and direct routes depend on shared public network paths and are more prone to slowdowns during peak hours. For multi-device households, servers labeled as IEPL dedicated lines are the better choice, especially when multiple people are on video calls or transferring large files at the same time.