RouteGate v0.1.0

RouteGate v0.1.0

RouteGate v0.1.0 is the first public MVP release of RouteGate: an open-source, self-hosted Linux VPN Management Platform.

This release closes the initial MVP milestone with a production-like Clean VPS path validated end to end on Ubuntu 24.04 LTS.

What is included

The supported v0.1.0 workflow is:

Clean VPS
→ RouteGate installer
→ PostgreSQL + Manager + Admin UI + nginx/HTTPS + local Agent
→ secure /setup activation
→ Guided Workflow
→ install sing-box through RouteGate
→ configure VLESS / Reality
→ create the first VPN account
→ Config Deploy
→ persistent client profile / QR / VLESS link
→ working VPN connection

RouteGate manages the infrastructure lifecycle through the product model:

RouteGate Manager → RouteGate Agent → VPN Core

Highlights

• Clean VPS Installer for the supported single-node Ubuntu deployment.
• Native systemd services for Manager and Agent.
• PostgreSQL persistence and migrations.
• nginx + Let's Encrypt HTTPS as the public management endpoint.
• Secure first access through a high-entropy, single-use /setup activation link.
• Automatic local All-in-One Server and Agent registration during installation.
• Guided Workflow / Next Action First onboarding driven by real system state.
• Allow-listed sing-box installation and service lifecycle through RouteGate Agent.
• VLESS / Reality server configuration with a recommended All-in-One setup.
• VPN accounts and persistent client profiles.
• QR code and VLESS link delivery for third-party clients.
• Config Deploy lifecycle: render, validate, apply, start/restart, health check, and rollback foundations.
• Routing Profiles / Split Tunnel foundations with Direct, VPN, and Block actions.
• Traffic usage and limits foundations.
• User Portal foundations and access hardening.
• Version, schema, and Agent compatibility reporting.
• English-first UI with Russian localization.

Supported installation

The live-validated v0.1.0 installation target is:

Ubuntu 24.04 LTS
amd64
single VPS
native systemd deployment

Before installation, point a DNS A record at the VPS and make TCP 80/443 reachable.

Install the latest published RouteGate release:

curl -fsSL https://raw.githubusercontent.com/ikaevus/RouteGate/main/install.sh \
  | sudo bash

Pin v0.1.0 explicitly:

curl -fsSL https://raw.githubusercontent.com/ikaevus/RouteGate/main/install.sh \
  | sudo bash -s -- \
      --domain vpn.example.com \
      --email owner@example.com \
      --version v0.1.0

See docs/deployment/clean-vps-installer.md for the full installation contract and recovery behavior.

All-in-One network layout

The recommended first-run layout keeps the management and VPN listeners separate:

RouteGate HTTPS / nginx    TCP 443
VLESS / Reality            TCP 8443

The recommended VLESS / Reality setup uses TCP, xtls-rprx-vision, a newly generated Reality keypair, a random Short ID, and the server hostname as the initial Reality server name/handshake target.

Important lifecycle behavior

The Clean VPS Installer installs the RouteGate management platform, not the VPN Core.

After first administrator activation, RouteGate guides the administrator to install sing-box as an explicit allow-listed action. A newly installed sing-box may remain inactive and unconfigured. That is expected: installed and running with a valid RouteGate configuration are separate states.

The first successful Config Deploy owns the first real sing-box startup after RouteGate has rendered and validated a complete configuration.

Validation

The final production-like Clean VPS acceptance passed on us.routegate.org.

Validated end-to-end behavior included:

• clean Ubuntu 24.04 LTS installation;
• secure /setup activation;
• automatic local Agent registration;
• Guided Workflow;
• sing-box installation through RouteGate;
• VLESS / Reality configuration;
• first VPN account;
• Config Deploy;
• persistent client profile / QR / VLESS link;
• real client connectivity;
• full host reboot;
• automatic service recovery;
• VPN connectivity after reboot.

Validated third-party clients:

• V2Box
• V2RayTun

The final accepted persistent client profile used fingerprint=firefox for the working Reality path.

Release artifacts

The GitHub Release publishes:

routegate-v0.1.0-linux-amd64.tar.gz
routegate-v0.1.0-linux-arm64.tar.gz
SHA256SUMS

The release workflow verifies the checksums and required bundle structure before publication.

The arm64 bundle establishes the multi-architecture packaging contract, but Ubuntu 24.04 LTS amd64 is the v0.1.0 live Clean VPS support boundary.

Security notes

The supported installer path includes these release boundaries:

• downloaded release bundles require SHA-256 verification;
• unsafe archive paths and links are rejected;
• Manager listens on loopback behind nginx/HTTPS;
• PostgreSQL is local-only;
• the installer avoids silently overwriting unrelated active host services;
• the first-access token is high entropy, time-limited, and single-use;
• bootstrap administrator environment values are removed after initialization;
• Agent infrastructure mutations use explicit allow-listed operations rather than an arbitrary remote shell API.

Security vulnerabilities should be reported through the process described in SECURITY.md, not public issues.

Known boundaries / Post-MVP

v0.1.0 intentionally does not include:

• RG-101C compatibility auto-tuning and advanced client-profile controls;
• additional VPN protocols or VPN Cores;
• appliance image work;
• Kubernetes or HA;
• managed/automatic RouteGate updates;
• official RouteGate mobile clients.

These are not release blockers for the supported MVP contract.

Source and license

RouteGate is licensed under AGPLv3-or-later.

The RouteGate name, logo, and official-build designation are governed separately from the software license; see TRADEMARKS.md and NOTICE.

Open code. Protected brand. Trusted official builds.