Pre-launch: FlashPath VPN is not yet open for purchase. This page describes the planned MVP service — final locations, terms, and prices will be published before sign-up opens.

A private connection, wherever you go.

FlashPath VPN encrypts your internet connection and lets you choose the region it goes through — for travel, remote work, and everyday use on networks you don’t control. Everything you need day to day lives in the app; this website is where you subscribe and read up before you start.

  • Planned as one account, one plan for all customers
  • Designed to run on RAM-only servers
  • Operated by a company registered in Canada
  • In the app: sign in, connect, switch location, check and renew your plan — no need to return to the website

Connection speed and the availability of individual websites and services vary by network, location, and the policies of those services. FlashPath VPN does not guarantee access to any particular site or service.

FlashPath VPN ACCOUNT PREVIEW
Not connected
Choose a location, then connect

Illustrative interface preview only — not live server status. Final locations and availability are shown in your account at launch.

How it works

Subscribe once — on this website or in the app — then do everything else in the app. The same flow on a short trip or a long stay away from home.

STEP 01 · WEB OR APP

Subscribe & create your account

Start here on www.swiftnetworktech.com or directly in the FlashPath app and choose a plan duration. One account, one plan for all locations — no separate plans per country or per type of traveller. Subscriptions bought in the app use Apple / Google billing; subscriptions bought on the web use web checkout. Both unlock the same account. Final terms will be published at launch.

STEP 02 · IN THE APP

Sign in and choose a location

Open the app, sign in with the same account, and pick the connection region that suits you — for example, a U.S. region while you are travelling outside the United States, or the region closest to you. The current location list is shown in the app before you connect.

STEP 03 · IN THE APP

Connect, switch & manage — all in the app

Tap to connect in the app. Traffic between your device and the FlashPath VPN server is designed to be encrypted. Disconnecting, switching locations, checking your plan and expiry, renewing, and updating account settings are all planned to be done in the app, without returning to the website.

For travel & extended stays

If you spend time away from home — on business, studying, visiting family, or living abroad for a stretch — FlashPath VPN lets you keep using a familiar connection region of your choice, on hotel, airport, café, and other shared networks.

For remote work & everyday use

Working from a coworking space, a rental, or public Wi-Fi? An encrypted connection adds a layer between your device and the local network. Which location you use, and what you use it for, is up to you.

Connection locations

Phase 1 is planned to focus on North America, including three U.S. regions, with the West Coast region shared across all customers. Additional locations may be added over time. The confirmed list will be shown in your account when the service launches.

United States — West CoastLos Angeles / San Jose area
Phase 1 · Main
United States — East CoastNew York / Virginia area
Phase 1 · Main
United States — CentralChicago / Dallas area
Phase 1 · Main
CanadaToronto / Vancouver area
Phase 1
More regionsFurther locations are evaluated based on demand and provider availability
Planned
Choosing a region: in general, a region closer to you — or closer to the services you normally use — tends to give a more responsive connection. Actual performance depends on your local network and cannot be guaranteed for any specific use.

Privacy, by design

FlashPath VPN is built around a simple idea: a connection service should need as little information about your activity as possible.

Encrypted connection

Traffic between your device and the FlashPath VPN server you connect to is encrypted, so it is not readable in plain form by the local network you are on.

RAM-only servers

Servers are designed to run in memory only, without writing connection activity to disk. This is a technical design choice intended to limit what data exists on a server at all.

Canadian company

FlashPath VPN is operated by SWIFT NETWORK TECHNOLOGIES LTD., DBA FlashNet, a company formally registered in Canada, under the domain www.swiftnetworktech.com. Details of what account information is kept, and why, will be set out in the Privacy Policy published before launch — that policy is not yet published, and this page is not a substitute for it.

What this does not mean: no connection service can make you completely anonymous online, and FlashPath VPN does not claim to. Websites and apps you sign into can still recognise your account, and you are responsible for using the service in line with applicable laws and the terms of the services you use.

The app does it all. This website gets you started.

That is the product split, plainly: the FlashPath app is the full product — every function on this page can be completed in the app. This website is the subscription entry point and the information display — what FlashPath is, where you can connect, what it costs, and where to download the app. The website itself does not create a connection; on iOS and Android a tunnel must run in a native app built on Apple’s NetworkExtension and Android’s VpnService (see the technical plan below).

In the app · Full product

Everything, in the FlashPath app

iOS and Android. If you never visit this website again after downloading, you should lose nothing.

  • Create account & sign in — register, sign in, and stay signed in on your devices
  • Subscribe & renew — view durations, subscribe, renew, and restore purchases via Apple / Google billing inside the app
  • See your plan — current plan, status, and expiry date, at a glance
  • Choose & switch location — full Phase 1 list, switch any time per plan terms
  • Connect & disconnect — one tap, with live connection status
  • Manage your account — account details, subscription management, and support entry
  • Read the essentials — privacy summary, data-use declaration, and help, shown in the app before purchase or use as the stores require
On this website · Entry & information

Subscribe and read up, here

For discovering FlashPath, subscribing without the app, and checking the details before you decide.

  • Product information — how it works, locations, privacy design, and the technical plan on this page
  • Subscription entry — choose a duration and subscribe via web checkout; it creates the same single account you sign into in the app
  • Download the app — links to the App Store and Google Play listings once the apps are released
  • Plan & account basics — sign in on the web to check plan status and manage billing for a web subscription
  • Policies & help — privacy policy, terms, and FAQ
  • Not on the web: connecting. Choosing a location here is information only. The actual connection, switching, and disconnect happen in the app — a web page cannot create the tunnel on iOS or Android.
FlashPath app — preview TAP A TAB · ILLUSTRATIVE ONLY, NOT LIVE

Connect screen

Your daily screen. Pick a location, tap once, see that you are connected.

  • One-tap connect / disconnect, with status and current location
  • Full location list — US West, US East, US Central, Canada (Phase 1)
  • Switch location in the app, without reopening the website

Account & plan screen

Everything about you and your plan, in the app — whether you subscribed on the web or in the app.

  • Signed-in account, plan name, status, and expiry date
  • Manage account details and sign out of devices
  • Support entry and the in-app privacy / data-use declaration

Subscribe & renew screen

Subscribe or renew without leaving the app. In-app subscriptions are billed by the store, as Apple and Google require.

  • 7 days · 30 days · 90 days · 12 months — one plan, duration only
  • Price, duration, and auto-renewal terms shown before you buy, plus Restore Purchases
  • A web subscription and an in-app subscription unlock the same account — sign in once, use everywhere

Preview of the planned app screens. The native apps are in development and go through Apple and Google review — including the VPN declarations in the technical plan — before release. Until an app is listed in the stores, treat it as not yet available; we won’t announce a date we can’t stand behind.

Same functions, two places — at a glance

FunctionIn the appOn this website
Create account / sign inYes — fullYes
Subscribe / renewYes — via Apple / Google billingYes — via web checkout (subscription entry)
View plan, status & expiryYes — fullYes — for your web account
Manage account & subscriptionYes — fullYes — billing basics for web subscriptions
Choose / switch locationYes — and it takes effectInformation only — list is displayed, selection happens in the app
Connect / disconnectYes — the connection itselfNo — a web page cannot create the tunnel
Product info, privacy, tech plan, FAQYes — essentials & declarations in-appYes — full version here
Download the app—Yes — store links here
One account, two ways to pay — kept separate as the stores require. Subscribe on the web and you pay by web checkout, outside the apps. Subscribe in the app and you pay through Apple In-App Purchase or Google Play Billing, with their price, renewal, and cancellation handling. The app does not send you to the website to pay, and the website does not replace the app for connecting. Either way you get the same single FlashPath account and the same plan.

Technical plan: store requirements & server choice

Research checked 2026-11-15/16 against official sources read live — Apple App Store Review Guidelines Guideline 5.4, Google Play “Understanding Google Play’s VpnService policy”, and AWS Lambda Pricing — plus indexed secondary sources as flagged below. This is a technical summary, not legal advice. Store policies and prices change; re-check the current documents and pricing pages at submission and purchase time.

Verified live: developer.apple.com — App Store Review Guidelines · support.google.com — VpnService policy · aws.amazon.com — Lambda Pricing

iOS · APP STORE — GUIDELINE 5.4

Apple: NEVPNManager, organisation account only

Guideline 5.4 (verbatim in the research): “Apps offering VPN services must utilize the NEVPNManager API and may only be offered by developers enrolled as an organization. You must make a clear declaration of what user data will be collected and how it will be used on an app screen prior to any user action to purchase or otherwise use the service. Apps offering VPN services may not sell, use, or disclose to third parties any data for any purpose, and must commit to this in their privacy policy.” A VPN licence must be supplied in App Review Notes where a territory requires one.

  • Tunnel: NetworkExtension — NEPacketTunnelProvider + NEVPNManager in native Swift / Objective-C. No web page, WebView, or custom proxy can create the tunnel. Entitlement com.apple.developer.networking.networkextension (value e.g. packet-tunnel-provider) is self-serve in Xcode / Signing & Capabilities since Nov 2016 — only Hotspot Helper and the NE app-push provider still need a managed request. Source: newly.app — Network Extension entitlement guide (index, May 2026).
  • Organisation + D-U-N-S first: an individual account will be rejected. FlashPath VPN needs its Canadian legal entity enrolled as an organisation, a D-U-N-S number (free via Dun & Bradstreet; Apple says allow up to 5 business days for issue + up to 2 business days for Apple to receive it), a public website on the company domain, and a person who can bind the company. Start this on day one — it is commonly the slowest step.
  • Declaration before purchase/use: what data is collected and how it is used, on an app screen, before any purchase or use — separate from the privacy policy.
  • No sale / use / disclosure: the privacy policy must commit to not selling, using, or disclosing VPN data to third parties. Any SDK that receives data (e.g. crash logs, account email) must be declared and consistent with that commitment.
  • Privacy labels & manifest: privacy-policy link in App Store Connect and in-app; App Privacy “nutrition labels” for every data type collected by the app and third-party SDKs; PrivacyInfo.xcprivacy manifest mandatory for new/updated apps since 1 May 2024 (secondary, index).
  • Subscriptions — IAP only in-app: digital subscriptions sold in the app must use Apple In-App Purchase (StoreKit), provide ongoing value, disclose price / duration / auto-renewal, work across devices, and include Restore Purchases. Minimum subscription period is 7 days — the 7-day plan sits exactly at that minimum, so confirm its StoreKit configuration in App Store Connect. Do not sell access via licence keys, external links/buttons, or a website checkout inside the app. Apple Developer Program: $99/yr (secondary, index).
  • Review risk: Guideline 4.3 (Design: Spam) — similar-looking VPN clients are frequently rejected. One secondary report described a VPN client taking Jan–May 2026 and 4 attempts under 4.3 — treat as anecdote, not a rule, but budget review time. Provide a demo account and keep backend services live during review.

Sources: Apple Guidelines §5.4 (verified live); D-U-N-S / enrolment — thecodevolt.com, appranker.net (index, secondary); IAP §§3.1.1/3.1.2 summaries — github.com/truongduy2611/app-store-preflight-skills, developerguidelines.com (index).

ANDROID · GOOGLE PLAY — VPNSERVICE POLICY

Android: VpnService as core function + declaration

Official Play policy (verified live): “Only apps that use the VpnService and have VPN as their core functionality can create a secure device-level tunnel to a remote server.” The implementation is android.net.VpnService + BIND_VPN_SERVICE permission, with the system consent dialog. A browser or WebView alone cannot provide the tunnel.

  • Must do: document VpnService use in the Play listing; encrypt data from device to tunnel endpoint; abide by Developer Program Policies.
  • Prohibited: using VpnService to (a) collect personal/sensitive data without prominent disclosure and consent, or (b) redirect/manipulate other apps’ traffic for monetisation (e.g. redirecting ad traffic through another country).
  • Prominent disclosure + affirmative consent: inside the app itself (not only listing/website), in normal usage flow, describing data accessed/collected via VpnService and how it is used/shared, requiring a tap to accept / tick box, separate from other disclosures — not only in a privacy policy or terms. If no personal/sensitive data is collected via VpnService, the disclosure still must explain why VpnService is required and how it is used.
  • Play Console declaration: all VpnService apps must complete the declaration (subject to Google approval; undeclared/deceptive use can mean suspension/termination). It asks: is VPN the core functionality, what data is collected/shared (checklist), does the app redirect/manipulate other apps’ traffic for monetisation (“Yes” fails), plus two videos ≤90 seconds each — one showing the app opened and VPN used, one showing the prominent disclosure. Resubmit if use changes.
  • Data Safety + privacy policy: privacy policy linked from listing and in-app; the Data Safety form is mandatory to publish and must declare all data collected/shared by the app and third-party SDKs, plus deletion options. Google notes Data Safety is developer-provided, not an independent audit (secondary, index).
  • Android 14+: foreground-service declaration required; VPN foreground-service type handling (systemExempted for VPN) must be declared (secondary, index). The app must not update itself outside Play.
  • Payments: Play Billing required for in-app digital subscriptions; no steering via listing, promotions, webviews, buttons, links or ads to an outside payment method. Subscriptions must disclose cost, billing frequency, auto-renewal, trials, and provide easy online cancellation. Fee schedule is changing in 2026–27 by region — verify the current fee in Play Console before pricing (secondary).
  • Account type — open question: two secondary sources state Google requires an organisation account for VpnService apps (D-U-N-S, company phone/website; Google warns D-U-N-S can take up to 30 days). This was not verified on an official Google page in this research — confirm in Play Console during setup. Registration is a one-time $25 fee (secondary).

Sources: Google Play VpnService policy (verified live, crawled 2026-10-19, read 2026-11-16); billing summary — github.com/leehueeng/store-review-check (index); org-account claim — yourmahbub.com, appranker.net (index, secondary, not officially verified).

What this means for FlashPath VPN: account management, subscription, and the connection itself all need to work in the native iOS and Android apps built on the frameworks above — the app is the full product. This website at www.swiftnetworktech.com is the subscription entry point (web checkout, outside the apps) and the information display; it does not replace the app. “Log in on a web page and you are connected” is not a model either store permits on mobile. Both stores require their own billing for in-app subscriptions — a website-only checkout inside the app will be rejected, and the app must not steer users out to web payment. Comparison: Apple is stricter on entity (organisation-only is in the guideline text itself) and on data (absolute ban on selling/using/disclosing VPN data). Google is stricter on process (declaration + two videos + prominent-disclosure screen reviewers check).

Can the tunnel itself be serverless?

The option in your screenshot — serverless using AWS Lambda MicroVMs, pay-per-use, near-zero cost when disconnected, quoted at about $0.13/hour — was assessed for the VPN data plane, the part that actually carries customer traffic.

Verdict: No for the data plane — Yes for the control plane

A serverless data plane does not work for a VPN. Lambda blocks inbound connections, caps invocations at 15 minutes, is stateless, and has no static IP — WireGuard needs the opposite: a persistent process listening on UDP 51820 at a stable public IP. Cloud Run is likewise HTTP-only and cannot accept raw UDP WireGuard traffic. The viable MVP is a hybrid: serverless control plane + always-on data plane (see below).

About “$0.13/hour”: this figure could not be verified. AWS Lambda is not priced per hour — verified live on aws.amazon.com/lambda/pricing, it is $0.20 per 1M requests + $0.0000166667 per GB-second (x86, tier 1; free tier 1M requests + 400,000 GB-seconds/mo). $0.13/hr × 730 hr = $94.90/mo if run continuously — far above a Fargate node (~$36/mo), a Fly.io microVM (~$2–$7/mo), or a $5 VPS. Do not use $0.13/hr as a serverless VPN cost.

Structural limitEvidence
Inbound connections blockedAWS Lambda FAQ, quoted in secondary sources: “Inbound network connections are blocked by AWS Lambda, and for outbound connections only TCP/IP and UDP/IP sockets are supported.” A VPN server must listen for inbound clients; Lambda cannot listen on a socket at all. Source: repost.aws (index).
15-minute maximum executionLambda max timeout is 15 minutes (900 s) per invocation. A tunnel is a session of hours/days and would be killed mid-session, repeatedly. Chaining invocations does not fix this. Sources: Lambda explainers (index).
Stateless / no persistent stateEach invocation is independent, with no shared memory. Session keys, sequence state, and NAT mapping cannot live in Lambda.
No static IPLambda runs in AWS’s shared VPC with dynamically allocated temporary IPs that change on cold starts/scaling. A client config embeds a fixed Endpoint = <public_ip>:51820; a moving endpoint breaks every client until config is re-pushed. Source: tutorialpedia.org (index).
WireGuard needs a host listenerWireGuard runs over UDP 51820 by default, in the Linux kernel since 5.6, and needs a publicly routable endpoint, IP forwarding + NAT masquerade, and PersistentKeepalive — host-networking operations Lambda / Cloud Run do not expose. Source: greengeeks.com (index). OpenVPN has the same inbound-listener problem, with higher overhead.
Cold starts & Cloud RunCold starts of 100 ms to several seconds are fatal to a “wake on first packet” design — the first packet is the handshake. Cloud Run is HTTP/HTTPS/gRPC/WebSocket only on a single PORT; “you cannot route raw TCP/UDP traffic.” Sources: slashdot.org, systemsarchitect.io (index).

MicroVM note: Firecracker (the isolation technology behind Lambda) is an isolation technology, not a networking fix — it does not change any limit above.

Recommended split: what is serverless, what must stay always-on

Design rule from the research: the data path (client ↔ WireGuard node ↔ internet) must contain no Lambda, API Gateway, ALB, or Cloud Run hop. The control path (client ↔ HTTPS API ↔ database) must contain no WireGuard node. If a component appears in both paths, the split is wrong.

LayerBelongs onWhy
Data plane — MUST be always-onWireGuard nodes on small VPS / microVM per region — 1 per Phase 1 region: US West, US East, US Central, CanadaPersistent UDP listener, static public IP, kernel WireGuard, IP forwarding / NAT, long-lived sessions.
Control plane — CAN be serverlessLambda + API Gateway (or Cloud Run / Cloud Functions for HTTP APIs), managed DB (DynamoDB / Firestore / RDS Serverless / Supabase), object storage, Secrets Manager, queues / schedulerShort, bursty, event-driven: sign-up, login, subscription checks (verify Apple/Google receipts server-side), WireGuard key/config generation and distribution, node list / health API, payment webhooks, email. Scales to zero when idle; free tier covers MVP volumes.
Config distributionServerless API + signed, short-lived config delivery. Private key generated on-device where possible; public key registered server-side.Keeps keys/configs out of the app binary; lets you add / remove / rotate nodes without an app update. Traffic must never flow through Lambda.
Node health / monitoringServerless scheduler (EventBridge / Cloud Scheduler) + Lambda health-checker probing each node, writing status to DB; CloudWatch / managed alertingHealth checks are short periodic jobs — ideal Lambda work. The probing is serverless; the thing probed is always-on.
PaymentsStore billing in-app (StoreKit / Play Billing) + server-side receipt verification (Lambda); Stripe or equivalent only for web purchases outside the appsVerification is request/response; webhooks are events. Apps must not steer users to web payment (see store sections above).
Must NOT be serverlessTunnel endpoint, per-connection state, NAT, DNS resolver for tunnel clients (run DNS on/near the node or use a managed resolver reachable from the node)See structural limits above. Do not put client DNS through Lambda.

If an IP becomes unavailable, how fast can you switch?

Honest caveat: no source in this research measured VPN IP-block recovery time. All times below are engineering estimates derived from provisioning / redeploy mechanics — label them as estimates in any plan. Detection time (health-check failures, user reports) is usually longer than the technical switch and is not included.

What fast rotation always needs

  • Spare capacity pre-provisioned — a warm standby node (or pre-built image/snapshot + reserved IP) in the same region. Building from scratch after detection is the slow path.
  • A way to publish the new endpoint — control plane pushes an updated node list (API the app polls on connect / on failure, or push). Design the app to re-fetch the node list on tunnel failure, not only on launch. DNS TTL / poll interval dominates the tail.
  • Client reconnect — the WireGuard handshake itself is fast (sub-second in normal conditions, by design). User-visible outage = detect + activate spare + publish config + client re-fetch + reconnect.
  • Do not reuse the unavailable IP — destroying a VPS releases its IP (Vultr docs, index); a new instance gets a new IP from the provider pool. A same-region recreate does not guarantee a different /24 or a clean reputation — that is a risk, not a guarantee.

Planned approach for the MVP

  • One warm spare per Phase 1 region if budget allows — at minimum spares in US West + US East, the two highest-traffic regions. Keep spares running and load-sharing: Vultr / Linode / Lightsail still bill for stopped instances, so a stopped spare saves little.
  • Versioned node list with short TTL, delivered via the serverless control plane, so publishing a spare takes seconds.
  • Automate the switch (health-check → mark unhealthy → publish spare → alert) so it does not depend on a person at 3 a.m.
  • Test before launch (game-day: mark a node unhealthy, measure time-to-reconnect for a test client) and replace the estimates below with that measurement.
  • No switch time and no restoration of access to any specific service is guaranteed.
ModelCan it rotate the data-plane IP?Estimated switching time*Cost of readiness
Serverless (Lambda / Cloud Run)No — N/A. No data-plane IP exists to rotate. Serverless only publishes a new node list in seconds once a new node exists.Seconds for config publish; tunnel itself still needs another modelNear-zero idle
VPS (Vultr / Linode)Yes — fastest and cheapest at MVP scale. Publish a warm spare via control plane, or API destroy + create from snapshot/image for a new public IP. One secondary source reported a Vultr one-click WireGuard deploy in 47 seconds — deploy time only, not detection + propagation.Estimate Warm spare: ~seconds–2 min. Destroy/recreate: ~2–10 minSpares double node cost: e.g. 4 regions × $5 = $20/mo live + $20/mo spares = $40/mo estimated
ECS / FargateYes, but the IP does not rotate with the task. Clients see the Network Load Balancer’s Elastic IP(s) (static by design). Rotating the client-visible IP means a new EIP / new NLB + config publish. NLB supports UDP (platform 1.4+); container must also expose a health port. Whether kernel WireGuard (vs userspace wireguard-go) runs in a Fargate task was not verified — test first.Estimate Task redeploy (same NLB IP): ~1–3 min, but IP unchanged. Full rotation: ~5–15 min + NLB provisioning~$36/mo per node + load balancer per region + egress
Cloud RunNo — N/A for the data plane (HTTP-only). Redeploying a control-plane service (~1–2 min) changes no VPN IP.N/A$0 when idle (control plane only)
Fly.io MachinesYes, with caveats. New Machine + new dedicated IPv4 ($2/mo) → publish. Shared Anycast IPv4 is unsuitable for non-HTTP protocols; dedicated IPv4 required. UDP reported as inconsistent (STUN anecdote) — unverified for WireGuard; test before relying on it.Estimate ~2–5 min, if UDP works in that region~$2–$7/mo per Machine + $2/mo per dedicated IPv4
LightsailYes, like a VPS. New instance from snapshot/blueprint + attach a new static IP (free while attached; $0.005/hr if unattached >1 hr).Estimate Warm spare ~seconds–2 min; recreate ~2–10 min$5–$7/mo per node

* Estimates only — no benchmark source found. Sources: Vultr docs / API (index); Fargate NLB/UDP — aws-samples.github.io, proxylity.com (index); Fly.io DERP write-up — usefuli.sh (index).

Recommended MVP architecture — Phase 1 North America

One image, one control-plane codebase, one failure domain per region. This is the only shape in which every component does what its platform is designed for, and it can be operated by a small team.

Clients: iOS (Swift, NetworkExtension / NEPacketTunnelProvider, NEVPNManager) Android (Kotlin, android.net.VpnService, WireGuard userspace) │ HTTPS (control) UDP 51820 (data) ▼ ▼ Control plane (serverless): Data plane (always-on): API Gateway + Lambda (or Cloud Run) 4× WireGuard nodes, 1 per region: • sign-up / login (email + OTP) • US West — Vultr Seattle / LA / Silicon Valley • subscription status (verify Apple / • US East — Vultr New Jersey / Atlanta Google receipts server-side) • US Central — Vultr Chicago / Dallas • WireGuard key registration + • Canada — Vultr Toronto / Linode Toronto per-user config generation Each: 1 vCPU / 1 GB VPS, Ubuntu LTS, • node list / health API kernel WireGuard, UDP 51820 only inbound, • payment webhooks (StoreKit / Play IP forwarding + NAT, DNS resolver, Billing; Stripe web only) hardening, unattended upgrades DynamoDB (or equivalent) for users, + 1 warm spare per region if budget allows subscriptions, node inventory, keys (or 2 spares: US West + US East) Secrets Manager for WireGuard server keys EventBridge + Lambda health-checker CloudWatch / managed logging + alerts S3 + CloudFront (or equivalent) for www.swiftnetworktech.com, policy, support

Estimated monthly cost — MVP Phase 1

All totals are estimates (arithmetic on the cited per-unit prices). Verify against provider pricing pages at purchase time; regional surcharges apply in some cities. Excludes engineering time, legal/privacy counsel, review rework, support, taxes, and paid monitoring/analytics — do not present these totals as total cost of the business.

LineBasis (source)Estimated cost
4× WireGuard VPS (1 per region)Vultr $5/mo or Linode $5/mo, 1 vCPU / 1 GB / 1 TB transfer; DigitalOcean $6/mo. Sources: tuxai.dev, computerandmobile.com (index; prices verified June/Oct 2026 in those sources)$20/mo
Warm spares (optional, recommended)Same $5/mo × 2–4+$10–$20/mo
Serverless control planeLambda $0.20/1M req + $0.0000166667/GB-s, free tier 1M req + 400k GB-s (verified live, aws.amazon.com/lambda/pricing) — MVP volumes well inside/near free tier~$0–$5/mo estimated
Domain, DNS, TLS, storage, loggingMarket rates; not priced in sources — budget line~$2–$5/mo estimated
Apple Developer Program$99/yr (secondary, index)~$8.25/mo equivalent
Google Play registration$25 one-time (secondary)One-time
Total without spares—~$30–$40/mo estimated
Total with 2–4 spares—~$40–$60/mo estimated
Bandwidth overage riskEach $5 VPS includes 1 TB/mo; overage billed per GB (rate not verified in this research — check Vultr/Linode overage pages). At MVP volumes 1 TB/node is ample; at scale egress dominates.Variable; monitor per-node transfer
Payment feesApple/Google 15% on first $1M/yr (enrolled) / 30% above, per secondary sources — verify current schedule in App Store Connect / Play Console; Stripe web fees separate% of revenue

Low-cost path to many global locations

Your added question: can one low-cost design combine serverless / cloud servers and reach many global sites? Yes — the hybrid above is that design. Adding a region is a procurement step (spin up the same VPS image there), not a redesign. Comparison below uses only prices and coverage from the research; all totals are estimates.

OptionIdle cost / nodeStatic IP · UDP / WireGuardCoverage & notes
A. Small VPS per region (Vultr / Linode / DO)$5–$6/mo (1 vCPU/1 GB, 1 TB incl.) — idle = full priceYes, included · Native kernel WireGuard, UDP 51820Best breadth per dollar: Vultr 30+/32 locations, Linode/Akamai 25+/26, DO ~15. Covers Phase 1 + Tokyo/Singapore/Hong Kong when deferred regions are added. Sources: contabo.com, webhostingadvices.com (index). Highest ops burden — mitigated with one image + Terraform/Ansible.
B1. Fargate (ECS) + NLB~$36/mo per 1 vCPU/2 GiB task (730 hr × $0.04048 + $0.004445/GB-hr) + LB + egress; no scale-to-zeroYes, via NLB + Elastic IP (the LB’s IP, not the task’s) · Possible with caveats; kernel-module access not verifiedAWS regions ~30+. Worst always-on cost: ~7× a VPS per region before load balancers. Not recommended for MVP / global-MVP data plane.
B2. Cloud Run$0 when idle — but cannot run the data planeNo static IP · No — HTTP-onlyGCP regions ~40+; use only for the control plane.
B3. Fly.io Machines~$2.19/mo (shared-cpu-1x 256 MB, Ashburn) to $6.70/mo (1 GB) + $2/mo dedicated IPv4 + egress $0.02/GB NA/EUDedicated IPv4 $2/mo required for non-HTTP · Uncertain — UDP reported inconsistent; test WireGuard end-to-end first18 regions (Oct 2026 checks); 17 cities retired incl. Montreal, Hong Kong, Miami, Seattle — Hong Kong retirement hits the deferred Asia list; Toronto remains listed. Verify live region list. Source: aiignitions.com (index). Runner-up if UDP test passes.
B4. Lightsail$5/mo (512 MB) / $7/mo (1 GB), 1–2 TB incl.; billed even while stoppedYes, included (free while attached) · Native (full VM)18 regions per one source, but only 3 US regions (N. Virginia, Ohio, Oregon — no California) and Canada coverage not verified. Added Hong Kong / São Paulo / Spain June 2026 per AWS notes (secondary). Source: bestusavps.com (index).
C. Hybrid — RECOMMENDEDControl plane ~$0–$5/mo at MVP volumes; idle cost = data-plane costSame as data-plane choice (A or B3)Coverage = data-plane provider’s coverage. Best at scale: control plane stays pay-per-request; data plane scales by adding $5 nodes or upsizing hot regions only. No per-region load-balancer tax.
Scenario (data plane only, est.)VPS (A)Fargate (B1)Fly.io (B3)Lightsail (B4)Hybrid C (= A + control)
4 regions, idle / low traffic4 × $5 = $20/mo4 × $36 = $144/mo + 4× LB + egress4 × ($2.19–$6.70 + $2) = ~$17–$35/mo + egress4 × $5–$7 = $20–$28/mo~$20–$25/mo
20 regions, idle20 × $5–$6 = $100–$120/mo20 × $36 = $720/mo + 20× LB + egress20 × ~$4–$9 = ~$80–$180/mo + egress20 × $5–$7 = $100–$140/mo (if all 20 offered — not verified)~$100–$125/mo

Regional surcharges apply in some cities (e.g. Vultr São Paulo +50%, Linode São Paulo +40% / Jakarta +20% in Oct 2026, per rack.pocketplay.win, index). At scale the driver is egress, not compute: Fly.io egress $0.02/GB NA/EU = $20/mo per 1 TB per node; VPS nodes hit their 1 TB cap then bill overage / need upsizing. Sequencing after Phase 1: (1) prove the hybrid on 4 North-America nodes; (2) add Tokyo / Singapore / Hong Kong as VPS nodes on the same provider(s) — same image, same control plane; (3) only then evaluate a second data-plane provider for redundancy / IP diversity.

Risks, ranked

  • 1. Store rejection / delay (highest). Organisation + D-U-N-S lead time; 5.4 and VpnService declaration; 4.3 similarity; privacy-policy commitment. Mitigation: enrol + request D-U-N-S first; build disclosure/privacy/declaration assets before the app is finished.
  • 2. IP reputation / unavailability is a when, not an if. Mitigation is operational (warm spares, fast config push, monitoring), not a product promise. Never promise a specific site/service will work.
  • 3. Single-provider concentration. One provider outage / policy change hits every region. Mitigation: two providers from the start (e.g. Vultr for US, Linode for Canada), or a portable image (Terraform + cloud-init) so a region rebuilds elsewhere in minutes.
  • 4. Logging / privacy liability. Apple’s no-sell/use/disclose commitment + Canadian PIPEDA + the privacy policy must match actual logging (ideally: no traffic logs; only account/billing + aggregate node health). Counsel must review policy against implementation.
  • 5. Node security. Minimal surface (only UDP 51820 + key-only SSH from admin IP), unattended updates, per-node keys, key-rotation runbook.
  • 6. Abuse / provider terms. Comply with provider ToS and lawful-use terms. Jurisdiction questions require legal review — not settled by this research.
  • 7. Bandwidth cost at scale. The $5/node model breaks past 1 TB/node or with heavy streaming; add bigger / more nodes per hot region, not more regions.

Open questions — not verified in this research

  • The “$0.13/hour” serverless figure — could not be matched to any Lambda / Fargate / Cloud Run / Fly.io rate found.
  • Exact IP-switching times — no benchmark source; all times here are estimates. Replace with a measured game-day result before launch.
  • Fargate + WireGuard in practice — NLB/UDP documented, but kernel WireGuard throughput in a Fargate task not verified.
  • Fly.io WireGuard-over-UDP — reported inconsistent for STUN/DERP; no WireGuard-specific test found.
  • Lightsail Canada (Toronto) availability — not verified; check in the AWS console.
  • VPS egress overage rates and AWS egress rates — not verified; needed for an at-scale cost model.
  • Current Apple/Google fee schedules (15%/30% and 2026–27 regional changes) — secondary sources conflict; verify in App Store Connect / Play Console.
  • Legal: whether any Phase 1 storefront requires a VPN licence; PIPEDA / data-residency duties; provider ToS on VPN use. Requires counsel.
  • Prices are snapshots from sources dated June–Nov 2026 — re-check at purchase time.
  • Beyond Apple Guidelines, Google VpnService policy, and AWS Lambda Pricing (verified live), other facts rely on indexed secondary sources as flagged.

One planned plan, by duration only.

The planned model gives every customer the same plan and the same locations — whether you travel occasionally or live away from home for months — with duration as the only difference. You can subscribe here on the web or in the app (in-app via Apple / Google billing); both create the same account, and everything after subscribing — connecting, switching, checking and renewing your plan — can be done in the app. Prices are not yet published: each duration below is marked “to be confirmed,” and final CAD prices will be announced before sign-up opens. Nothing on this page is an offer to sell.

7 Days

7 days · planned single billing

Price: to be confirmed before launch

  • For a short trip or a first try
  • Planned to include Phase 1 locations
  • Full access in the app, plus web account
  • Location switching, per final launch terms
Read the FAQ

30 Days

30 days · planned single billing

Price: to be confirmed before launch

  • For a month of travel or remote work
  • Planned to include Phase 1 locations
  • Full access in the app, plus web account
  • Location switching, per final launch terms
Read the FAQ

12 Months

12 months · planned single billing

Price: to be confirmed before launch

  • For year-round use
  • Planned to include Phase 1 locations
  • Full access in the app, plus web account
  • Location switching, per final launch terms
Read the FAQ
The planned model has no tiers and no add-on locations. There is no separate “travel” plan and no separate plan by customer type planned. Where you subscribe does not change the plan: web checkout on this site and Apple / Google billing in the app both activate the same account, which you then manage in the app. Final plan terms — including locations, switching, renewal, and refunds — will be set out in the terms published at launch, which will govern over this page.

Questions

Straight answers, including the limits.

Will FlashPath VPN work with a specific website, app, or streaming service?

We can’t say in advance for any specific service. Websites and apps set their own rules about the connections they accept, and those rules change. FlashPath VPN provides an encrypted connection through a location you choose; whether a particular service accepts that connection is decided by that service.

How fast will it be?

Speed depends on your local network, your distance to the location you choose, and conditions on the wider internet at the time. Choosing a closer region generally helps. We don’t publish a guaranteed speed, because we can’t control those factors.

What information does FlashPath VPN keep?

FlashPath VPN is designed to minimise activity data: servers are designed to run in memory only and are not designed to store browsing activity. Account and billing information needed to run a subscription will be described in the Privacy Policy published before launch. Please read that policy before subscribing when it is available — it will be the controlling document, not this page.

Can I switch locations?

Yes — in the app. The planned single plan is designed to let you switch in the app between the locations available at the time, without coming back to this website. Availability of a specific location can change; the current list and the final switching terms will be shown in the app, in your account, and in the terms at launch.

Do I need to come back to this website after I subscribe?

No. The app is planned as the full product: sign in, choose and switch location, connect and disconnect, check your plan and expiry, renew, and manage your account can all be done in the app. This website is mainly the subscription entry point and the place for product information, plan details, policies, and app download links.

Can I subscribe in the app, or only on the web?

Both. Subscribing on this website uses web checkout, outside the apps. Subscribing inside the iOS or Android app uses Apple In-App Purchase or Google Play Billing, as those stores require — the app will not send you to the website to pay. Either route creates the same single FlashPath account; sign in in the app with that account to connect.

What happens if a location becomes unavailable?

The planned design keeps warm standby nodes and delivers the current node list through the serverless control plane, so a replacement can be offered without an app update. Research estimates (not measurements — no benchmark source was found) put a warm-spare switch at roughly seconds to 2 minutes for publish + client re-fetch/reconnect, and a destroy/recreate from snapshot at roughly 2–10 minutes, excluding detection time. It is not guaranteed: a replacement address may also be unavailable or not accepted by a particular network or service, and a same-region replacement does not guarantee a different network block or clean reputation. See the technical plan for the full assessment, including why the tunnel servers are not planned as serverless.

Which devices are supported?

The MVP is centred on the native FlashPath apps for iOS and Android — that is where you connect and manage everything. This website works in a browser for subscribing and reading product information, but it does not itself create a connection. The exact supported platforms and OS versions for launch will be listed here and in the app stores before purchase. The apps follow Apple and Google review and are announced only when available.

Who operates FlashPath VPN?

FlashPath VPN is a product operated by SWIFT NETWORK TECHNOLOGIES LTD., DBA FlashNet, a company formally registered in Canada, at www.swiftnetworktech.com. The MVP operates under that Canadian company.

What am I responsible for?

You are responsible for how you use your connection, including complying with the laws that apply to you and the terms of any website or service you use. FlashPath VPN provides the connection; how you use it is your decision.

Sign-up is not open yet

FlashPath VPN is in pre-launch. When sign-up opens, this website will be the subscription entry point — confirmed locations, prices, and terms published here, plus download links for the apps. After that, the app takes over: sign in, connect, switch, and manage your plan there. Please rely on the launch information, not on this preview page.