explaingit

nadoo/glider

Analysis updated 2026-07-03

3,669GoAudience · ops devopsComplexity · 3/5Setup · moderate

TLDR

glider is a forward proxy tool that routes your network traffic through remote servers. It supports many protocols including Shadowsocks and SOCKS5, protocol chaining, and automatic failover across multiple servers.

Mindmap

mindmap
  root((repo))
    What it does
      Forward proxy
      Protocol chaining
      Load balancing
    Protocols
      Shadowsocks
      SOCKS5 and HTTP
      VMess VLESS Trojan
    Features
      DNS server
      IPSet management
      DHCP server
    Audience
      Network operators
      Power users
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Route internet traffic through a remote Shadowsocks or SOCKS5 server to bypass network restrictions.

USE CASE 2

Balance connections across multiple proxy servers with automatic failover when one goes down.

USE CASE 3

Run a local DNS server that sends queries through your proxy to prevent DNS leaks.

USE CASE 4

Chain multiple proxy protocols so traffic passes through one server before reaching another.

What is it built with?

Go

How does it compare?

nadoo/glidergo-jet/jethoanhan101/algo
Stars3,6693,6693,669
LanguageGoGoGo
Setup difficultymoderatemoderateeasy
Complexity3/53/51/5
Audienceops devopsdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a remote proxy server already running one of the supported protocols such as Shadowsocks or SOCKS5.

In plain English

glider is a forward proxy tool written in Go. A forward proxy sits on your local machine and routes your outgoing network traffic through one or more remote servers. This is useful when you want to reach internet destinations through a different path, for example to bypass network restrictions or to route traffic through a trusted server in another location. The tool supports a large number of proxy protocols: HTTP, SOCKS5, Shadowsocks, Trojan, VLESS, VMess, SSH, and several transport layers including TLS, WebSocket, and KCP. You can chain protocols together, so traffic can go through one protocol to reach a server that speaks another. You can also set up multiple forwarding servers and have glider balance traffic across them using different strategies: round-robin, high availability (where it falls back to a working server if one fails), latency-based routing, or destination hashing. Along with the proxy features, glider includes a DNS server that can forward DNS queries through the proxy rather than resolving them directly. This prevents DNS leaks and allows custom rules that map specific domain names to specific forwarders. It supports DNS caching to reduce repeated lookups. On Linux, it can also manage IPSet, which is a kernel-level feature for grouping IP addresses, so that routing rules can be applied at the network level based on domain resolution results. There is also a simple DHCP server included that can run in failover mode, though this is described as a service component rather than the primary feature. Installation is available as a pre-built binary, via Docker, through package managers on Arch Linux and macOS, or by building from source with Go. Configuration can be passed as command-line flags or loaded from a config file. The README includes example configurations for common setups. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Show me a glider config file that forwards all traffic through a Shadowsocks server and automatically falls back to a SOCKS5 backup if the first fails.
Prompt 2
How do I configure glider to send DNS queries through a proxy and cache the results locally to reduce repeated lookups?
Prompt 3
Write a glider command that balances TCP connections across three Trojan servers using the latency-based routing strategy.
Prompt 4
How do I set up glider on Linux with IPSet rules so that domains matching a specific list always route through a dedicated forwarder?

Frequently asked questions

What is glider?

glider is a forward proxy tool that routes your network traffic through remote servers. It supports many protocols including Shadowsocks and SOCKS5, protocol chaining, and automatic failover across multiple servers.

What language is glider written in?

Mainly Go. The stack also includes Go.

How hard is glider to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is glider for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub nadoo on gitmyhub

Verify against the repo before relying on details.