Signal
Your bot, alert, or REST client creates order intent.
FAQ
Questions before routing automated signals through Titan.
Short answers for developers and signal operators evaluating Titan's pre-trade gate, receipt model, broker boundary, and proof limits.
How it works
Evaluate
Titan checks the signal against configured pre-trade gates before broker submission.
Return
Titan returns allow or block output with a reason, trace id, and decision trail.
Execute
Your own execution path decides what to do next. Hosted Titan does not place orders.
Direct answers
What is Titan Fortress?
Titan Fortress is hosted pre-trade diagnostics and decision infrastructure for automated trading systems. A signal source sends proposed intent to Titan before broker submission. Titan evaluates configured safety checks, returns an allow or block answer, and records a decision receipt that explains what was checked. It is diagnostics and control infrastructure, not a broker or signal generator.
How does Titan Fortress make automated trading safer?
Titan makes automated trading safer by moving risk checks to a required step before execution. It can stop duplicate signals, cooldown violations, daily-loss breaches, exposure limits, and broker-rejection patterns before your forwarder submits an order. The benefit is operational control and traceability, not guaranteed profit or guaranteed loss prevention.
Who is Titan for?
Titan is for developers, retail algo traders, and small trading desks that already have a strategy and execution path. It fits bots that send TradingView alerts, Python signals, or REST requests and need a separate pre-flight layer before broker submission. It is not for discretionary trading tips.
Does Titan place trades?
No. Hosted Titan evaluates and records signals; it does not independently place, close, or cancel broker orders. If Titan returns an allow result, your own forwarder or execution code decides what to do next. Your broker remains the system of record for orders, positions, and custody.
Is Titan compatible with my broker?
Titan's public examples are written around Alpaca because the hosted forwarder and CSV diagnostic support Alpaca workflows today. The core pre-trade eval API accepts generic order intent, but broker execution remains in your forwarder. If your broker differs, check the API shape and forwarder boundary before relying on it.
What is a pre-trade risk check?
A pre-trade risk check evaluates an order before it reaches the broker. It can inspect side, symbol, market hours, cooldowns, daily loss, exposure, sizing, bracket validity, and account state. The check answers whether the order should continue, stop, or be reviewed before execution.
What is a decision receipt?
A decision receipt is the record Titan writes for a signal evaluation. It includes the signal, outcome, reason, trace details, and verification path when proof artifacts are available. A receipt proves what Titan recorded; it does not prove broker execution, fills, profitability, or strategy quality.
Execution boundary
Hosted Titan evaluates and records proposed order intent. It does not generate signals, hold funds, require broker credentials for public evals, or independently place broker orders.