Skip to the evidence
AI Trading SignalsDefinition / Population / Proof

FreqAI assessment

Open-source machine-learning extension

A documented ML workflow within Freqtrade; an implementation is not proof of an investable edge.

Earlier product descriptions were inspected 7 October 2026. This expanded edition adds public-source research and original educational cases on 13 October 2026. We have not trained these vendors' models, operated their paid accounts, certified live profitability or collected a genuine user-rating sample.

What is documented

FreqAI describes itself as a machine-learning extension for Freqtrade. Its framework can support user research, while the researcher remains responsible for the chosen features, labels, model and experiment definition.

Versioned records

Keep configuration and data identity with every training and evaluation run. Distinguish historical simulation, dry-run observation and actual orders. A new model identifier or altered feature set should not silently inherit an older experiment's validation claim.

Safety boundary

This page does not install a bot, supply trading credentials or deploy automated execution. No live profit or reliability test was conducted. Open-source availability enables inspection; it does not guarantee causal inputs, sensible position rules or favourable outcomes.

Sources

Compare the product categories

Framework capability without a strategy badge

FreqAI's originating documentation identifies an ML extension within Freqtrade. That supports a framework description, not proof that a selected configuration produces profitable or independent out-of-sample results. Retain the configured feature definitions, target, model artefacts, training windows and software version. Open-source inspectability can help a researcher ask precise questions while still requiring actual run records. This review installs no bot, shares no credentials and operates no live or dry-run trading account.

A retraining identity example

In a fictional review, configuration A generates an earlier series while configuration B changes a feature and training schedule. B must not silently inherit A's original evaluation label. The packet keeps both configurations, artefact IDs and producing-output bindings. A later reconstruction with B can be informative development research, but it cannot establish that the earlier prospective outputs came from B. Missing source data or runtime records limit the conclusion; they do not prove the framework or every user strategy failed.

Data and execution layers remain separate

Preserve actual feature availability and the complete prediction population, including missing or unresolved labels. A recorded prediction, a simulated order and a filled venue transaction answer different questions. A dry-run state cannot be upgraded to funded execution by a chart caption. A favourable historical research-fill window retains its own hypothetical status. Costs, collateral and real venue permissions need their actual definitions before a monetary comparison can be made.

Costs and operating scope to confirm

Free source code does not prove that data, computation, hosting or account implementation are free. Confirm the selected setup and what owns its normal operation before relying on its outputs. This publication does not create a personal-computer production dependency, managed bot or paid service. Compare FreqAI for the documented ML research task, with experiments and records at the required boundary. Its existence is neither an automatic edge guarantee nor a reason to invent an unsupported negative rating.

Direct sources and reviewed scope

Public documents, not private vendor experiments. The worked cases are invented; source dates do not establish a model-validation engagement.