Robeing Accelerator Documentation

Robeing Accelerator is a zero-trust network access (ZTNA) platform with hardware-grade TCP acceleration built directly into the client kernel. Unlike traditional VPNs that add latency, Robeing is architected to reduce it.

Quickstart

Get connected in under two minutes:

# Linux
sudo dpkg -i RobeingAccelerator-Linux-0.9.4-beta.deb
robeing auth login --token YOUR_BETA_TOKEN
robeing up

# macOS (after mounting DMG)
robeing auth login --token YOUR_BETA_TOKEN
robeing up

Authentication

During beta, authentication uses personal invite tokens. After GA, full SSO via SAML 2.0 and OIDC will be available.

robeing auth login --token RBNG-XXXX-XXXX-XXXX
# Token is stored in ~/.config/robeing/credentials.json
# Refresh happens automatically every 24 hours

Zero-Trust Model

Robeing implements ZTNA: every connection is verified regardless of network location. The trust model is built on three pillars:

• Device identity — each device gets a short-lived X.509 certificate, rotated every 24h.
• User identity — JWT-based bearer tokens scoped to specific resources.
• Continuous verification — the Robeing daemon re-validates identity on every new TCP session, not just at connection time.

TCP BruTA Acceleration Kernel

BruTA (Brutal TCP Accelerator) is a congestion-control algorithm designed for lossy and high-latency links. Instead of backing off exponentially on packet loss (like CUBIC or BBR), BruTA maintains a fixed transmission rate while aggressively retransmitting.

BruTA parameters

APPEX TCP Engine

APPEX (Application Acceleration) dynamically adjusts TCP window size, buffer allocation, and ACK pacing based on measured RTT and bandwidth-delay product (BDP). It's most effective on high-throughput, high-latency paths ("long fat networks").

APPEX operates at the socket level and requires no kernel modules. It hooks into the system's TCP stack via setsockopt calls on supported platforms (Linux 5.10+, Windows 10+, macOS 12+).

TCP FastOpen Mode

This is the feature that differentiates Robeing's connection latency from every other ZTNA product on the market.

Standard TCP requires a full three-way handshake before application data can be exchanged:

Standard TCP:
Client → SYN             → Server
Client ← SYN-ACK         ← Server
Client → ACK + HTTP_REQ  → Server   # 1 RTT wasted
Client ← HTTP_RESPONSE   ← Server

Robeing FastOpen:
Client → SYN + HTTP_REQ  → Server   # data sent immediately
Client ← SYN-ACK + DATA  ← Server   # response on first ACK

The Robeing client constructs the initial TCP segment to carry the encrypted HTTP request payload alongside the SYN flag. The server-side Robeing relay accepts this and responds with data in the SYN-ACK. This is semantically equivalent to TCP_FASTOPEN but does not require the kernel option to be set on either endpoint.

Config File

Default config path: ~/.config/robeing/config.toml

# ~/.config/robeing/config.toml

[core]
server   = "us-east.relay.robeing.com"
port     = 443
protocol = "tcp"   # or "udp"

[acceleration]
fastopen        = true
bruta_enabled   = "auto"
appex_enabled   = true
bruta_rate_mbps = 0   # 0 = auto-detect

[routing]
mode        = "split"   # "split" or "full"
include_dns = true

CLI Reference

robeing up

Connect to the Robeing network using the stored credentials and config.

robeing up [--daemon] [--config PATH] [--region REGION]

robeing auth

robeing auth login --token TOKEN
robeing auth logout
robeing auth status

robeing status

robeing status

# Example output:
● Connected — us-east.relay.robeing.com
  User:       [email protected]
  Device:     macbook-m3 (cert exp: 18h)
  Latency:    14ms
  Mode:       split-tunnel
  FastOpen:   enabled
  BruTA:      standby (loss 0.0%)
  APPEX:      active (BDP: 1.4 MB)