Most agent governance tools want you through a signup flow before you see a single screen. We shipped asqav demo so you can see the product without an account.
pip install asqav[cli]
asqav demo
That opens a local dashboard at http://localhost:3030 with four pre-loaded scenarios. No API key, no Docker, no cloud call. The HTTP server runs entirely inside the SDK.
What you see
Four risky agent actions, each with the full context a reviewer would need to decide:
- Claude Code wants to rm -rf ~/projects. High risk, destructive filesystem rule fires.
- Fintech agent wants to send an 850 000 EUR wire. Amount over threshold triggers HITL.
- DevOps agent wants to scale production to zero. Namespace + replicas rule blocks it.
- Clinical agent wants to order CT with contrast, allergy not checked. Medium risk, reviewer sees the gap.
Each card renders six fields: action payload, agent reasoning chain, risk classification with reason, triggering policy name and rule, a required reason textarea (minimum ten characters), and an expected diff preview. Approve or Deny produces an HMAC-signed receipt. The dashboard re-verifies each receipt in the browser and shows whether the signature is valid.
Why we built it
Agent governance sits at the top of a long conversation before engineers start wiring SDKs into their code. A demo that runs without a network, without an account, and without a container gives the technical buyer a working artifact to share in thirty seconds. The rest of the integration - real policies, cloud signatures, dashboard - follows once the team agrees this is the shape they want.
What this is not
The receipts in the demo use HMAC over canonical JSON. Production asqav uses ML-DSA-65 (FIPS 204) signatures and RFC 8785 JCS canonicalization. Swap asqav demo for asqav.init(api_key="sk_...") and you get the real cryptography, the multi-party signing, the incidents and compliance reports. The demo is a preview of the UX and the audit flow, not a stand-in for the production trust chain.
Source and docs
-
asqav demolives in the SDK, Apache 2.0: github.com/jagmarques/asqav-sdk - Approval card UX in the real dashboard: docs/approvals
- Attestation format (third-party verifiable, RFC 8785): docs/attestation