1. Multipath rather than single-line failover
Two or more usable routes are maintained at once, with quality sampled every two seconds. When the primary exceeds its loss threshold, traffic moves within 80 ms without a new handshake.
Acceleration quality comes down to three things: how loss is handled, how fast a degrading route is replaced, and what encryption costs you. Here is how we approach each, with figures you can verify.
Six concrete differences
Each point maps to something measurable rather than an adjective.
Two or more usable routes are maintained at once, with quality sampled every two seconds. When the primary exceeds its loss threshold, traffic moves within 80 ms without a new handshake.
Intercontinental traffic prefers our own transport instead of public egress, which keeps jitter noticeably lower at peak hours. This is why we invest in transport rather than inflating node counts.
The standby route has its session state ready 300 ms ahead, so handovers between Wi-Fi and cellular — or entering and leaving a tunnel — are barely perceptible.
Mobile defaults to ChaCha20-Poly1305; desktops can switch to AES-256-GCM. Both support forward secrecy, so the only real difference is efficiency on mobile chips.
We keep your email, subscription state and device count. No phone number, no access records, no connection timing. What we do not need, we do not store.
There is no script library. Attach a diagnostic report and you will get advice based on the actual handshake result and quality samples.
Side by side
The three approaches differ in cost structure, and the long-run experience differs accordingly. The table compares the dimensions where users most often get caught out.
| Dimension | QuickQ | Free public proxy | Mainstream VPN |
|---|---|---|---|
| How routes switch | Multipath, moves in 80 ms | None, manual reconnect | Single-line reconnect |
| Network change behaviour | Pre-warming, near seamless | Always drops | Usually reconnects |
| Peak-hour jitter | Private backbone preferred | Varies wildly with public egress | Depends on purchased links |
| Encryption | ChaCha20 or AES-256, selectable | Often none | Usually one fixed option |
| Data retained | Email and subscription state | Frequently full access logs | Often connection logs |
| Disconnect protection | Built in | None | Available on some plans |
| Per-app routing | By process and domain | None | Mostly global mode only |
| Refund terms | 14 days, no questions | — | Often conditional |
Technical notes
Traditional VPN protocols assume a reasonably stable path and slow down sharply once loss persists. Cross-border links are the opposite: loss is normal and lasts minutes to hours. Nova is designed for that condition.
Who uses it
Several overseas dashboards per day, where slow page loads cost real working time. The link score tells them at a glance whether a route is worth keeping.
Long-lived sessions are the priority. Path pre-warming keeps voice calls and terminal sessions intact while moving between networks.
One router configuration covers every device, sending streams and downloads down the high-bandwidth path while matches use the low-jitter one.
It has no time limit and needs no payment method. One look at the link score will tell you whether QuickQ is worth keeping on your network.