The application
Trading
Signals on closed candles, plans with tiers and optional risk limits, backtests on two years of data. Execution always stays with you.
On this page
Create a plan to follow buy or sell conditions, then review its signals and test it on past data. The module is included in Pro. Signals provide information; no order is sent to your platform.
Pro plan
The trading module, its strategy editor and its backtests are part of the Pro plan.
No orders, ever
Patrima monitors, signals and plans. Execution stays with you, on your own exchange or wallet, by design.
Signals every 15 minutes
Evaluated on closed candles, so they can lag the live price on purpose. The Market data line at the top of the spot page shows when the data was retrieved.
Plans with tiers and limits
Entry and exit conditions, buy and sell tiers that each total 100%, and optional risk limits recorded with the plan.
Backtests on two years
Daily candles, signal on the close of one day and execution the next, fees and slippage included, with risk-adjusted metrics.
Open Strategy and choose a template: Simple DCA, Active accumulation with exit, Technical swing or Multi-signal convergence. The page then reads section by section: the plan in brief, the template, the conditions, the tiers, the risk limits, the followed assets and the backtest. Every setting is on the page, none is hidden behind a mode. Each condition reads as a sentence in your language; clicking it opens its type, its settings and its importance, required or optional.
Simple DCA only provides periodic buys. Active accumulation with exit also includes an exit condition. Multi-signal convergence exits only on protections, a stop that follows volatility or a loss limit, each of which sells the whole position: it has no sell tiers. To add sells to a Simple DCA plan, apply a template with an exit.
The template, conditions, tiers, risk limits and indicators all wait for Save, at the bottom of the screen: applying a template fills the page without saving it, and Discard changes returns to the saved plan. The assets a plan follows are saved at once, and so is creating, duplicating or deleting a plan, after confirming that unsaved changes will be lost: New plan and Duplicate sit next to the plan selector, Delete in the plan's menu. When a save is refused, the page says why and your changes stay on it. For plans with buys and sells, each side's tiers are meant to total 100%: the screen flags any other total, and a total above 100%, or a tier level of zero or below, is not saved. The buys draw from one of your reserve sub-pockets, chosen in the Tiers section; the destinations of the sales, when set, total 100%, each with a share above 0% and a different sub-pocket. An accumulation plan does not sell: its hidden sale settings never block a save.
Conditions are evaluated every 15 minutes using closed candles; a weekly condition reads only weeks that have closed, and a loss limit reads the loss at the last close. A signal closes once its conditions have not been met for more than three days in a row. An accumulation plan with a buying day opens one signal per period, week or month, so it buys once in each. The signal opens after the close of the buying day, read on closed candles: the purchase it describes falls on the next day, as in the backtest. Its amount is the asset's budget spread over the periods left in a two-year horizon, as the backtest spreads its capital: the horizon starts at the plan's first entry signal for the asset under its current rules, or now before that purchase, and a weekly plan that starts counts 104 periods, a buy of about $96 for a $10,000 budget. Renaming the plan does not restart the count, a change of its rules does, and once its 104 weeks or 24 months have passed a new horizon starts. A protective exit, a loss limit or a stop that follows volatility (ATR), arms a sale of the whole position at the exit signal price, read reached at once: the plan's sell tiers, placed above the exit price, serve the other exit conditions, and a fall does not reach them. For a plan whose required exits are all protective, such as Multi-signal convergence, sell tiers have no use: the Tiers section and the plan in brief say that each exit sells the whole position, for a plan saved with tiers before too. When the loss limit or the stop is met while another exit signal is already open, that signal closes and a protective one opens at the last close, with the same sale. The backtest executes that sale at the close of the day after the signal. The Signal log records detected events. The Market data line at the top of the spot page shows when the data used was retrieved.
Signal reliability counts the cycles opened under the current signal rules: the date next to its title says since when, and earlier cycles stay in the Signal log. Sell tier reached gives the share of closed cycles in which the price reached at least one sell tier armed by the exit signal, with the count under the rate; Sell tiers reached gives, for each tier, how many of the armed tiers the price reached, the tiers still open aside. Returns per cycle run from the price when the entry signal was detected to the price when the exit signal was, without your position sizes or fees; they do not represent your personal profit and loss. Cycles recorded before these prices were kept are not counted, and the duration of a cycle also runs from detection to detection. A cycle runs from an entry signal to the exit signal that follows: an entry signal that switches off before does not close it, and an asset that leaves its plan, excluded or no longer held, takes it out of the figures, as a change of its plan's rules does: the signal reopened under the new rules starts a new cycle. A protective exit ends the cycle without counting as a tier reached. A DCA plan never sells: its buys are counted apart, as periodic buys.
The backtest replays the plan on two calendar years of daily data, about 730 days for a crypto-asset and about 504 sessions for a stock. Its annualized figures, yearly growth and Sharpe and Sortino ratios, are computed on calendar time, so a stock's year is not read as 252 days. It assumes a signal at one day's close and execution the next day. Fees are counted at 0.1% per trade, and you can set slippage, the difference between an expected price and the execution price, from 0 to 500 basis points. It replays the conditions and tiers shown on the page, unsaved changes included: a rule can be tried before it is saved. Under the backtest, the copilot reads the strategy or this result when you ask: the strategy analysis covers the saved plan, the backtest analysis the result on screen.
Compare return, maximum drawdown, the number of cycles and performance against buying and holding over the period. Few cycles provide little evidence. A good past result does not guarantee a future one.
A backtest compares at most four distinct external symbols in its conditions.
Never executed
Patrima never places orders. Signals and plans are information for a decision you take yourself; there is no execution feature to enable.
Frequently asked questions
Why does a signal not match the live price?
Signals are computed on closed candles, not the live tick: this avoids reacting to noise that reverses before the candle closes. So a signal can lag the live price by design. The Market data line at the top of the spot page shows when the data used was retrieved. When a price source does not answer, the page uses its last prices, up to a day old, and a Prices line gives their time.
How are several conditions combined?
An entry signal opens when every required, active entry condition is met. An exit signal opens as soon as one required, active exit condition is met. An optional condition triggers nothing: at entry it is counted alongside the others, at exit it is ignored. A plan without a required entry condition opens no signal, and neither does a plan without a required exit condition, unless it is an accumulation plan, which never sells. The Conditions section states both rules above its lists.
Does saving a plan change its open signals?
Only when the signal rules change: the conditions, the plan type or the tiers. The next run of the engine then closes the plan's open signals, cancels their tiers, and opens them again under the new rules where their conditions are met. A signal reopened on the same origin stays the same signal: the Signal log shows the close and the reopening, without a new notification for the signal or for the tiers it had already reached; a tier it reaches for the first time notifies. The other settings, such as the indicators shown, the capital flow or the risk limits, leave the signals as they are, and the save bar says before you save when the signals will restart. Moving an asset to another plan restarts its signals the same way.
Which positions does the default plan follow?
The tradable positions you hold that have a price and market data, stablecoins and cash aside. A position without a price, as most deposit and liquidity tokens are, or without market data for its indicators, is not followed: no signal, no tier, and its panel on the spot page says why. Under Followed assets on the strategy page, it shows with its switch off and the reason under its symbol. Switching it on, or choosing a plan for it, makes it follow that plan; an asset you assigned to a plan follows it in any case. An asset enrolled in an accumulation plan that you no longer hold stays followed by that plan, which can signal a buy: the positions table lists it, marked no position, and Followed assets too, at zero, with the switch that excludes it; it stays out of the totals.
What does "Sell tier reached" under "Signal reliability" measure?
The share of closed signal cycles in which the price reached at least one sell tier armed by the exit signal, with the count under the rate, for example 3 of 6 cycles. This describes signals, not your actual trades or net gain. Only the cycles opened under the current signal rules count: the date next to the card's title says since when, and earlier cycles stay in the Signal log. A cycle runs from an entry signal to the exit signal that follows, even when the entry signal switched off in between; a change of the plan's rules takes the open cycle out of the figures. A protective exit, which sells at the signal price, does not count as a tier reached, and the buys of a DCA plan are counted apart.
How do I read a backtest, and how much can I trust it?
Start with the four figures above the chart: the strategy's return, that of buying and holding over the same period, the gap between the two and the max drawdown. Efficiency, under the chart, gives the number of closed cycles and the simulated fees: few cycles provide little evidence, and the result then says so. The glossary explains the metrics; past results do not predict future ones.
What are risk limits?
Optional limits per plan, each in whole percents: maximum exposure per asset, maximum capital committed, and a portfolio stop-loss. The plan in brief shows them and the copilot reads them in its analysis; signals and the backtest do not apply them.
Why does my accumulation plan never signal a sell?
Simple DCA only provides buys. For exits, apply a template that includes them, such as Active accumulation with exit.
Why does the spot value start with ≈?
The totals count the positions of the table: the tradable ones you hold, stablecoins and cash aside. The total adds up those that have a price, and the realized P&L also counts the tradable positions you sold in full. As on the dashboard, the realized P&L reads – only when a sale rests on an unknown cost: a wallet read by a sync and never sold does not hide it. When a token has no price available, it is left out of the total, which then shows ≈, and the ? next to its label counts the positions left out. When no position has a price, the total shows a dash, never zero. The unrealized P&L total adds up the positions that have both a price and a known cost: when others are missing, it shows ≈ with the count under it, for example 1 position counted out of 8, and when none qualifies it shows a dash. The dashboard's realized and unrealized trading count the same sales and the same positions by the same rule. A token recorded with its contract address is priced by that address, the same way on every page. A price is also set aside, and the token counted among those without a price, when its source marks it as unreliable or when it is more than ten times above or below the price your wallet sync recorded in the last seven days: such a gap is a wrong quote, not a market move. The trading pages and signals read only the prices of Patrima's sources: a token the dashboard values at the last price your wallet provider recorded counts here among those without a price, where the dashboard's unrealized trading counts it, with ≈. An account in which a sale or a transfer takes more than it held at its date is left out of the page's figures and of the signals, as on the dashboard: a message at the top of the page names it and leads to the transactions, where correcting a date or a quantity brings it back.
What does "Tiers reached" show on the spot page?
A tier is reached when the price crosses the level your plan set from the price of an open signal. The card lists each reached tier with its price and the amount your plan set for it, sales first; a purchase without an amount means the buy source is empty, or that the allocation reading is incomplete (a position without price, an account not read) and budgets are on hold, which the Buy budget card states. Without a saved allocation plan, or when the default plan has no buy source, the card says so too and leads to the allocation or the strategy. Each asset draws on its own plan's buy source, and its sales go to its own plan's destinations: the card also shows the sources of the other plans. For an asset whose cost is unknown, such as a position read from a synchronized wallet, the conditions and the tiers are evaluated, except a loss limit: it reads the P&L, unknown, and does not fire. The card counts the followed positions in that case. On an account entered by hand, recording the purchase price in Transactions completes the cost; on a synchronized wallet or exchange, that entry is refused, since its rows come from its source. It is a reading of your plan: Patrima places no orders, and doing nothing remains an option. In the positions table, a position's status comes from the recorded signal, the same one the Signal log uses, and the filters (Tiers reached, Signals, Waiting, No plan, No price) sort every position into one of them; No price gathers the positions without a plan or a price. The table opens sorted by value, largest first.
Why can a position's status differ from its conditions?
The status in the positions table comes from the recorded signal, the same one the Signal log keeps. The panel of a position also shows its conditions at the last market data reading, evaluated on closed candles, with their values in your language. Between two runs of the engine, every 15 minutes, the live reading can already differ from the recorded signal; the next run records the change. For a position whose cost is unknown, a loss limit reads P&L unknown and does not fire; its other conditions are evaluated.
How do I read the Signal log?
The Signal log lists every event your trading plan recorded, newest first: an entry or exit signal that opens or closes, a tier reached, a tier cancelled. Each row gives the date and time in UTC, the asset, the event, the direction with its tier, and the detail: the signal price, the tier price, or why a signal closed, for example conditions not met for 4 days, or a new buying window for an accumulation plan. You can filter by event type and search an asset. The log stays readable without the Pro plan, because it holds your account's data; new signals are recorded with the Pro plan.
Can Patrima execute trades for me?
No. It monitors, signals and plans; execution stays with you, on your own exchange or wallet. This is a deliberate design choice, not a missing feature.
See also