DATA, NETWORK AND DEPLOYMENT
What runs on your machine, and what leaves it.
Measured on one reference install, not estimated. If you are evaluating ClawMetry for a fleet, this is the page to send to whoever owns the risk.
Before you put a daemon on your laptop
The footprint, measured.
Measured on one reference install: 165 sessions, 19,977 events. Not estimated.
Footprint
clawmetry uninstallThe query server binds to loopback only, with a one-time 32-hex token and a discovery file at mode 0600. It is why the dashboard can read the store without holding the writer lock.
What leaves, exactly
Never. These stay in the local file.
The key is generated on the node and never leaves it. Decryption happens in your browser. Compelled by a subpoena, we hand over a blob we cannot open, plus the node id, the version and some counters.
The local file is plaintext
Everything is sealed in transit and at rest in our cloud, and it is not encrypted on your own disk. The DuckDB file carries default user permissions. Anything running as your user can read it.
Redaction fails open
Secrets are fingerprinted at ingest by default, before disk. It is pattern-based, and on an internal error it keeps the original value rather than dropping data. It is tuned for credential shapes, not customer PII.
A connected node can be stopped remotely
If you turn cloud on, Stop, Pause and Resume are reachable from the dashboard and the desk device for any node on the account. That is the feature. Run local-only and no such channel exists.
Three places to run it
Cloud is optional.
It always was.
The daemon computes into a DuckDB file on your own disk. Where the dashboard lives after that is your call, and it is the same rate whichever you pick.
01 · Local only
Nothing leaves
Included in the MIT core
The dashboard reads the local file through a loopback query server. There is no account, no sync and no destination to point at.
- Network destinations: none
- Inbound ports opened: 0
- Free forever for OpenClaw, NVIDIA NemoClaw and Goose
02 · Our cloud
Sealed before it leaves
$19 per node, per month
The snapshot is encrypted on the node with a key generated there and never sent. Your browser decrypts it. Subpoena us and we hand over a blob we cannot open.
- AES-256-GCM, key held on the node
- Decryption happens client side
- Stop, Pause and Resume reach any node on the account
03 · Self-hosted
Your infrastructure, single tenant
$190 per node, per year
One container serves the UI and the ingest API on your own network, with node tokens and admin auth. Licences verify offline against an embedded Ed25519 key you can fingerprint and compare.
- No calls to clawmetry.com beyond an off-by-default version ping
- Same feature set, same runtimes, same rate
- Two months free against the monthly price
The rate does not change with the deployment. Self-hosted is $19 per node per month or $190 per node per year, exactly like the cloud plan, because you are paying for the software and not for our servers. What changes is who holds the data and who runs the container. Buy a self-hosted key without talking to anyone.