01
Your application proposes the trade
It supplies the instrument, direction, entry, stop, and requested risk. TFFP does not generate the trading signal.
TFFP Risk Engine
Shared risk policy for trading applications
One risk engine across strategies, accounts, and execution workflows
The TFFP Risk Engine is deterministic risk-policy infrastructure for trading applications. Your application decides what it wants to trade. TFFP evaluates the proposed trade against current account state and customer-defined risk policies and returns a structured risk decision.
Become a Design PartnerALLOW
The proposed trade complies with the evaluated policy.
REDUCE
A smaller permitted risk amount is available for planning.
REJECT
No permissible executable risk remains.
UNAVAILABLE
Required risk or account state is not available.
The problem we are exploring
Individually acceptable trades can create unacceptable account-level risk
Position sizing inside one strategy is straightforward. Coordination becomes harder when multiple strategies, copiers, or execution processes share one account and one remaining risk budget.
Remaining account risk capacity
$500
- Strategy A requests
- $350
- Strategy B requests
- $300
- Copier requests
- $200
- Total requested
- $850
How should multiple trading processes coordinate one account-level risk policy and shared risk capacity?
How the TFFP Risk Engine works
02
TFFP evaluates risk
The engine evaluates per-trade risk, daily risk capacity, portfolio exposure, and trailing drawdown with deterministic calculations and explicit policy semantics.
03
TFFP returns a structured decision
Each evaluated rule can pass, fail, be unavailable, or be intentionally not evaluated, providing an explainable decision boundary.
Explainable risk decision
The most restrictive capacity guides the decision
- Requested risk
- $500
- Per-trade capacity
- $400
- Remaining daily capacity
- $200
- Portfolio capacity
- $275
- Trailing drawdown capacity
- $150
Decision
REDUCE
Permitted risk
$150
Binding constraint: Trailing drawdown
A REDUCE decision is planning guidance
A reduced executable trade must be revised and reevaluated before execution. Only an ALLOW decision is eligible to proceed through the currently supported executable workflow.
- Proposed trade
- REDUCE
- Revise size
- Reevaluate → ALLOW
Built for deterministic risk decisions
Decimal-safe calculations
Financial decisions do not depend on binary floating-point approximations.
Versioned policy semantics
Risk rules have explicit definitions rather than ambiguous labels such as daily loss.
Structured rule results
Applications can identify which rule passed, failed, was unavailable, or was not evaluated.
Explicit account state
Unknown account information is not silently treated as zero.
Calculation and execution context
Hypothetical calculations and executable trades can have different state requirements.
Framework-independent core
The Risk Engine is separated from the TFFP interface and trading-platform integrations.
Potential workflows
Where centralized risk policy may help
Trade copiers
Coordinate account-level risk policy across copier and subscriber execution workflows.
Multi-strategy systems
Evaluate independent strategies against shared account-level constraints.
Execution-enabled SaaS
Separate strategy logic from centralized risk-policy evaluation.
Multi-account applications
Apply consistent risk semantics across account workflows.
Proprietary trading tools
Reconstruct why a proposed trade was allowed, reduced, rejected, or unavailable.
Product boundary
TFFP evaluates risk
Conceptually: “Here is the trade I intend to place. Given this account state and customer-defined risk policy, what risk is permitted?”
Product boundary
TFFP does not choose the trade
It does not determine the instrument, buy or sell direction, entry, target, or strategy. The client application supplies the proposed trade.
Design partner program
We are looking for design partners
The core TFFP Risk Engine is running today. Before building a broad public developer platform, we are working with a small number of trading-technology teams to understand how they coordinate risk across strategies, accounts, and execution processes.
- Trade copier developers
- Multi-account trading software
- Execution-enabled trading SaaS
- Directly distributed algorithmic systems
- Prop-trading software
One integration path
Work with one specific existing trading workflow.
Narrow FX risk-policy scope
Define the exact account state and policy semantics being evaluated.
Shadow mode first
Existing execution continues normally while TFFP evaluates alongside it.
Compare decisions
Investigate disagreements with current risk logic.
Measure value
Assess decision agreement, account-state freshness, consistency, explainability, and engineering effort avoided.
Customer validation
Does your team deal with this today?
When multiple strategies request risk from the same account, how do you coordinate available capacity?
What happens when two requests arrive against the same remaining risk budget?
How do you keep risk policies consistent across strategies or customer accounts?
How do you reconstruct why a trade was allowed or blocked after the fact?
Help shape the TFFP Risk Engine
Discuss a design partnership
If your team already manages account-level risk across multiple strategies, accounts, or execution processes, we would like to learn how you are solving it.
Learn how the Risk Engine worksForex Risk Disclosure
Forex trading and leveraged trading involve substantial risk and are not appropriate for every trader. You can lose part or all of your capital. Educational content on TradingForexForProfit is provided for research, workflow, and training purposes only and should not be treated as individualized investment advice.
Always evaluate your own financial situation, risk tolerance, and account rules before placing a trade. Past performance does not guarantee future results.