T3thr

Time-series pipelines need a single config surface and a clear boundary between offline replay and live ingress. T3thr runs file and CSV paths in the default container image on Docker Hub. Pro adds WebSocket, REST, message bus, and gRPC connectors behind a signed JWT you load as FORS33_LICENSE_KEY, verified locally with no per-run remote checks in the documented path.

Plans

Core

Public container on Docker Hub. Historical and batch workloads use local config only: no license key and no callback in this mode. 

docker pull fors33/data-bridge
View on Docker Hub
  • File and CSV configs from mounted volume
  • Deterministic, keyless default path
  • Same image family as Pro (feature-gated)

Pro

Billing

$12/mo

Live connectors with license-gated JWT. Checkout returns to /t3thr/key?session_id={CHECKOUT_SESSION_ID}.

  • WebSocket, REST, message bus, and gRPC connectors
  • File and CSV paths remain available
  • Keys and rotation through Account
Subscribe to Pro

L3dgr ecosystem

Attestation, sealing, and Lab multiseat workflows pair with T3thr on shared operator and billing surfaces.

  • Open scanner and verifier images
  • Pro and Lab tiers for .f33 sidecars
  • Account-backed licensing
Open L3dgr hub

Container execution

Baseline (Core)

Mac / Linux example. Mount your config directory and point at default.toml.

docker run --rm \
  -v "$(pwd)/config:/app/config" \
  fors33/data-bridge \
  --config /app/config/default.toml

Windows (PowerShell): use backtick line continuation and ${PWD}/config for the volume mount.

Authenticated (Pro)

Export FORS33_LICENSE_KEY before docker run. License verification runs inside the container. 

docker run --rm \
  -e FORS33_LICENSE_KEY="your_key" \
  -v "$(pwd)/config:/app/config" \
  fors33/data-bridge \
  --config /app/config/default.toml

Operators remain responsible for network, retention, and compliance outside the engine.

Disclaimer: Software is provided as-is. Fors33 infrastructure executes locally; operators maintain absolute responsibility for network routing, hardware compliance, and data retention.