burrow

Your own stealthy Telegram proxy.

burrow runs a Telegram MTProto proxy behind a real website with a real certificate, in hardened containers on a server you control. Telegram apps connect natively. Everyone else just finds a quiet personal blog.

Digby the mole, in aviator goggles, popping out of a burrow while a paper plane loops overhead
# on your server: one command does everything (Docker, firewall, tuning, TLS, watchdog, smoke test, QR code)
curl -fsSL https://raw.githubusercontent.com/deadboyccc/Burrow/main/install.sh |
  sudo BURROW_DOMAIN=notes.example.com BURROW_EMAIL=you@example.com bash

# no domain? paste as is: your IP becomes a free wildcard-DNS name, still a real certificate
IP=$(curl -fsS4 https://api.ipify.org) &&
  curl -fsSL https://raw.githubusercontent.com/deadboyccc/Burrow/main/install.sh |
  sudo BURROW_DOMAIN="${IP//./-}.sslip.io" BURROW_LINK_HOST="$IP" bash

# or try it on your own machine first: nothing exposed, fully self-tested
git clone https://github.com/deadboyccc/Burrow.git burrow && cd burrow && ./burrow try

Why burrow

Each piece was picked for safety, reliability and performance. Meet Digby: moles dig tunnels under walls, and this one wears flying goggles because your messages fly through.

🎭

Looks like a website

FakeTLS makes the handshake a TLS 1.3 hello to your own domain. Probes, scanners and browsers get a real site with a Let's Encrypt certificate.

🛡️

Hardened by default

Non-root, read-only, zero-capability containers. Images pinned by digest, dependencies by hash, secrets never in argv or logs, and no record of who connects.

🔗

Share with one link

A tg:// link and an offline QR code. burrow rotate revokes every link at once.

🩺

Self-healing

Restart policies, Docker live-restore and a watchdog that probes the proxy every five minutes and recreates it if it hangs.

⚡

Fast

mtg is a lean Go relay. BBR, fq and tuned buffers help on the lossy, long-distance links censored users live with.

🧪

Tested for real

275 automated tests, including live stacks that push real MTProto traffic to Telegram's data centres, and replay and probe attacks.

How it works

mtg owns port 443. A connection only reaches Telegram if its hello carries an HMAC made with your secret, has a fresh timestamp and has never been seen before. Everything else is spliced, byte for byte, to the decoy website.

📱 Telegram appor 🕵️ a censor's probe
→
mtg on :443FakeTLS gate: HMAC, timestamp, anti-replay, IP lists
→
☁️ Telegramvalid secret
🏡 Decoy siteeverything else (Caddy, real cert)

Get started

About 20 minutes from nothing to your phone using your own proxy. The deployment guide covers every step.

Rent a small server, point a domain at it

1 vCPU, 1 GB RAM, Debian or Ubuntu. Add an A record such as notes.example.com → your server's IP. No domain? Use 203-0-113-7.sslip.io (your IP with dashes).

Run one command on the server

curl -fsSL https://raw.githubusercontent.com/deadboyccc/Burrow/main/install.sh |
  sudo BURROW_DOMAIN=notes.example.com bash

Re-run it any time to upgrade; your secret is kept. Prefer your laptop? ./burrow deploy root@IP --domain … does the same over SSH.

Scan, connect, share

The installer ends by printing your links and a QR code. Later: /opt/burrow/burrow share shows them again, and /opt/burrow/burrow rotate revokes them all.