Frequently asked questions
Frequently asked questions
TradeClaw's public hosted archive currently has no TradeClaw paywall, and the self-hosted code is MIT-licensed. Third-party hosting, market-data, broker, and notification services may charge their own fees. See /data-freshness for source-specific refresh cadences.
TradeClaw's open rule-based engine combines technical indicators such as RSI, MACD, Bollinger Bands, EMA, and ATR with multi-timeframe confluence. BUY/SELL labels and confidence values describe weighted indicator agreement, not a probability of profit. No external AI API is required.
Automated execution is disabled by default. When an operator explicitly enables it, only gate-approved crypto signals can reach the implemented Binance USDT-perpetual executor, which uses testnet by default. The RoboForex R StocksTrader execution bridge is still an interface scaffold, so forex, metals, and equities remain signal-only. MetaApi is used by a separate account/position viewer; it is not the signal data source or an implemented execution route. Paper-trading results are simulated, not broker fills.
Clone the repo, copy .env.example to .env, set DB_PASSWORD, USER_SESSION_SECRET, and AUTH_SECRET, then run `docker compose up -d`. The default stack maps documented .env variables through an explicit allowlist and starts the app, PostgreSQL, Redis, and migrations; startup time depends on image pulls and the host. MetaApi is not required. NEXT_PUBLIC_* values are compiled into the client bundle, so changing them requires matching image build arguments and a rebuild.
The public hosted archive is currently available without a TradeClaw paywall, and the codebase is MIT-licensed. Third-party hosting, data providers, brokers, and notification services may charge their own fees. The repository still contains optional or legacy integration code; its presence is not a promise that a paid hosted feature is available. Published outcomes are OHLCV-resolved signal studies, not broker fills or customer portfolio returns.