Secure links for offices and teams

n9 vpn protocol

Managed VPN connectivity for companies, offices, remote teams, and private services.

managed clients operator panel nodes / gateways UDP / TCP / QUIC

Private connectivity for real work networks.

The protocol connects offices, contractors, remote teams, and internal services through controlled N9 gateways. The client uses the system VPN, n9tun, and n9core to keep corporate traffic on the right route.

  1. 01 Application
  2. 02 System VPN Network Extension / VpnService / Wintun
  3. 03 n9tun
  4. 04 n9core
  5. 05 UDP / TCP / QUIC
  6. 06 Internet

Transport policy stays under operator control.

A node can allow UDP, TCP, and QUIC separately for different networks and customers. The client can follow company policy or use a selected transport; UDP remains the default path.

UDP

Default packet lane

The default low-latency path for office traffic, remote access, and service-to-service flows, with n9way pacing and per-client data sessions.

TCP

Stream fallback

A reliable stream path for corporate networks where UDP is blocked, unstable, or shaped by the provider.

QUIC

Shared encrypted lane

An optional shared 9110 lane for networks that pass QUIC better than classic UDP traffic.

n9core keeps corporate routing predictable.

Operators get one clean N9 stack for clients, nodes, gateways, and panel: routing rules, MTU, transports, and recovery live in one model.

MTU

Server-synced MTU

Nodes send the tunnel MTU to the client, while operators can override MTU for a specific company, office, or client.

n9way

Clean packet mode

Diagnostics and code now use n9way naming for the packet tunnel path across the current stack.

Ports

Per-client data port

Every client still receives its own data session, even when a node serves many companies or offices through shared transport rules.

Rules

DNS-aware routing

DNS, provider rules, direct paths, and tunnel fallback remain visible so support can explain where corporate traffic goes.

Managed clients for company devices.

Windows and Android builds are published in GitHub releases. The Apple branch combines iOS and macOS through App Store/TestFlight. All platforms share the same managed client line.

Windows

Windows client

Desktop client for office PCs, admins, and remote staff with local profiles, n9core routing, and transport selection.

Download ZIP
Android

Android client

Mobile client for employees and field teams with encrypted N9 traffic and the current gateway rules.

Download APK
iOS / macOS

Apple client

Unified Apple branch for iPhone and Mac devices with the same profile model, transport selection, diagnostics, and corporate VPN stack.

App Store / TestFlight
Managed stack

Client, node, gateway, and panel in one line.

One N9 path for managed devices, office networks, private services, gateways, and the operator panel.

Privacy Policy

Clients store VPN profiles locally on your device. A profile contains the gateway address and profile token you provide. The clients use this information to request an N9 VPN Protocol session and create the system VPN route.

The clients do not sell personal data and do not include third-party advertising trackers. Network traffic passes through the N9 gateway selected in your profile. Server-side account, traffic, and session information may be processed by the gateway operator to provide the VPN service, enforce account limits, and diagnose connection issues.

For privacy questions, contact privacy@n9witch.com.

Support

For help with profiles, profile tokens, VPN permissions, downloads, App Store access, or connection stability, email support@n9witch.com.

When reporting a connection problem, include your device model, OS version, client version, selected transport, and whether the issue happened on Wi-Fi, Ethernet, or cellular.