Loading HoneyMesh...
Loading HoneyMesh...
Administrator setup · free SDK and paid host pilots
Install Node Guard Free now, or review the paid host setup path while replacement customer packages complete validation. These instructions are for noncritical evaluation.
Paid host package replacement is in progress. New checkout and affected downloads are temporarily closed. The commands below describe setup for an already installed agent. Do not install an older paid host package while replacement packages are being signed and tested.
Node Guard Free needs Node.js 20 or newer, one persistent application process, and a trusted source for the real client IP. Node Pro and Infrastructure Core need a noncritical Ubuntu 24.04 AMD64 host; the tested Core path uses generic XDP. Node Pro needs a dedicated Linux user for each protected app.
Node Guard Free needs no checkout. New paid host checkout is temporarily closed. When it reopens, one paid block will cover up to five Linux hosts; two cover ten. Each host uses one slot regardless of CPU or worker count and receives a separate signed JSON license. Orders above nine licenses arrive as a ZIP. Review current pricing and availability.
Customer host downloads are closed. The steps below apply to existing paid customers after a replacement package is released; do not install the withdrawn package.
After the invoice is paid, search your checkout inbox and spam folder for the HoneyMesh license email. Save the JSON attachments in a private folder. For an order above nine hosts, extract the attached ZIP into that folder; assign a different JSON license file to each host. If the email does not arrive, contact Admin@Network-Decode.com with your Stripe invoice number. Never email app secrets or passwords.
When replacement packages are available, Node Pro buyers use Node Pro access and Infrastructure Core buyers use Core Beta access. Verify the same billing email used at checkout before downloading the plan on your receipt.
ls -lh ~/Downloads/HoneyMesh-Node-*.tar.gz ~/Downloads/honeymesh_*.deb 2>/dev/nullIf installation is on a separate VPS, copy the package and its matching emailed JSON license there over SSH. Replace FILE, LICENSE.json, USER, and HOST with the real filenames and hosting-provider login details. Keep the license out of any public web directory.
scp ~/Downloads/FILE USER@HOST:~/scp ~/Downloads/LICENSE.json USER@HOST:~/The replacement packages are still in validation. The previous publisher fingerprint and package hashes belong to withdrawn releases. Wait for the final plan-specific download page to show the new archive hash, signature, and publisher fingerprint before installing. Stop if any value differs from that release.
cd ~/Downloads # or the folder containing the package
sha256sum FILECustomer archives include CUSTOMER_INSTALL.md, a signed manifest, public key, and package checksums. Use only the instructions and hashes that accompany the replacement release.
For an already installed paid host agent
https://127.0.0.1:8443 on that host and paste the token into the Enter Admin Token prompt. If the browser was already open with an empty or wrong token, refresh the page to get the prompt again.sudo systemctl status honeymesh.service --no-pager
curl --cacert /etc/honeymesh/certs/ca/ca.crt https://127.0.0.1:8443/api/health
sudo jq -r '.admin_token' /var/lib/honeymesh/runtime-state.jsonThe root configuration at /etc/honeymesh/honeymesh.json can have an empty admin_token; the agent generates and saves the active token in /var/lib/honeymesh/runtime-state.json. The SOC admin token, your emailed paid license, and the Firewall console login are separate credentials. If the command prints nothing, contact support before changing either file.
For a remote VPS, keep the SOC bound to loopback and use ssh -L 8443:127.0.0.1:8443 USER@HOST from your laptop. Confirm the local CA before trusting the browser certificate. Seeing interfaces and events confirms the console can read the agent; it does not by itself prove ENFORCE or a paid entitlement. Review the interface, TEST mode, and rollback path before changing mode.
Path A · application only
Install the free SDK in the Node.js app you want to protect. It needs no account, license, root access, or HoneyMesh agent and does not attach XDP.
cd /path/to/your-app
node --version
npm install @network-decode/node-guard@0.2.0-alpha.11
npx nodeguard init
npx nodeguard doctor nodeguard.policy.json
npx nodeguard policy validate nodeguard.policy.jsoninit creates an OBSERVE policy and refuses to overwrite an existing file. Check your lockfile for the exact package version and npm integrity hash.
Replace /path/to/your-app with your application directory. Follow the developer setup for Express or the Next Route Handler guide. Your application must verify the source and explicitly record a security event; the SDK does not classify every request automatically.
cp node_modules/@network-decode/node-guard/examples/auth-observations.json ./observations.json
npx nodeguard policy test nodeguard.policy.json observations.json --at 2026-11-03T18:00:00ZThe included synthetic events should produce an OBSERVE decision without blocking. The example file is in the installed npm package. This simulation does not prove your real application has recorded an event.
Use createPolicyGuardV1 with the generated policy. Keep mode: "OBSERVE" during normal traffic review. Do not take client identity from a raw forwarding header or request body.
Run normal requests and one controlled known-bad event from a source you control. Check decisions in your app logs. Exclude operator and monitor addresses before considering ENFORCE, which limits requests in the application. Roll back by returning to OBSERVE or redeploying your prior app build. Process-local limits clear on restart. Multiple workers do not share counters in this alpha.
Path B · Linux host and app
Use a noncritical Ubuntu 24.04 AMD64 host with a separate VPS console. Start with the agent in TEST and no public XDP attachment. Install the Node Pro package for the multi-app bridge; the Core package alone does not provide it.
The previous signed Node Pro package is withdrawn. Wait for the replacement package and its matching signed manifest before installing. The package verification commands will be updated to the exact new release.
Confirm TEST mode, disabled sharing, and no public XDP attachment in the local dashboard. Back up any prior config and state.
Find your dedicated app user's numeric UID with id APP_USER. Replace APP_USER, APP_UID, and customer_api_01 below. The app ID must be 8–128 letters, numbers, underscores, or hyphens. The provisioner creates private files but does not install or activate them.
id APP_USER
sudo python3 provision-node-pro.py --app-id customer_api_01 --app-uid APP_UID --output /root/node-pro-review
sudo cat /root/node-pro-review/node-edge-apps.jsonReview the UID, socket path, auto_block: false, and empty canary_ips. Follow the included CUSTOMER_INSTALL.md for protected file locations and group access. The agent and app need separate protected copies of the generated secret. Never paste a secret into a support ticket.
On a fresh Node Pro installation, replace YOUR_EMAILED_LICENSE.json with the file received by email and copy the generated files to their protected paths. If any destination already exists, stop and follow CUSTOMER_INSTALL.md to preserve the existing registration.
sudo install -d -o honeymesh -g honeymesh -m 0700 /etc/honeymesh/apps
sudo install -o honeymesh -g honeymesh -m 0600 /root/node-pro-review/agent-secret /etc/honeymesh/apps/customer_api_01.secret
sudo install -o honeymesh -g honeymesh -m 0600 /root/node-pro-review/node-edge-apps.json /etc/honeymesh/node-edge-apps.json
sudo install -o honeymesh -g honeymesh -m 0600 ~/YOUR_EMAILED_LICENSE.json /etc/honeymesh/node-pro-entitlement.json
sudoedit /root/node-pro-review/20-node-pro.confIn that drop-in, add Environment=HM_NODE_PRO_ENTITLEMENT_FILE=/etc/honeymesh/node-pro-entitlement.json and Environment=HM_NODE_PRO_UNIT_ID=YOUR_UNIT_ID, using the exact unit_id from your emailed JSON. Then install the drop-in:
sudo install -d -o root -g root -m 0755 /etc/systemd/system/honeymesh.service.d
sudo install -o root -g root -m 0644 /root/node-pro-review/20-node-pro.conf /etc/systemd/system/honeymesh.service.d/20-node-pro.confStore the separate client-secret in an app-private directory, mode 0600, owned by the dedicated app UID. Follow CUSTOMER_INSTALL.md for socket group access. Then start and check the agent:
sudo systemctl daemon-reload
sudo systemctl restart honeymesh.service
sudo systemctl status honeymesh.service --no-pager
curl --cacert /etc/honeymesh/certs/ca/ca.crt https://127.0.0.1:8443/api/healthFor Node Pro host integration, install the plan's signed pilot bundle and follow its included bridge guide. The standalone free SDK in Path A does not itself include the paid agent bridge. Configure the pilot bridge with the registered appId, socket path, and app-private client-secret. Send a controlled signed event and confirm it is observed in TEST. A wrong UID, secret, or app ID must be rejected. Keep auto_block off during initial setup.
Path C · local Linux protection
Download the standalone Core package, manifest, signature, and publisher key from the paid Core Beta page into the same folder.
The previous signed Core package is withdrawn. Wait for the replacement package and its matching signed manifest before installing. The package verification commands will be updated to the exact new release.
Stop if architecture is not x86_64, verification fails, or health is not good. Upload the emailed license.json in the local dashboard and check tier, node allowance, and expiry. Keep the dashboard on loopback; from your laptop, use:
ssh -L 8443:127.0.0.1:8443 USER@HOSTKeep Exchange and trusted sharing off. Observe a controlled trap in TEST and check normal traffic. Before a short ENFORCE test, confirm a separate console, protected management addresses, one controlled test source, and an independent control source. Select only the intended interface. Verify block and release, then return to TEST.
If management access fails, use your VPS provider console. Replace IFACE with the interface name you recorded before enforcement:
sudo systemctl stop honeymesh.service
sudo ip -details link show dev IFACE
sudo ip link set dev IFACE xdp off
sudo systemctl disable honeymesh.serviceSee the version-matched Core quickstart for removal and recovery details.