Search brief

Risk management for algos belongs before the broker.

Algorithmic strategies need rules that run before orders leave the automation stack. Titan provides that pre-trade decision layer without taking broker custody.

How it works

01

Signal

Your bot, alert, or REST client creates order intent.

02

Evaluate

Titan checks the signal against configured pre-trade gates before broker submission.

03

Return

Titan returns allow or block output with a reason, trace id, and decision trail.

04

Execute

Your own execution path decides what to do next. Hosted Titan does not place orders.

Guardrails before execution

Titan checks the proposed order against risk rules before broker submission. The point is to catch bad automation states before they become broker events.

Audit trails for decisions

Decision receipts let operators inspect what Titan evaluated, which gate stopped the signal, and which account state informed the answer.

Risk boundary

Titan can enforce configured rules and preserve evidence. It cannot make a strategy profitable or prove a broker fill happened.

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.