Deception Mesh is an open-source Rust MVP that records activity against decoy HTTP and SSH services, then sends structured events to a central control plane for review, export, and notification. It is designed for observation and triage—not to block attacks or prove that a system is secure.
The project’s documentation describes a distributed sensor architecture and provides local Docker-based setup instructions. It also identifies security work that remains unfinished, so the project should not be treated as a fully hardened production platform. The details below reflect its public project page as accessed October 7, 2026; current release status may differ.
As an Amazon Associate I earn from qualifying purchases.
What Deception Mesh is for
Deception Mesh is presented as a defensive telemetry project: operators deploy decoy services, collect interactions with them, and use the resulting events to investigate or prioritize suspicious activity. The named decoys are HTTP and SSH. HTTP traps include routes such as /login, /admin, and /wp-login.php; the SSH honeypot is described as having no real shell. The project page does not establish that the system blocks attacks, measures a detection rate, or reduces incidents. Project documentation
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A secondary description frames the project as a compact way for developers and students to study deception telemetry, but that framing is not evidence of adoption or operational effectiveness. LavX News, July 9, 2026
#1 Best Overall
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
How the documented architecture works
The documented path runs from sensor agents to a central control plane, then to PostgreSQL and operator-facing outputs. Sensors host the decoys, capture details such as source IP, route, or attempted login, and report events. The control plane handles authentication and tenant access checks, persists events, and manages webhooks. PostgreSQL stores events, audit records, heartbeats, and sensor state. Project documentation
- Sensors: expose decoy HTTP and SSH services, report their status through heartbeats, and send captured activity.
- Control plane: validates authentication, applies tenant-based role access, processes events, and handles webhook delivery.
- Storage and outputs: PostgreSQL backs event and operational data; operators can query events, export CSV, and configure webhooks.
The listed technology stack includes Rust, Axum, Tokio, PostgreSQL, Docker, JWT, and role-based access control (RBAC). The project page also names an EventV1 schema, enrollment tokens, severity rules, repeated-activity handling, administrative audit records, and a webhook queue with retries and backoff. These are documented capabilities, not independently verified results. Project documentation
What severity rules and repeated activity mean
The project describes rule-based severity and handling for repeated activity, which can help organize events for triage. That is not the same as a validated detection engine: the published material supplies no detection-rate evaluation, incident-reduction result, or measured comparison against other tools. Treat the severity labels as the project’s prioritization mechanism, not as proof that an event is malicious or that an attack has been stopped.
Rank #2
- HARDWARE PLUS SECURITY SERVICES: FortiGate-60F Firewall Appliance bundled with 1 year of FortiCare Premium and FortiGuard Unified Threat Protection.
- UNIFIED THREAT PROTECTION (UTP): Secures against advanced online threats with comprehensive web filtering and anti-botnet technologies.
- OPTIMIZED FOR MEDIUM-SIZED BUSINESSES: Tailored for businesses needing robust security without the infrastructure of larger enterprises.
- RELIABLE CUSTOMER SUPPORT: FortiCare Premium ensures high-quality support and service continuity.
- EFFECTIVE PROTECTION: Employs advanced filtering technologies to safeguard against sophisticated threats.
How to try the documented MVP
The project page describes local scripts and Docker workflows, plus a separate outline for a VPS deployment. Its manual local demonstration proceeds through database and control-plane startup, health checks, and a demo script. Follow the current repository instructions before running anything; the public project page’s snapshot may not match later changes. Project documentation
Local quickstart scripts
The listed quickstart uses scripts/t29_install_mvp_local.sh and scripts/e2e_t29_quickstart.sh. These are the documented entry points; their exact behavior and prerequisites should be checked in the repository version you intend to run.
Manual Docker demonstration
- Use Docker Compose to start PostgreSQL and the control plane as described by the project.
- Check the control plane’s
/healthand/readyendpoints to confirm basic health and readiness. - Run
scripts/demo.shto exercise the demonstration workflow.
Suggested VPS sequence
For a VPS, the page outlines preparing production secrets, building images, starting the control plane and database, creating an administrator and tenant, registering a sensor, and running a production smoke test. This is a deployment outline, not evidence that the resulting configuration is secure by default or suitable for every environment.
Rank #3
- 【Up to 1100 Mbps VPN Speed 】 Hardware-accelerated WireGuard and OpenVPN-DCO deliver up to 1100 Mbps VPN throughput, over 3× faster than Brume 2 for smooth remote access and file transfers.
- 【Three 2.5G Ports & Multi-WAN】Tri-port 2.5GbE design with flexible WAN LAN configuration supports multi-gigabit wired setups, dual-ISP Multi-WAN and failover to keep home and SOHO networks online.
- 【Stealth VPN Obfuscation】VPN obfuscation disguises VPN traffic as regular HTTPS, helping you evade blocking, bypass restrictive networks and maintain stable, private connections.
- 【DPI protection】Deep Packet Inspection with visual dashboards blocks adult/gambling/malicious sites, while SQM and QoS prioritize gaming, calls, and video when bandwidth is tight
- 【OpenWrt & USB 3.0 Expansion】OpenWrt with 1GB DDR4 and 8GB eMMC lets you install plugins and build VPN, ad-blocking or NAS, while USB 3.0 Type‑C connects high-speed storage or 4G/5G dongles
Security controls and unfinished hardening
The project page lists JWT for users and tenant RBAC, hashed sensor and enrollment tokens, Argon2 password verification, strict EventV1 validation, and webhook delivery history and retries as implemented controls. These descriptions do not amount to an independent security audit. The reviewed materials report no penetration-test result, deployment benchmark, or operational reliability measurement. Project documentation
The same page identifies important unfinished work: sensor mutual TLS (mTLS), automatic per-tenant data retention, formal token rotation, and a /metrics endpoint. It says local or development mode accepts HTTP and that production should use real HTTPS. The project itself cautions against describing the MVP as fully hardened for production. Project documentation
Accordingly, treat the MVP as a project to inspect or test in a controlled environment unless you have independently assessed its code, deployment, secrets, network exposure, and data-handling requirements. Decoy events can include source IPs and attempted credentials or routes, so consider access control and retention before collecting them.
Who may find it useful—and what it does not establish
The documented design may interest developers and students examining a Rust-based telemetry pipeline, as well as defenders who want to explore decoy-triggered event collection. The available material supports describing it as an observability and alerting project, not a comprehensive security platform. It does not establish effectiveness at detecting real attacks, suitability for a particular compliance regime, or readiness for unattended production use.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
