T3thr

T3thr routes normalized telemetry through one config file. The public container image on Docker Hub covers file and CSV workloads without a license. Pro adds live WebSocket, REST, message bus, and gRPC connectors with license verification inside the container at startup.

Plans

Core

Historical and batch workloads use local config only: no license key and no callback in this mode.

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

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

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