Online and offline usage
Verdock runs in your network. Online, only two things leave and both can be switched off. Offline, licence and usage are checked and counted locally.
On this page
Verdock runs where your agents run. We never receive your data, transactions, prompts, receipts or keys.
What runs where#
| Part | Network needed |
|---|---|
| Policy decisions, caps, outcome checks, signed receipts | None |
| The offline verifier (Python, Node, browser) | None |
verdock demo --offline | None. Every socket call is blocked and the run reports 0 attempts. |
| Provider adapters | The provider API, only when you use them, in test mode |
| The egress gateway | An opt in network API. No quickstart command starts it. |
| The hosted test workspace | getverdock.com |
The Python and Node packages contain no hosted workspace, no private runtime, no managed signing keys, no deployment tools and no telemetry.
Online: the only two things that leave#
An optional licence check and a signed usage count. Both can be switched off. The exact fields are on what leaves your machine and the policy is on the data policy.
Offline: how usage is counted#
- A signed licence file checked locally.
- A hash chained local usage counter.
- A quarterly signed usage export.
- A true up at renewal.
Evidence is never locked. After expiry there is 30 days of grace, then new actions stop and old receipts still verify offline with the public key.
Updates and support#
Updates are signed and you choose when to install. Support works from a redacted diagnostics bundle that you review before sending. We reproduce with test data.