[ MESH ]
Warning
Please be aware this project is currently in public alpha. We take security seriously, and we recommend not using this in production till we have conducted a full penetration-test. This is scheduled at the start of 2026. Features and APIs may change. Please report issues on GitHub.
MESH is a censorship-resisting, peer-to-peer first, end-to-end encrypted overlay network for digital forensics. It's a fork of the Tailscale protocol, but is self-hostable and heavily modified for civil society and forensic operations.
It adds hardened transport and obfuscation options such as AmneziaWG for hostile or censored networks, and falls back to encrypted HTTPS relays when UDP is blocked. This offers protection against the GFW and detection by Deep Packet Inspection (DPI) systems.
It can create and tear down end-to-end mesh links between a locked-down analyst host and forensic clients (for example, Android devices) in seconds by removing hub-and-spoke topologies. MESH lets you spin up a forensics mesh, collect data, tear it down, and start again without complex configuration. This is remote forensic and network capture without a hub-and-spoke design.
Key functions
- Builds peer-to-peer subnets for device analysis.
- Provides end-to-end encryption via WireGuard/AmneziaWG and distributes keys automatically.
- Creates a virtual TUN interface and assigns CGNAT-range addresses for use with ADB-over-Wifi & Libimobile.
- Advertises LAN routes or exit nodes for network monitoring and PCAP.
- Intergrates directly with AndroidQF for spyware IOC checks with MVT
- Transfers forensic artifacts such as ADB bug reports and
dumpsysoutput. - Runs a self-hostable control plane to create and manage meshes between analysts, enforce ACLs, and block compromised nodes on connection.
- Supports kill-switch capabilities to block a device’s other network traffic while the forensics link remains active.
- Supports ephemeral deployment and teardown on disconnect.
- Enables rapid creation, isolation, and teardown of remote investigation nodes.
Mesh networking, made for remote mobile forensics
-
MESH networking
Discover why using a MESH network is a powerful way to build secure ephemeral remote forensic networks for threat analysis and forensics
-
Architecture
Learn about the three core components that power MESH
-
Use cases
See how MESH helps investigators in real-world scenarios
-
Platform support
Check which platforms are supported and what's coming next
Quick start
Ready to get started? Follow our step-by-step guide:
-
Getting started guide
Complete setup guide from zero to your first forensic collection
Or jump directly to a specific component:
- Set up the control plane - Deploy your self-hosted coordination server
- Install the analyst client - Set up your Linux/macOS forensic workstation
- Deploy the endpoint client - Install the MESH app on target devices
- Verify your setup - Test connectivity and run your first collection
Learn more
Documentation
- Architecture - Deep dive into how MESH works under the hood
- User guide - Learn forensic workflows and best practices
- AmneziaWG configuration - Configure censorship resistance
- CLI reference - Complete command-line documentation
- Troubleshooting - Common issues and solutions
About the project
- About BARGHEST - Learn about the team behind MESH
- Platform support - Current and planned platform support
- Get help - Community, support, and contributing