CLI reference

clawmetry license / clawmetry activate#

Manage the self-hosted Pro or Enterprise license.

clawmetry activate CLAW1.xxxxx        # shortcut
clawmetry license activate CLAW1.xxxxx
clawmetry license status

license#

clawmetry license [ACTION] [KEY] [--json]

--json emits {action, ok, ...}.

activate#

A shortcut for license activate, because it is the one people run.

clawmetry activate CLAW1.xxxxx
clawmetry activate CLAW1.xxxxx --json

The --json envelope is byte-identical to clawmetry license activate <KEY> --json, so a wrapper does not need to branch on which spelling was used.

Verification is offline#

Keys are verified cryptographically on the machine. There is no license server call in the activation path, which is what makes an air-gapped install possible at all.

CLAWMETRY_LICENSE_PING controls whether an optional check-in happens; CLAWMETRY_LICENSE_SERVER points at an alternative server if you run one.

Fingerprints#

clawmetry license fingerprint

Prints the machine fingerprint a key can be bound to. This is what you send when requesting a node-locked key, and what to check when a key that worked yesterday stops working — a fingerprint changes when the underlying machine identity does, which containers do more often than people expect.

Verify without activating#

clawmetry license verify CLAW1.xxxxx --json

Useful in provisioning: check a key is valid and covers what you need before committing a machine to it.

Where the license lives#

~/.clawmetry/license.key. It is a file — back it up with the rest of your configuration, and do not commit it.

When something looks locked#

clawmetry diagnose --json

That prints every input the resolver used: the license file, the cached cloud plan, the enforce environment variable, and the in-process cache state. It is much faster than guessing. → diagnose

Tier#

air_gapped_license is an Enterprise feature. Self-hosted Pro keys work offline too; the Enterprise variant covers the fully disconnected case with no optional check-in at all.