LatticeNet builds Lattice, a sovereign control plane for the agent era: self-hosted fleet management where the work can be done by hand or delegated to AI agents, and the judgment stays with the operator either way.

The mechanism is the identity. Every privileged change to a node is a reviewed plan; the approval hashes what the operator was actually shown; execution is bound to that exact plan, artifact digest, and target set; and a hash-chained audit log records what actually happened, not what was intended. Nodes run an outbound-only agent that holds its own last-line policy, so neither a compromised control plane nor a misbehaving automation can quietly own the fleet. Where the system does not know, it says unknown instead of green.

Core:

• lattice-server - the control plane: state, approvals, audit, plugin host.
• lattice-node-agent - outbound-only host agent with node-side capability flags.
• lattice-dashboard - strict-CSP Vue operator console, bundled into the server image.
• lattice-sdk - shared Go models and the plugin protocol contract.
• lattice - umbrella: overview, roadmap, tutorials, compose, developer handbook.

Plugins (signed, capability-scoped, sandboxed UIs):

• lattice-plugin-vpn-core - sing-box proxy lines, users, and usage.
• lattice-plugin-sub-store - native subscription platform: store, fetch, process, publish.
• lattice-plugin-netguard - nftables security groups with reviewed apply and reality reporting.
• lattice-plugin-wireguard - WireGuard networks and device peers, planned before applied.
• lattice-plugin-bridge - the sandboxed postMessage channel between plugin UIs and the host.
• lattice-plugin-template - starter kit and packaging tools for plugin authors.
• lattice-plugin-index - signed, read-only plugin catalogue. Not a live install channel by design.

Companions:

• Astra - iOS companion for phone-first review and approval.
• latticenet.github.io - public website and documentation.

• Agents dial out; nodes need no public inbound management port.
• Dangerous host changes follow plan, review, approve, apply. Approvals are hash-bound to the reviewed plan.
• Scopes, node allowlists, and per-node capability gates are mandatory for high-risk operations.
• Plugins are signature-verified at install, load, read, and execute; their UIs run in opaque-origin sandboxes with no network of their own.
• Public exposure belongs behind WireGuard, Cloudflare Access, nginx/Caddy, or equivalent perimeter controls.

Lattice is in rapid alpha development and is operated daily against a real multi-region fleet of about thirty nodes. Stable releases are deliberate and rare; the alpha train moves fast. Server and dashboard versions on the alpha train are pinned to each other, agent releases embed compatibility metadata, and latest never selects a prerelease. Read the hardening guide before exposing a deployment, and enable privileged node execution only where reviewed host mutation is required.