Air gapped install
Run agents and approved internal systems inside one boundary. Every message gets a signed receipt, outbound calls pass an allowlist, and an admin reviews every field before an offline export.
On this page
Inside your boundary, agents message each other and approved internal systems through a local engine. Nothing here uses a network. Every message gets a signed, hash chained receipt that holds a digest of the payload, never the payload.
Install the package first by following the offline install. The boundary is part of the workspace SDK in sdk/python of the repository.
Build a boundary#
from verdock.airgap import Boundary
box = Boundary("boundary", allow_hosts=["api-m.sandbox.paypal.com"])
box.register_agent("payout-agent")
box.register_agent("recon-agent")
box.register_system("ledger", handler=lambda sender, kind, payload: ...)
box.send("payout-agent", "recon-agent", "payout.proposed", {"amount": 500}) # delivered and receipted
box.send("payout-agent", "unapproved-crm", "export", {}) # blocked and receipted
box.egress("payout-agent", "evil.example.com") # blocked and loggedOutbound#
Outbound calls go only through the gateway allowlist in your policy. Each allowed call is receipted. Every other host is blocked and logged.
Offline export#
An admin reviews every field that would leave the boundary, then exports a signed bundle. The receiver checks it offline.
verdock airgap boundary --out bundle.json
verdock airgap boundary --out bundle.json --yes
verdock verify bundle.json --key BOUNDARY_PUBLIC_KEYWithout --yes the command shows the fields and writes nothing. With it, the signed bundle is written. The receiver learns nothing beyond the reviewed fields. A changed, removed or reordered receipt, or a different key, fails the check.