Newt

Newt is a local WireGuard tunnel client and TCP/UDP proxy that provides zero-trust remote access to home lab services through Pangolin.

  • Network Services
  • Security
  • Tools & Utilities
Newt is a local WireGuard tunnel client and TCP/UDP proxy that provides zero-trust remote access to home lab services through Pangolin. It exposes private resources without port forwarding or public exposure. For new deployments, use the Pangolin CLI instead of this template.

Platform availability

Available on 5 of 10 platforms

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 25 days ago
Popular
59919 GitHub stars
Easy to install
755 install platforms, install notes, Docker image
Light to run
No data
Security check
70no serious findings, 5 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
919
Open issues
34
Last commit
2026-10-27
Latest release
1.19.0
License
AGPL-3.0
Activity
declining

Checked 22 days ago - source: GitHub (fosrl/newt)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in endpoint, ID, and secret before starting Set --endpoint, --id, and --secret (or use a config file) so Newt knows which server to connect to and can prove your identity. If any are wrong, Newt can’t start a tunnel. source
  • Keep your config file private and in place If you start Newt with --config-file (for example /etc/newt/config.json), make sure the file exists, is readable by Newt, and stays protected because it may contain your secret key. Missing or too-loose permissions can block startup or leak access. source
  • Add mTLS certificate files if you use them If your setup uses mTLS (two-way client and server certificate checking), provide the client certificate, client key, and CA file (the trusted root certificate) paths, and make sure those files exist and aren’t blocked by permissions. Without all three, Newt can’t complete the secure connection. source
  • Phased-out notice Use the Pangolin CLI and 'pangolin site up' for new deployments instead of Newt. source

Fetched 37 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should I use the Newt template for a new deployment?

For new deployments, the recommendation is to use the Pangolin Site template with the Pangolin CLI rather than the Newt template. Newt acts as the tunneled gateway to your local network.

What must I configure before Newt can start a tunnel?

Provide the server endpoint, connector ID, and secret using flags or a config file. If any of those values are missing or wrong, Newt cannot start the tunnel.

Can Newt expose local services behind CGNAT without opening router ports?

Yes. Self-hosting Pangolin with Newt can expose home services over the internet without opening router ports or publishing your home IP. It also avoids CGNAT limitations.

How do remote users authenticate for access?

Users connect with their existing identity. Pangolin enforces identity- and context-aware rules for zero-trust access to specific applications.

Answers sourced from fossengineer.com, github.com, github.com, pangolin.net

Community

Collected 53 days ago - public community threads