You are the one who has to sell this internally, in meetings we are not in. Anything a security reviewer needs is ungated, because asking an engineer to fill in a form to read your architecture is how you get marked unresponsive.
The short version. What ClawMetry is, who it is for, what it costs directionally, and what a rollout looks like. The one to forward to someone who has thirty seconds.
Where data is collected, what is encrypted and how, exactly what leaves the machine, subprocessors, supply-chain controls, and the certifications we do not hold.
Entity and contracting details, insurance position, data processing, support commitments, and the eight questions every vendor review asks. Written to be pasted into your process.
Which of your specific agent runtimes we can observe, alert on, and actually block — because that varies, and averaging over it would be dishonest.
These are being produced. If you need one before it is published, ask — a real request moves it up the queue, and we would rather send you a draft than a placeholder.
The consensus security questionnaire, completed. Pre-answers most of a standard vendor security review.
A real, redacted evidence bundle generated by the product, mapped to NIST AI RMF and SOC 2 control families.
A worksheet for estimating current agent spend and the share of it that is recoverable waste, using your own numbers rather than ours.
Installation, licensing, and update procedure for networks with no outbound route.