İmovniača processes market data in real-time and generates signals that you can verify in the public ledger of results, before and after execution.
The dashboard displays active signals, verification status and execution history for each instrument you follow.
Each signal is timestamped at the moment of generation, before the trade is executed.
Accuracy rate, average position duration and number of verified records are available publicly, by instrument and time period.
Records cannot be changed retroactively. The status of each entry is visible in the ledger.
İmovniača does not offer a black box. Each signal comes with context: what data was used, what pattern was recognized and how many similar situations were recorded in the historical data.
The goal is to reduce noise in decision-making, not to replace the analyst. The platform is built for users who want to check the logic before trusting the signal.
Models are trained on historical and current market data and backtested before being applied to live data. Each model change is recorded with the date and reason for the change.
The result of backtesting for each version of the model is available as part of the ledger documentation.
The data is processed through the streaming API, without waiting for periodic updates. The system compares the current state of the market with the patterns recognized in the model and generates a signal as soon as the conditions match.
Integration with external data sources is performed through a documented API interface.
The position size and stop-loss level are calculated based on the current volatility of the instrument, not fixed settings. Risk parameters are adjusted per instrument, not across the entire portfolio at once.
The user can see at any time on which calculation the parameter was set.
The system pulls data from market feeds, the order book and relevant macroeconomic indicators. Data sources are listed next to each signal.
The model compares the current state with historical patterns and calculates the probability of the outcome repeating itself. The threshold for signal activation is adjustable by the user.
The system suggests the moment of execution that minimizes slippage, taking into account the current liquidity of the instrument. The recommendation can be made manually or via an API call.
The record format below corresponds to the actual structure of the public ledger. Each row represents one signal, from the generation to the closing of the position.
| The date | An instrument | Signal | Status | Verification |
|---|---|---|---|---|
| 04.03. | EUR/USD | Long | Closed · gain | Confirmed |
| 04.03. | DAX40 | Shorts | Closed · loss | Confirmed |
| 05.03. | BTC/USD | Long | Open | In processing |
| 05.03. | GBP/JPY | Shorts | Closed · gain | Confirmed |
The lines shown illustrate the structure of the record. The full history, including all instruments and time periods, is available on the public ledger.
View the entire ledger →Latency depends on market and data source. The data is processed via a streaming API, without periodic retrieval, so the signal is generated as soon as the model conditions match the current state of the market.
The integration takes place via an API or webhook call to a broker platform that supports it. The signal can be performed manually or automatically, depending on the user's settings.
API keys are stored encrypted and are not visible in the interface after entering them. Access to the account is limited to authorized sessions, and every change of settings is recorded in the internal log.
No credit card required for initial access.