Quick start

Deploy a node and find your local proxy ports.

Install the desktop app, add a provider, create a VPS node, then use the Mixed, HTTP, or SOCKS endpoint locally.

Install a preview build

Download a build for your platform and verify the checksum before launching it.

Add cloud credentials

Use a test API key scoped to instance and firewall management.

Create a node

Pick a supported region and plan. Larger plans can receive the full protocol stack.

Review protocol details

Inspect SS, Hysteria2, VLESS-Reality, and Trojan ports and links.

Use local ports

The overview page shows Mixed, HTTP, and SOCKS ports directly.

Import elsewhere

Copy protocol links into sing-box, Clash, v2rayN, Hiddify, or another client.

Local endpoint formats

These are the formats exposed by the desktop overview port panel.

Mixed

Copy as host and port.

127.0.0.1:7890

HTTP

Use for apps that expect an HTTP proxy URL.

http://127.0.0.1:7891

SOCKS

Use for tools that accept SOCKS5 endpoints.

socks5://127.0.0.1:7892

Provider credential guidance

Use a dedicated test token for evaluation. Avoid all-purpose personal tokens.

Vultr

Use a key that can create instances, manage firewall rules, read metadata, and delete test nodes.

DigitalOcean

Use a token that can create droplets and SSH keys. Recovery uses a managed SSH key.

SSH host

Use hosts you own or are authorized to manage. Deployment needs service and firewall privileges.

Common failures

Most preview issues fall into one of these buckets.

Provider rejected the request

Check token scope, account balance, region availability, and quota.

SSH never became ready

Wait for cloud-init, confirm firewall access, and verify SSH support.

Local port cannot connect

Confirm the kernel, proxy/TUN state, and node links are healthy.

Deeper project documentation

The repository contains architecture, API, multi-cloud, and release-gate documents.