Placement
Install on Linux hosts you intend to protect. XDP acts on selected interfaces; it does not cover every route through a network.
Loading HoneyMesh...
Loading HoneyMesh...
For CTOs and network administrators
HoneyMesh adds selected Linux host ingress enforcement to existing controls. Review where it runs, who can authorize a rule, what the tests actually proved, and how a mistake is reversed.
Application, agent, kernel and optional Exchange boundaries
Privileges, local data, release integrity and recovery
A six-checkpoint TEST-first runbook with pass and stop criteria
Install on Linux hosts you intend to protect. XDP acts on selected interfaces; it does not cover every route through a network.
The tested 2.3.6-rc2 packaged service requires Linux kernel 5.8 or newer for its capability model. Validate distribution and architecture against the exact release you deploy.
The packaged service uses a dedicated honeymesh user and bounded capabilities. Mesh peers need individual certificates and explicit trust configuration.
Core Beta is available through an eligible paid plan. Distributed Pro sharing is outside the current pilot and requires separate qualification and opt-in.
Choose an allowlist, observe-first policy, ban review owner, rollback procedure, and support contact before enforcing on production interfaces.
Run this on systems you own or are authorized to test. Keep existing firewall, identity, and monitoring controls in place.
Choose representative Linux hosts and interfaces. Record the services, normal traffic, kernel, architecture, and existing network controls.
Install, configure traps and trust, and review events without enforcing bans. Confirm logs, certificates, and operator access.
Test configured detection with authorized traffic, then issue a manual ban. Confirm the protected interface, peer acceptance, and that an unbanned control source still reaches the same services.
Record detection accuracy, false positives, local and remote enforcement time, control-source reachability, service health, CPU/load, peer reconnect behavior, and time to release a mistaken ban.
The federation PoC covers the operator-ban path. An automatic-detection pilot must separately measure detection and false-positive behavior before making a production claim.
Three-node AMD64 manual-ban test, limits, and downloadable PDFs
Interactive browser simulation for operator workflow
Published package versions, checksums, manuals, and licensing files
Architecture, trust controls, sharing boundaries, and operating model
Current paid beta terms and the buyer path
Two response paths, prerequisites, procedure, and scorecard
Architecture boundaries, review questions, and fulfillment path
A company review should cover software version and support lifecycle, agent privileges, release integrity, vulnerability handling, data flows and retention, certificate and license management, incident reporting, EULA, privacy terms, support response, and cancellation. Request current documents and terms from Network Decode before relying on them as contractual commitments.
Infrastructure Pro is priced at $15 monthly per five-node block for noncritical local Core evaluation. Signed beta checkout is open for the stated noncritical host profile. Distributed Pro capabilities remain outside this pilot. Review the beta terms and verify the signed package before installation.
Ask for the security and procurement pack