Scanner
Maps attested vs unattested files by sidecar presence. Emits coverage baselines. Does not validate signatures.
pip install fors33-scanner==0.10.0
docker pull fors33/fors33-scanner:v0.10.0
L3dgr
Tamper-evident integrity for operator-selected folders and sealed datasets. Public scanner and verifier tools on PyPI and container images support independent checks. Pro covers sidecars and sealing; Lab adds engineering seats, registry history, and account-backed billing.
Open Verification
Cryptographic trust should be independently verifiable. Current pins are Fors33 Scanner 0.10.0 and Fors33 Verifier 0.11.0 on PyPI and Docker Hub. They do not require Docker Desktop or an L3dgr account. Auditors and systems engineers can verify L3dgr outputs independently.
Verifier
Authenticates .f33 sidecars and sealed trees. Uses --mode auto or --mode sidecars. Validates signatures.
pip install fors33-verifier==0.11.0
docker pull fors33/fors33-verifier:v0.11.0
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.
Ten-Minute Recipe
First integrity check with Python 3.9–3.12. No Docker Desktop, no OAuth, and no Seal license. Pin versions. Do not use :latest as an assurance baseline.
-
01 · Install
Verifier on the machine that holds the tree.
pip install fors33-verifier==0.11.0
-
02 · Optional scan
Sidecar presence, not proof.
pip install fors33-scanner==0.10.0 fors33-scanner --root ./data --json
-
03 · Verify
Use --mode sidecars when .f33 files already exist.
fors33-verifier --mode auto --root ./data --format json
CI: pin
fors33-official/fors33-verifier@v0.11.0
(file plus hash, or mode / root for a tree).
Coverage gate:
fors33-scanner@v0.10.0.
After a pass, Seal and seats are on
Licensing,
L3dgr Beta,
or
sales@fors33.com.
These tools support integrity checks and audit preparation. They do not certify compliance with SEC Rule
17a-4(f) or any other regulatory framework.
Licensing
Pro checkout is temporarily unavailable while we finish the L3dgr Docker extension release. Lab is not offered as self-serve checkout. Apply for L3dgr Beta or contact sales@fors33.com for Institution plans.
Billing
Pro
$19/mo $190/yr 1 seat
- Public scanner and verifier for independent audit (above)
- Sealed volumes and .f33 sidecar generation
- Documented API Key Delivery
- Includes access to T3thr's File and Live Connectors
Lab
Opens later engineering seats
- Everything included with Pro
- Engineering seats and registry history
- Account-backed billing and tenant claim
- Multiseat signing
Institution
Contact for pricing Seats, air-gap, and SLA by agreement
- Everything included with Lab
- Custom operator seats, air-gap, and on-premise options
- Customer-owned immutable storage for audit preparation
- Account-backed billing and dedicated SLA by signed order form
Fors33 Relay
Optional hosted continuity when your edge workstation cannot keep cloud-reachable ingest running. L3dgr remains your control plane for configuration, sealing, and evidence. Configure release and reconcile in L3dgr Settings → System → Continuity. Not available for air-gapped entitlements.
- Relay Burst
- Release streams before planned outages: extension updates, quitting Docker Desktop, or shutdown. Segments reconcile when L3dgr returns. Metered stream time applies after included hours.
- Relay Always
- Run always-on ingest without keeping Docker or your laptop running. Stream caps follow your workspace entitlement. Enterprise agreements may pin region and SLA by contract.
- Outage coverage
- Burst covers short planned edge outages. Always covers continuous ingest when the source is reachable from Fors33 Relay. See Service status for plane health; full continuity framing in Relay documentation.
Support by Plan
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.
Pro
Email support for billing, key delivery, installation, and documented usage. Custom integration work and service-level guarantees are not included.
Lab
Pro support scope plus multiseat billing, tenant claims, registry history questions, and help interpreting product exports.
Institution
Lab scope plus integration assistance, procurement and account coordination, integrity and retention workshops, operator onboarding, dedicated incident routing, on-premise deployment planning, and formal SLA language in a signed Institution agreement.
Common Questions
These answers cover purchase, access, and support scope. For account-specific help, use the L3dgr support route.
- What happens after checkout?
- Stripe redirects paid checkouts to Key Delivery. The checkout email also carries the retrieval path for accessing the issued key.
- Where do I get my F33 API key?
- Use Key Delivery after checkout. The page shows your issued key when the checkout session ID or email retrieval link is still valid.
- Can I upgrade from Pro to Lab?
- Yes. Route Pro to Lab upgrades through L3dgr support so billing, seat limits, and tenant access update without a second purchase.
- Does Pro include T3thr connectors?
- Yes. Pro includes documented access to T3thr File and Live Connectors as part of the L3dgr entitlement set for pipeline ingress.
- Do plans include custom integrations?
- Custom integration support is not included with self-serve Pro. Institution plans can include integration work by agreement.
- Is there an SLA?
- Pro and Lab do not include a published SLA. Institution response targets and uptime terms are defined only in a signed agreement.
- Pro vs Lab?
- Pro: one seat, sealed volumes, .f33 sidecars, and public scanner or verifier use with documented key delivery. Lab adds engineering seats, account-backed billing, tenant claims, and registry history.
- What support is included?
- Support follows Support by Plan above, from documented Pro email help through agreement-backed Institution coverage. Contact L3dgr support with tier, account email, and Docker Desktop build for routing.
- Compliance documents?
- See L3dgr legal & compliance for privacy, commercial, and extension terms, and the SEC 17a-4 Compliance Checklist for regulated review. PDFs support procurement review without exposing protected product internals.