Application policy
Login abuse review
Your app records verified failed logins. Compare an OBSERVE policy with a short application-level throttle before enabling it.
Loading HoneyMesh...
Builder / free local guides
These guides give your administrators a starting point. Enter configuration, network details, build records, and secrets only on systems you control. This website has no setup form, credential generator, build tracker, or remote connection to your environment.
Ideas you can run locally
Each example starts with data your application already knows and ends with a decision you can inspect. The guides show the current tools and their limits.
Application policy
Your app records verified failed logins. Compare an OBSERVE policy with a short application-level throttle before enabling it.
Integration protection
Check a webhook's signature, timestamp, delivery ID, and body size in your own app. Reject duplicate deliveries without sending the secret here.
Admin workflow
Start with synthetic traffic, edit the proposed policy, and review changed decisions and policy hashes before touching a live application.
Incident review
Replay ordered observations to explain when a restriction would begin and expire. Export a redacted result into your own incident record.
Builder template
Generate a route-scoped policy with selected and unaffected control fixtures. Review changed decisions and the checks still needed before deployment.
Builder template
Model a short application deny after your app verifies a replay. The template does not replace webhook signature validation.
Identity policy
Compare two synthetic tenants behind the same IP. A selected tenant can reach a policy threshold while the control tenant stays open. Real tenant identity must come from application authentication.
All examples run in your environment. Policy comparison and replay simulate application decisions; they do not prove live host or packet enforcement.
Run on your own machine
Use a disposable Node.js project. These commands install the published alpha and generate a local random value; they do not contact Network Decode with your configuration. Keep the generated value in your own secret store.
mkdir node-guard-evaluation && cd node-guard-evaluation
npm init -y
npm install @network-decode/node-guard@0.2.0-alpha.12
node -p "require('./node_modules/@network-decode/node-guard/package.json').version"
node -e "console.log(require('node:crypto').randomBytes(32).toString('hex'))"The final command prints a sample local secret in your terminal. It does not register a token or grant access to a HoneyMesh host. Use the package documentation for the exact local API and webhook configuration.
Builder starter kit / published alpha.12
The published alpha.12 package creates a local project from login-abuse, API-probing, webhook-replay, or tenant-API templates. Each compares OBSERVE with proposed ENFORCE using selected and unaffected control fixtures. A review command saves a redacted local report and leaves source attribution and production approval unchecked.
mkdir nodeguard-builder && cd nodeguard-builder
npm init -y
npm install @network-decode/node-guard@0.2.0-alpha.12
npx nodeguard builder templates
npx nodeguard builder init my-security-tool --template api-probing
npx nodeguard builder check my-security-tool
npx nodeguard builder review my-security-tool --output my-review.jsonThe example uses synthetic source addresses. Adapt its files locally, verify real source identity in your application, and keep real events, reports, and secrets in your own systems. The report is created with restricted file permissions and refuses to overwrite an existing file. No command installs a host agent or activates a kernel rule.
Read the Builder starter kit guideGoal: Qualify a pinned package in a disposable project.
Deliverable: A local build record and a rollback path held by your team.
Goal: Compare current and proposed application decisions.
Deliverable: A reviewable policy change with an explicit rollback step. Simulation does not apply a host rule.
Goal: Reproduce an application decision from ordered evidence.
Deliverable: A local, redacted decision record. Replay does not prove a live packet drop.
Goal: Test a signed event without sending its secret to this site.
Deliverable: A local verification matrix and a secret-rotation plan.
Goal: Make local configuration, build, and rollback repeatable.
Deliverable: A runbook and build record controlled by your organization. Builder does not deploy builds or manage hosts.
The proposed HoneyMesh API and distributed Exchange remain under development. These public guides do not issue paid host licenses or enable kernel enforcement.