Pipeline Infrastructure
The threat engine runs on dedicated Hetzner workers behind Temporal workflows, with Postgres for state, Redis for queues, and Pinecone for the Evidence Vault.
Overview
Signal verification and thesis monitoring need durable, replayable workflows — not stateless lambda calls. Every pipeline run, every drift check, and every stop-loss watch is a Temporal workflow with explicit state, timers, retries, and an audit trail. Workers run on dedicated Hetzner hardware.
Infrastructure features
Temporal-orchestrated workflows
Thesis Guard, Earnings Distillation, and stop-loss watchers each run as a durable Temporal workflow with deterministic replay.
Auto-scaling worker pools
Workers scale on signal volume. Earnings days and macro shocks burst capacity automatically; idle hours scale down to baseline.
Isolated tenant compute
Each user gets an isolated worker queue and Temporal namespace. Evidence is namespaced per user in Pinecone.
Edge + cloud split
Scraping and browser automation runs on edge workers over residential IPs. LLM inference, embeddings, and DB writes run on Hetzner cloud workers.
Stack reference
Each pipeline run uses the following components:
Operational targets
99.95%
Workflow durability
< 200ms
Signal API p99
100%
Workflow audit trail