1. Decision order: use case first, route second, price last
Three use cases, three completely different weightings
Comparing cross-border network services as if they were one big category is the fastest way to buy the wrong thing. The same price bracket can hide completely different routes and completely different exit capacity. Before you compare anything, sort your own use into one of the three groups below — everything that follows depends on it.
Type 1: Web pages, email and research
This kind of traffic is short-lived, low-bandwidth and tolerant of brief interruptions. A single request is tens to hundreds of KB, and if a page fails to load you can just refresh. For this, absolute latency is not the deciding factor; what matters more is whether DNS resolves reliably and whether the connection still works during peak hours. Direct routes are perfectly adequate off-peak and cost the least.
Type 2: Streaming and AI tools
This traffic is long-lived, needs sustained bandwidth and is sensitive to packet loss. Video has to keep buffering ahead, and AI chats need the session to stay alive. As packet loss rises, video first drops its bitrate and then stalls, while AI tools show cut-off replies or request timeouts. This is the use case that justifies paying a little more for route quality, because what you save in price you pay back in waiting, every single day.
Type 3: Cross-border work and file transfer
The pattern here is online all day, upload as well as download, and no interruptions allowed. Video calls are the most sensitive to jitter — a few tens of milliseconds is enough to make voices break up. Go straight to the dedicated-line tier for this, and check peak-hour behaviour first, because that is exactly when meetings happen.
Why price should come last
Price is the result of route type, exit capacity and support costs — not an independent variable. Picking a price first and then hunting for a route means letting the result constrain the cause. The sensible order is: use case, route type, bandwidth and data, devices and sharing, refunds and support — and only then pick the cheapest option among those that satisfy the first five.
Three common ways people decide backwards
The first is buying the cheapest tier, discovering within a week that it is unusable at peak, and paying again to upgrade. The second is counting nodes without looking at where they are, then finding that the region you actually use has only one entry point. The third is being drawn in by a low average monthly price on a long plan, paying for a long period up front, and then stopping halfway. All three have the same flaw: the decision order is reversed — price filters the options first, and then you try to find something suitable among what is left.
Log a week first, then choose a tier
If you are not sure which group you fall into, the easiest approach is to log one week: roughly how long you are online each day, what kind of services you open most, and whether anything needs to stay connected for hours. After a week, both usage and scenarios become concrete, and choosing a tier stops being a gut feeling. You will use this log again in the billing chapter.
How to use this guide
If you want to get connected right now, start with the Quick Start guide, which walks through creating an account, getting your subscription and importing it into a client as one straight line. This page is a reference manual — come back to the relevant chapter when you wonder why a route is slow or what the difference between two price tiers actually is. The split is simple: one page answers 'how do I do this', the other answers 'why choose it this way'. For prices and tiers, go to the pricing page; for the actual region list, go to the global locations page.
One test that works
No adjective on a marketing page counts as evidence. Only three things do: the text of the terms, route performance you can measure yourself, and a checklist you can tick off item by item.
2. Route Types: Cost and Experience Differences Between IEPL, Relay and Direct
How each route type is built
A direct route connects your device straight to an overseas exit server over the public international gateway. A relay adds a relay node between you and the overseas exit: you connect to the relay first, and the relay forwards to the exit. An IEPL dedicated line runs over an international Ethernet private line, physically or logically separated from the public international gateway, so there is a relatively fixed path from entry to exit.
Where the cost difference comes from
The cost of a direct route is mainly bandwidth and address resources in an overseas data centre, with low marginal cost — which is why it can be the cheapest. A relay adds a domestic or near-shore forwarding segment, billed by bandwidth, so the cost goes up. An IEPL line is billed by dedicated-line bandwidth, and the price per unit of bandwidth is far higher than public gateway capacity. That is the only reason it is expensive, and the only reason it is stable. Once you see that, you understand why the dedicated tier costs more for the same amount of data: it is not a markup, it is a different cost structure.
Where the experience difference comes from
Direct-route experience depends on how congested the public international gateway happens to be. A direct route at 3 a.m. and the same route in the evening can behave like two different lines. A relay improves the segment between you and the relay node, replacing the most congestion-prone part with something more controllable, at the cost of one extra hop and slightly higher latency. An IEPL line improves the whole path: stable latency, low jitter, low packet loss — at the cost of price.
| Route type | Path | Cost | Latency stability | Peak-hour performance | Best for |
|---|---|---|---|---|---|
| Direct | User → public international gateway → overseas exit | Lowest | Highly variable | Clearly affected by gateway congestion | Web browsing, email, research |
| Relay | User → relay node → overseas exit | Medium | Fairly stable | Smoother than direct, one extra hop | Video, everyday work, AI tools |
| IEPL dedicated line | User → dedicated line entry → overseas exit | Highest | Stable | Least variation | Live meetings, long connections, file transfer |
Route types are labelled by the operator, and a label still needs verifying yourself — see the next section.
How to tell which type a route is
Three ways. First, look at the naming: a serious provider marks the route type in the node list, while vague labels like 'high speed' or 'optimised' usually mean direct. Second, check whether one region has several tiers: a region with a single route can hardly cover different use cases, whereas direct, relay and dedicated options suggest the operator has put work into the path. Third, measure it: test the same target repeatedly at peak hour — a dedicated line should trace a flat curve, while a direct route will visibly rise and fall.
Use mtr to see the path and packet loss
The command-line tool mtr shows both the path and the packet loss at every hop. Do not just look at the last hop: look at which hop the loss starts from. If it starts inside the domestic segment, the problem is at the local gateway. If it starts at some middle hop on the international segment and continues to the exit, the problem is that segment. If only the last hop loses packets, the exit data centre may be rate-limiting that protocol.
mtr -rwc 60 example.comWhat the flags mean: -r outputs a report, -w uses wide output so nothing is truncated, and -c 60 sends 60 probe packets. Sixty samples are enough to show whether the loss is persistent. Run the test at peak hour — clean off-peak numbers tell you nothing.
Route coverage of this service
VPNCQ currently offers 120+ countries / 150+ routes, covering common regions such as Japan, Hong Kong, the United States, Singapore, France and Canada. A single region usually has several routes to choose from. The suggested order is: filter by region, then by route type, then decide by how it actually performs that evening. The full list is on the global locations page, grouped by region with each route's type and streaming support.
A common misconception
'Dedicated is always faster than direct' does not hold. A dedicated line wins on stability, not on peak speed. If all you do is look things up during the day, a direct route may well hit a higher peak; the real value of a dedicated line shows up at peak hours and on long connections. The reverse — 'direct is always cheaper' — is not entirely true either: if instability makes you switch services repeatedly, the total cost ends up higher.
Route choice is not a one-time decision
The same route behaves differently at different times. Test once in each of the hours you normally use, and write the results down, so next time you switch you have a reference instead of starting from zero.
3. Bandwidth and Concurrency: Three Different Things Behind One Number
One number, three meanings
The 'bandwidth' on a marketing page usually means one of three completely different things: total data-centre outbound bandwidth, per-user speed cap, or shared pool capacity. Total outbound bandwidth is the capacity of the whole exit server; it sets the ceiling for all users combined and has no direct bearing on how fast one person can go. The per-user cap is the rate limit the operator applies to a single account, and that is the number that actually determines your peak. A shared pool divides the outbound capacity among everyone online at that moment, so the real speed depends on how many people are using it.
| Term | Meaning | What it means for you |
|---|---|---|
| Data-centre total outbound bandwidth | Outbound capacity of the whole exit server | Sets the overall ceiling at peak times |
| Per-user speed cap | The rate limit applied to one account | Sets the peak for a single device |
| Shared pool | All users draw on the same outbound capacity | Real speed at peak depends on how many are online |
Why 'huge total bandwidth' does not mean 'fast for you'
If an exit server's outbound capacity is shared, the more people online at peak, the less each one gets. That is overselling: selling more capacity than actually exists. Moderate overselling is normal in the industry, because not everyone uses full speed at the same moment; excessive overselling shows up as everyone slowing down together at peak. The only way to tell is repeated peak-hour testing over several days — there is no shortcut.
Concurrency is not the same as device count
Concurrent connections means the number of connections open at one moment — a single browser tab can hold anywhere from a few to dozens. Simultaneous devices means how many devices are using the same account. The two are often confused. What actually matters to you is whether the service charges by device count, and whether running several devices at once makes them compete for bandwidth.
How much bandwidth 4K and meetings really need
Going by the typical bitrates streaming platforms use, one 4K stream usually sits in the teens to low twenties of Mbps, and 1080p in the single-digit Mbps range; video meetings need far less bitrate but far more tolerance for jitter. These are general platform figures, not promises from this service. What you actually need to confirm is whether a single device can hold the speed you need at peak hour.
How to test speed properly
A single speed test is almost worthless. Do three things consistently: fix the target (the same test endpoint or the same video), fix the time window (the same hour on three to five consecutive days), and fix the number of runs (at least three each time, take the median). Only then are the numbers comparable. Also watch the local side: Wi-Fi signal strength, whether the router is busy with something else, and whether the system is downloading updates in the background — all of these contaminate the result.
Peak hour is the only real exam
Congestion on international gateways follows a clear daily pattern, usually from evening into late night. Off-peak, any route can produce a beautiful number. So the only thing worth judging a route on is how it behaves at peak: does it open pages reliably, does video keep re-buffering, do meetings break up. Those three questions are more direct than any speed figure.
First work out which layer the problem is on
If things get clearly worse at peak and are fine off-peak, the problem is most likely link congestion rather than your local setup. Switch to another route in the same region for comparison first, then judge whether the service itself is at fault.
4. Billing Models: Monthly Plans vs Data Packs
The real difference between the two billing models
A monthly plan buys the right to use the service for a period, with data resetting each month; a data pack buys a fixed total allowance that lasts until it runs out. The first suits people who use it every day, the second suits people who use it intermittently. The difference is not in the unit price but in what happens to the unused part: unused monthly data goes back to zero at reset, while an unused data pack balance stays there.
Tiers offered by this service
There are three monthly tiers: ¥9.9/month with 60GB, ¥18/month with 250GB and ¥28/month with 500GB. There are three data packs: ¥158/300GB, ¥358/1000GB and ¥658/3000GB, valid until used up, never expiring. Monthly data resets each month on the activation date, and the price difference for a mid-term upgrade is prorated over the remaining days.
| Item | Monthly plan | Data pack |
|---|---|---|
| Billing unit | Per month | Per total volume |
| Allowance handling | Resets monthly on the activation date | Valid until used up, never expires |
| Tiers on this site | ¥9.9/month 60GB · ¥18/month 250GB · ¥28/month 500GB | ¥158/300GB · ¥358/1000GB · ¥658/3000GB |
| Changing mid-term | Upgrade difference prorated over remaining days | Buy another pack as needed |
| Best for | Daily use | Occasional use, backup |
How to estimate your monthly usage
Do not guess. The easiest approach is to log one week: how long you were online each day and what you mainly did. After a week, multiply by four and leave a little headroom. If one day in that week was heavy use (long video or large file transfers), count that day separately. The point is to pick the right tier, not to be accurate to the gigabyte — the gaps between tiers are wide enough that a rough range is all you need.
How mid-term upgrades are calculated
When a monthly subscriber moves up to a higher tier mid-term, the price difference is prorated over the remaining days, so you do not pay for a whole extra month. This rule is friendly to anyone who wants to test the water on a small tier: run the ¥9.9 tier for a week, confirm the routes work, then upgrade — far safer than buying the top tier straight away.
A mixed strategy
A common combination is a monthly plan sized for everyday use as the baseline, plus a data pack for surprises: a week-long business trip, a batch of files to send at short notice, or a platform update that suddenly needs a big download. A data pack does not expire, so keeping one costs you nothing — that is its biggest advantage over a monthly plan.
Payment methods and activation
Alipay, WeChat Pay and USDT are supported. The first two suit most users and activate immediately on payment; USDT suits situations where regular payment channels are inconvenient. One thing to keep in mind when choosing: refunds normally go back through the original payment channel, so whichever method you pay with is the route your refund takes.
Three buying patterns to avoid
The first is buying a very long term up front to lower the average monthly price, then stopping halfway. The second is buying the top monthly tier when you only use it a few days a month. The third is starting with a data pack, running out, and realising you actually use it every day — at which point a monthly plan is the right move. The test is simple: log two weeks; if you use it every day, it is a monthly-plan case, and if you use it two or three days a week, it is a data-pack case.
5. Devices and Family Sharing: What Unlimited Devices Really Means
The limits of unlimited devices
Unlimited devices means you are not charged per device: the account works on as many devices as you like, with no extra fee for the second or third. It solves the 'one person, several devices' problem — phone, tablet, laptop and the desktop at home can all be set up without picking just one to save money. It does not change the fact that bandwidth is shared: the more devices online at once, the less each one gets.
Supported platforms
The client covers five platforms: Windows, macOS, iOS, Android and Linux. Desktop suits a fixed desk, mobile suits life on the move, and Linux suits servers and development machines. The same account can log in on all of them. Clients and subscriptions are obtained from the user panel; no direct static installer links are provided on the site.
Two ways to share at home
The first is installing a client on each device and importing the subscription separately. It is simple to configure and devices do not affect each other, but each one has to be maintained on its own. The second is deploying on the router, so every device at home goes through the same route automatically. That gives central management and zero-config onboarding for new devices, but it demands router performance — low-end routers easily become a bottleneck when encrypting and forwarding — and all devices share one route, with no per-device split.
What to watch when sharing an account
Creating an account needs only a username and password, with no email address required. That also means those two things are the only credentials: giving the account to family means giving them the credentials. Changing the password invalidates every device already logged in, so they need to import again. If it is only a temporary loan, changing the password afterwards is the simplest way to close it off.
Setting priorities when many devices are online
Home bandwidth is shared, so several devices watching 4K at once will squeeze each other. In practice, give priority to whatever needs stability: the computer in a meeting and the desktop mid-transfer come first, while video on phones and tablets can wait. If the router supports QoS, putting the meeting device on high priority makes a bigger difference than switching routes.
What to do when you change devices
A subscription is a configuration, not a licence tied to one device. After changing phones or reinstalling the system, just import the same subscription on the new device and delete the old configuration. There is no unbinding request and no extra charge for changing devices.
One detail that is easy to miss
Mobile systems suspend apps in the background, so the connection has to be re-established when you return to the app. If you notice a few seconds of waiting every time you switch back, that is the system's battery-saving policy, not the route. Adding the client to the battery optimisation whitelist helps; the exact location differs by brand, and on Android it is usually under 'Battery' or 'App management'. Full first-time setup steps for each platform are broken down in the Quick Start guide.
6. Refunds and Support: What Guarantees to Expect
Three things to check in a refund policy
Period, conditions and process. The period is how many days you have to apply; the conditions are when a refund is allowed and whether you must give a reason; the process is where to submit, how long it takes and where the money goes back. Only a policy that states all three is usable — 'refunds supported' on its own says nothing.
Refund commitment of this service
A 30-day refund, no questions asked. No questions asked means you do not have to explain why, and there is no 'how much data you used' threshold. You can apply within 30 days of your first payment, and the refund goes back through the original payment channel. The point of this commitment is that every judgement about route quality can be verified by you after paying — and if it does not hold up, you get your money back.
What support should include
Three things: a way to submit a problem, documentation you can check yourself, and a predictable response rhythm. A way to submit means a ticket system or a clearly stated support channel, not just an address; documentation means you can find answers to common questions on your own; a response rhythm means roughly how long a reply takes. The most overlooked of the three is documentation — most questions are already answered there, and a clearly written doc saves half the waiting.
Four things to do before opening a ticket
First, confirm your local network works (can you get online without the service connected). Second, try another route in the same region. Third, restart the client. Fourth, record the symptoms: which site or app, at what time, and what error appears. Submitting with those four in hand gets you a much faster answer, because the first round of troubleshooting is already done.
Rule out false alarms before asking for a refund
Some problems look like route failures but are local settings: a large system clock offset breaks the handshake, an abnormal DNS setting makes some domains unresolvable, and an outdated client can be protocol-incompatible. Once you have ruled out all three and it still does not work, going through the refund process is not too late — a refund is the last step, not the first.
| Check | What you should see | Typical vague wording |
|---|---|---|
| Time limit | A clear number of days; this service offers a 30-day refund, no questions asked | 'Refunds supported', with no number of days |
| Conditions | No questions asked, with no usage threshold attached | 'Subject to usage' |
| Process | A ticket form or a clearly stated application entry point | A single address that nobody answers |
| Refund route | States that the money returns to the original payment channel | No refund route stated |
About long-term promises
Any claim of 'long-term validity' or 'lifetime' only counts once it is written into the terms. The test is direct: open the terms page and see whether the sentence is there and whether conditions are attached. Written in, it is a commitment; not written in, it is marketing. The data pack rule 'valid until used up, never expires' is written into the facts, and it means the allowance does not lapse simply because time passes.
7. How to Spot Common Traps
Overselling: everyone slows down at peak
Overselling means selling more capacity than the actual outbound capacity. Moderate overselling is normal, because not every user runs at full speed at the same moment; excessive overselling looks very consistent: everything is fine off-peak, everyone slows down at peak, and switching routes changes nothing. To identify it, test the same target at the same time on three to five consecutive days — if it drops at the same point every time, you have your answer.
Inflated node counts: numbers that do not match the list
Claimed node counts are easy to pad: one entry split into several names, several cities in one region counted as several countries, temporary test nodes included in the total. Spotting it is just as easy: after logging in, count the regions actually available, check whether each region really has its own entry point, and check whether several nodes in the same city differ only by name. Numbers can be printed on a marketing page; a list has to match item by item. The full list for this site is on the global locations page, where you can check it line by line.
Going dark: the most expensive trap
The industry calls it 'running off' when an operator suddenly stops the service and cannot be reached. It is not a route problem but an operational one, and what you lose is the entire prepaid amount. There are warning signs: only payment methods that are hard to reverse, missing or extremely thin terms, content that never updates, prices clearly below the cost line, and support that only ever sends automated replies. Conversely, complete terms, several mainstream payment methods and content that keeps being updated at least show the operator is investing for the long term.
Price traps: low average monthly cost on long plans
'Buy two years, get two years free' stretches the decision cycle out very long, while route quality changes month by month. The sensible approach is to verify on the shortest term first, and only consider a longer term once it works. At any point, prepaying for longer than you are confident you will use it, just to lower the average monthly price, is taking on unnecessary risk.
Data allowance traps
Three common ones: describing a monthly reset as a cumulative allowance, when it is actually a total rather than a monthly amount; a data pack that lists an expiry date, contradicting 'never expires'; and counting upload and download separately when actual usage is the sum of both. When reading the terms, look for three words: reset, validity period, and billing direction.
Client download traps
Clients should only come from official channels. A client repackaged by a third-party site may carry extra configuration, and any client that asks you to turn off system security settings should be abandoned outright. A legitimate client does not need you to disable your firewall, and it does not need you to install a root certificate of unknown origin.
Privacy wording traps
The more information a registration form asks for, the larger the exposure. The sensible approach is minimisation: only what is needed to identify the account. This service does not require an email address to register — a username and password are enough — which is one way of reducing personal data exposure. For how to verify a no-logs claim, the article how to verify a no-logs VPN has a more detailed checklist.
| Symptom | Possible underlying problem | How to check |
|---|---|---|
| Normal off-peak, slow for everyone at peak | Oversold outbound capacity | Test the same target at the same time for three days running |
| Many regions listed, few actually usable | Inflated node count | Count the regions actually available after logging in |
| Terms page blank or only a few lines | Insufficient operational investment | Check whether the refund period, conditions and process are all present |
| Price clearly below comparable services | Unsustainable cost structure | Buy the shortest term first to verify |
| Data pack lists an expiry date | Contradicts 'never expires' | Search the terms for 'validity period' |
The patterns above describe practices that exist in the industry; they are not aimed at any specific service.
8. Pre-Order Self-Check List
Demand side: write it down first
Before ordering, write your requirements in three sentences: what the main use is, roughly how long you are online each day, and how many devices will be used at once. If you cannot write those three sentences, it is not time to order yet — go back and keep the log from the previous chapter for a week first.
Ten items to confirm one by one
- Use case classified: web research, streaming and AI tools, or cross-border work — pick one as the main one.
- Usual regions identified: list at least two backup regions so you are not stuck when a single entry point fails.
- Route types clear: whether the same region offers direct, relay and dedicated options.
- Bandwidth terms clear: what the per-user cap and the shared pool are, and whether peak-hour tests exist.
- Billing model chosen correctly: monthly plan for daily use, data pack for a few days a week.
- Device count confirmed: devices are unlimited, but work out how many will be online at peak together.
- Platform coverage confirmed: whether you use Windows / macOS / iOS / Android / Linux.
- Payment method available: at least one of Alipay, WeChat Pay and USDT works for you.
- Refund terms read: period, conditions and process all line up.
- Registration data minimised: no email address required, just a username and password.
Technical side: two commands
Once connected, use two commands to confirm the exit and DNS resolution are correct. The first checks the exit address and where it is registered; the second checks which server DNS resolution goes through. If both match expectations, then look at application-level behaviour.
# 1) Check the exit: replace the example address with an IP lookup service you trust
curl -s https://example.com/ip
# 2) Check DNS: pick one line for your system
scutil --dns | head -20 # macOS
resolvectl status | head -20 # LinuxThe addresses in the examples are placeholders — replace them with a lookup service you trust. The commands themselves involve no account credentials, so they are safe to run. If the exit address still shows a local address, the proxy is not actually carrying your traffic; go back to the client and confirm the connection state.
Which tier to pick: a comparison table
| Usage intensity | Suggested starting point | Why |
|---|---|---|
| An hour or two of web and email a day | ¥9.9/month 60GB | Low bandwidth, short connections; the smallest tier is enough |
| Video or AI tools every day | ¥18/month 250GB | Long connections and sustained bandwidth need a bigger allowance |
| Whole family, several devices, mostly 4K | ¥28/month 500GB | Shared across devices, the allowance drains fast |
| Only a few days a month | Data packs from ¥158/300GB | Valid until used up, never expires, nothing wasted |
These are starting suggestions; the actual tier should follow the usage you logged over a week. Full tiers and details are on the pricing page.
Suggested trial order
The suggested order is: run the smallest monthly tier for a week, covering at least one peak hour; once the routes are confirmed working, decide whether to upgrade the tier or add a data pack. The advantage is that each step costs little, and what you are verifying is your own real usage, not someone else's review. If it turns out to be unusable within the week, the 30-day refund is still within its window.
Two extra points for business trips
For a short business trip, look at the hotel network as well as the route: some hotel networks block certain ports, which shows up as the client saying it is connected while pages will not load. In that case, switch protocol or port first, then judge whether the route is at fault. For how much data to take on a trip, the article VPN for business trips breaks it down by trip length.
9. Common Questions About Buying
Can I have a monthly plan and a data pack at the same time?
Yes. They are separate allowances: the monthly plan resets each month on the activation date, and the data pack lasts until used up and never expires, so they do not conflict. The usual pattern is a monthly plan as the baseline plus a data pack for sudden heavy usage. See the pricing page for the exact tiers.
Devices are unlimited — can I share the account with friends?
Unlimited devices means you are not charged per device; the account itself has only two credentials, a username and a password. Sharing the account means sharing the credentials, and changing the password invalidates every logged-in device. Sharing within a household is common practice; sharing outside it is a trade-off you have to weigh yourself.
When does the 30-day refund period start?
It starts on the day of your first payment, and you can apply within 30 days without giving a reason. The refund goes back through the original payment channel. This commitment covers the first payment; renewals and later data pack purchases do not restart the clock.
Why does one region have several route types?
Because different uses place different demands on the path. Direct costs the least and may peak higher, which suits daytime research; a relay improves the most congestion-prone segment, which suits video and everyday work; an IEPL dedicated line has stable latency and low jitter, which suits live meetings and long connections. Offering several tiers in one region is what makes choosing by use case possible.
Monthly data resets — does unused data roll over?
No. Monthly plan data resets each month on the activation date, and resetting means the meter starts again; unused data is not carried over. If you want an allowance that does not lapse with time, choose a data pack: valid until used up, never expires.
A one-week business trip: which is the better buy?
For a one-week trip, a data pack is the first thing to look at, especially if you only use it a few days a month. It lasts until used up and never expires, so the remaining balance is still there for the next trip. If you travel so often that you are on the road every week, that is really a daily-use case, and a monthly plan fits better.
What information is needed to create an account?
No email address is required — a username and password are enough. That is also a way of reducing personal data exposure: the less you fill in, the smaller the surface. Those two things are the only credentials for the account, so keep them safe.
Which payment methods are supported?
Alipay, WeChat Pay and USDT. The first two activate immediately on payment, and USDT suits situations where regular payment channels are inconvenient. Refunds normally go back through the original payment channel, which is worth factoring in when you choose.
Which platforms do the clients support?
Five platforms: Windows, macOS, iOS, Android and Linux. Clients and subscriptions are obtained from the user panel; no direct static installer links are provided on the site. First-time setup steps are in the Quick Start guide, broken down by platform.
For anything not covered here, start with the FAQ page, which is organised into four groups: account and subscription, connection and troubleshooting, speed and routes, and billing and refunds. Streaming region and resolution questions are on the streaming page. To see the practical difference between free and paid first, the article free VPN vs paid VPN ran the same set of target sites through both.