Tooling · built

The whole operator surface is one binary.

meshctl takes you from nothing to a running two-node mesh without hand-writing a config file or grepping a node ID out of logs. When you ask a node for status, it dials in as a real authenticated peer — because there's no back door to dial instead.

Commands

Command	What it does
`init-root`	Generate the mesh root signing key, once per mesh.
`gen-identity`	Make a node's keypair, print its node ID and the exact next command to run.
`issue-cert`	Sign a membership certificate for a node ID.
`init-config`	Scaffold a node's `meshnode.json` from flags.
`status`	Reachable? Authenticated? Then: roles, persistence/replication config, live realtime and shard peer counts.

./bin/meshctl init-root -out root.key
./bin/meshctl gen-identity -out node-a/identity.pem
CERT_A=$(./bin/meshctl issue-cert -root root.key -node <node-a-id>)
./bin/meshctl status -config node-a/meshnode.json -addr 127.0.0.1:17002

status reports what's actually true — "did the handshake succeed" is table stakes, not the answer.

Request a meshctl command →