fleetmesh // MESHNODE OPS
Standalone Meshnode Control Console • meshnode-control/1 • meshctl • FIPS IP-less Access
OPERATOR CONNECTED UNIX SOCKET
Node Target (`unix://`, `fips://`, `https://`):
npub1... fd00::...
Node DID & Class
did:nostr:...
Class: anchor • Uptime: 0s
meshnode-control/1 Socket
0 Calls
/var/lib/meshnode/control.sock
FIPS IP-less Overlay
fd00::...
fips://npub1...
Compartments Lifecycle
0 / 0 Running
0 Refusals Recorded
Active Mesh Peerings
0 Peers
Pressure: 0%

1. Interactive Meshnode & `meshctl` Web CLI Terminal (No SSH Required) meshnode-control/1 + meshctl + fips

meshnode-ops$

2. Node Compartments, Lifecycle & Circuit Breakers 6 Compartments

Compartment Plane State Restarts / Trips Refusals Operator Action

3. Mesh Peerings, Bilateral Grants & FIPS Endpoints 0 Peers

Peer (`npub` / `fd00::/8`) Transport Standing Grant Budget Actions

4. Declarative `meshctl` Reconciler (`MeshNode`, `Peering`, `GrantPolicy`)

Declarative `fleetmesh.org/v1alpha1` Manifest (YAML)
`meshctl` Reconciler & Compiler Output
Run meshctl status, diff, apply, or export...
MESHNODE OPS Required role: node_operator

Fleetmesh Meshnode Ops

Authenticate with your Node Operator Token, Nostr Bunker (NIP-46), or Operator DID / Key to access meshctl & node telemetry.

Authenticates against the attached MeshTube user/admin store or local Meshnode Operator credentials.
or Browser Signer
Supports remote NIP-46 signers (bunker:// / nostrconnect://) and NIP-07 browser extensions (Alby, nos2x).
Signs a one-time cryptographic challenge using BIP-340 Schnorr secp256k1 and binds your did:nostr identity.
Use a signed mtpass_ portable identity ticket or a MeshTube mtk_ API key.
FleetMesh Unified Identity (v1) DID / NIP-46 / Service SSO