Scanner
Executes localized integrity checks against baseline configurations. Identifies state drift and structural entropy prior to pipeline execution.
docker pull fors33/fors33-scanner
Tamper-evident integrity for Docker volumes and sealed datasets. Public scanner and verifier images support independent checks. Pro covers sidecars and sealing; Lab adds engineering seats, registry history, and account-backed billing.
Cryptographic trust should be independently verifiable. The baseline tools required to scan environments and authenticate data provenance are publicly available as standalone container images. Auditors and systems engineers can verify L3dgr outputs independently.
Executes localized integrity checks against baseline configurations. Identifies state drift and structural entropy prior to pipeline execution.
docker pull fors33/fors33-scanner
Cryptographically authenticates .f33 sidecars. Ensures data provenance remains mathematically sound and tamper-free.
docker pull fors33/fors33-verifier
Verifier and Scanner are MIT-licensed open tools. They run locally on your infrastructure; they do not use the L3dgr Docker Desktop Extension airlock, L3dgr account OAuth, or L3dgr optional technical telemetry. These tools support integrity checks and audit preparation only. They do not certify compliance with SEC Rule 17a-4(f) or any other regulatory framework.
$19/mo $190/yr 1 seat
$129/mo $1,290/yr up to 4 seats
Contact for pricing Up to 10 seats
Contact for pricing Custom allocation
L3dgr support is scoped by plan. Self-serve tiers receive documented product support; integration depth, onboarding, and service levels are reserved for agreement-backed plans.
Email support for billing, key delivery, installation, and documented usage. Custom integration work and service-level guarantees are not included.
Pro support scope plus multiseat billing, tenant claims, registry history questions, and help interpreting compliance exports from the product.
Lab scope plus integration assistance, procurement and account coordination, compliance mapping workshops, and operator onboarding.
Institution support scope plus dedicated incident routing, on-premise deployment planning, and formal SLA language negotiated in enterprise agreements only.
These answers cover purchase, access, and support scope. For account-specific help, use the L3dgr support route.