Choose the boundary
Host one Exchange for the organization on a Linux VM or inside a private network. Name the organization owner, backup owner, and administrators before enrolling nodes.
Loading HoneyMesh...
Loading HoneyMesh...
Organization controlled intelligence
A Private HoneyMesh Exchange gives an organization one place to coordinate threat signals across the networks it operates. Each network keeps a separate identity and local control over what it accepts and enforces.
The Exchange is a Node.js control and signal service. It can sit in your own network or on an organization managed VPS. HoneyMesh agents remain on the protected Linux hosts.
An optional bridge to another organization or the hosted Exchange requires its own approval path. Private operation does not require sending signals to the hosted service.
Host one Exchange for the organization on a Linux VM or inside a private network. Name the organization owner, backup owner, and administrators before enrolling nodes.
Run the HoneyMesh Exchange Node application behind an HTTPS reverse proxy. Keep its database, admin console, and Node port private. Use a dedicated service account and durable storage.
Provision the first admin through a one-time local bootstrap, require MFA, and enroll each HoneyMesh cluster with its own identity. Never copy a node credential between networks.
Start with an organization-only directory. Approve which clusters may publish and which may receive. Require separate approval for any outside network or hosted Exchange bridge.
Start with feed review and no automatic enforcement. Test a controlled signal, revocation, expiry, backup restore, and the kill switch before enabling short-lived local enforcement.
Your team runs the Exchange, controls the database and retention, and decides who may administer it.
A cluster joining the directory does not gain permission to send signals to every other cluster. Review and approve each sharing path.
The receiving HoneyMesh node keeps its own trust list, mode, allowlist, and enforcement switch. A shared indicator is not an unconditional ban.
Use short signal lifetimes, retraction, audit records, and an Exchange kill switch. Keep a tested backup and restore procedure.
The Exchange Node application already supports a configurable Exchange address, signed node traffic, discovery, explicit sharing relationships, a private admin console, and a local SQLite pilot. The organization self-host package is being prepared as a controlled preview. It still needs a repeatable installer, production database and recovery decision, and full deployment validation before we offer it as a turnkey download.
Use the blueprint to design a pilot now. Request the preview package and a guided setup when your organization is ready to test it.