ClawMetry Cloud - See your OpenClaw agents' costs, activity & memory live
byā¢
Your OpenClaw agent is running, but do you know what it's doing or how much it's costing? ClawMetry Cloud gives you live flow visualization, token costs, memory state, and sub-agent activity from any browser or Mac app. Two commands to connect: pip install clawmetry, then clawmetry connect. E2E encrypted, your data never touches our servers unencrypted. Open source locally, $5/node/month for cloud. 7-day free trial.



Replies
ClawMetry
Hey Product Hunt! š
I'm Vivek, the maker of ClawMetry. A few weeks ago, I launched the open-source version here and you gave an incredible #5 Product of the Day. Thank you!
But after talking to dozens of users, one thing kept coming up: "I love the dashboard, but I can't see it when I'm away from my desk."
That's the problem ClawMetry Cloud solves. It syncs your AI agent metrics to the cloud so you can check on your agents from any browser, anywhere. The catch? We built it with end-to-end encryption, your data is encrypted before it ever leaves your machine. Even we can't read it.
What's new in Cloud:
⢠š E2E encrypted sync (zero-knowledge architecture)
⢠š Browser access from anywhere (https://app.clawmetry.com/)
⢠š Multi-node monitoring (all your agents, one dashboard)
⢠š Native Mac app
Some context on traction:
⢠75K+ PyPI downloads
⢠Built for the OpenClaw ecosystem (316K GitHub stars)
⢠7-day free trial, then $5/node/month
I'd love to hear: What's the biggest pain point you have monitoring your AI agents in production?
Happy to answer any questions! š
Okan
Having E2E encryption built right into the monitoring layer is a massive relief for anyone running OpenClaw agents on untrusted networks. I would definitely use this to keep tabs on my remote scraping nodes without having to tunnel into each server manually. I am really curious to hear how you handle the initial key exchange process when provisioning a new agent from the command line.
ClawMetry
@y_takaĀ thanks for the feedback! Regarding the E2E encryption, When you run clawmetry connect, the CLI generates a random AES-256 encryption key locally on your machine. This key never leaves your device. The CLI then authenticates with our API using your cm_ API key, and starts pushing encrypted snapshots. The encryption key is stored in ~/.clawmetry/config.json alongside your API key. When you open the dashboard in the browser, you enter (or paste) that same key once, and it's stored in localStorage. All decryption happens client-side in the browser via Web Crypto API. Our servers only ever see encrypted blobs, never the key, never the plaintext.
co.dev
congrats on the launch!