CALL / MEETINGS
Preserve RTT, jitter and loss headroom under load. Reserve upload and ACK capacity, keep established flows on a stable path and defer background bulk.
LATENCY FIRSTNATIVE C23 / macOS DESKTOP AVAILABLE / WINDOWS & LINUX CLI AVAILABLE
LaneVertex is being built to keep meetings responsive and accelerate downloads and uploads across laptop Wi-Fi and one or more USB-tethered phones. Local flow policy. Server-compatible parallel transfers. One C23 core.
macOS Desktop available · Windows / Linux command-line builds available
Three priorities shape the multi-link architecture. CALL protects interactive traffic; bulk work uses the capacity that remains.
Preserve RTT, jitter and loss headroom under load. Reserve upload and ACK capacity, keep established flows on a stable path and defer background bulk.
LATENCY FIRSTUse eligible links for separate downloads and server-supported HTTP ranges. Resume with content identity and integrity checks.
DOWNLOAD CAPACITYRun independent upload jobs across links, or use multipart and resumable protocols supported by the destination. Track sent and server-confirmed bytes separately.
UPLOAD CAPACITYThe architecture combines local flow distribution with application-owned transfer engines. Each mechanism respects its destination protocol and platform capabilities.
Assign eligible separate flows to Wi-Fi, USB tethering or Ethernet. Keep source and path affinity; connect directly to ordinary destinations.
Parallel ranges with origin support, content identity, integrity checks and resumable state. Received, verified and committed bytes remain distinct.
Independent jobs and destination-supported multipart or resumable uploads. Explicit part identity, finalization and abort; sent is not server-confirmed.
Torrent files, magnets and seeding belong to the engine roadmap: verified pieces, bounded peers, resumable storage and shared link policy.
One native interface and one headless frontend share the controller, job store, configuration and immutable metrics. No duplicate transfer engines.
Separate download and upload rates for every usable link. Sum only the same direction, interval and byte category; keep overhead and verification explicit. Mbit/s · MB/s.
Cellular opt-in · Per-link and global budgets · Modules start on demand
Multiple phones require distinct usable tether interfaces and operating-system support. Shared carrier or upstream bottlenecks can limit gains. Separate flows and supported transfer protocols provide parallelism; arbitrary single TCP connections are not combined.
LaneVertex is independently developed by one person around explicit control of memory, work and data ownership. These engineering choices target lean startup and predictable behavior under large transfers; product-wide performance comparisons remain ahead.
LaneVertex is in active development. Public releases are available (macOS 1.0.6; Linux and Windows 1.0.6); end-to-end product and platform qualification continues.
| Component | Status | Scope |
|---|---|---|
| Native C23 core + control | AVAILABLE | The shared core for GUI and CLI ships in version 1.0.6 on macOS and 1.0.6 on Linux and Windows; policy and accounting features keep being extended. |
| Local multi-link operation | IN QUALIFICATION | Provider activation, traffic coverage and device compatibility depend on the operating system. |
| Transfer engines | PARTLY AVAILABLE | Single-connection HTTP(S) downloads ship in the public releases. Multi-link downloads, multipart uploads and torrent/magnet/seeding are not yet verified for public releases. |
| Linux / Windows / macOS | AVAILABLE | macOS: desktop app 1.0.6, Developer ID signed and notarized by Apple; routed bridge interfaces now count as links. Linux and Windows: command-line builds 1.0.6, now with a desktop GUI preview on Linux (X11) and Windows — settings, start at login, starting downloads and uploads, Diagnose, a signed update install (Linux pkexec/apt, Windows msiexec), a Traffic tab with a saved blocklist (shown only, not enforced) and Wi-Fi scan/join (Linux nmcli, Windows Native Wifi, tested only with mocks) are wired; Windows network adapter monitoring is tested only under wine. Traffic-blocking enforcement, native Wayland (XWayland only), HiDPI, enterprise 802.1X Wi-Fi, and any real Windows 10/11, Windows-on-ARM or Linux desktop hardware run remain open. Native desktop apps for Linux and Windows remain in development. |
Meeting protection and multi-link gains remain validation targets, with no universal failover or speed guarantee.
Evidence scope: 30 October 2026The planned headless frontend and native GUI operate on the same jobs, policies and byte accounting. Scriptable control without a second engine.
Desktop & CLI guidelanevertex interfaces list --format json
lanevertex jobs list --format json
lanevertex events --format ndjson