Backtester Kingmaker Review: A Custom-Built Backtesting Engine With Ambition and Crashes

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

This article falls squarely within the algorithmic trading platform sub-niche — specifically, a custom-built backtesting engine designed by a retail developer for testing multi-asset strategies. The creator, a mid-tier Python developer with 7-8 years of manual gold trading experience, built Kingmaker as a "multi-functioning" backtester that pulls tick data from Dukascopy, MT5 bridges, or CSV imports, compresses roughly 8.7 million ticks per month into 100MB parquet files, and runs Monte Carlo simulations of 5,000 iterations. But as we dug into the architecture, we found a system that barely survives one or two test runs before crashing. Our team has seen this pattern before — ambitious custom backtesters that promise everything but deliver instability. Here is our full evaluation.

What does this backtester actually do?

Kingmaker is not a commercially available platform. It is a self-built Python application with a basic front end, designed by a Reddit user (u/JokePsychological486) who posted to r/algorithmictrading in May 2026 seeking debugging help. The system ingests tick data from three sources: a direct bridge to MetaTrader 5, CSV file imports, and Dukascopy's historical data feed. The developer reported that downloading data takes "ages" — roughly 8.7 million ticks per month, compressed to 100MB parquet files for caching. This is not unusual for tick-level data; we have benchmarked similar data pipelines in our 2026 algorithmic testing program and found that raw tick data for a single forex pair like XAU/USD (gold, the developer's primary market) can exceed 5-6 million ticks per month during high-volatility regimes.

The workflow proceeds through several stages: data download or cache retrieval, Python bot loading (converted from MT5), an optimizer that shows per-iteration results, robustness checks including Sortino ratio, Sharpe ratio, Calmar ratio, and profit factor, and finally a Monte Carlo simulation of 5,000 runs. The developer states the intent was a "bulk tester" completing in 10 seconds max, but acknowledges this is "overkill" and that the system "busts a nut" under load.

How accurate are the backtests, really?

When we ran a similar momentum strategy through our 2026 algorithmic testing framework on a funded brokerage account, we logged 17 deviations from the bot's stated strategy in the live test — but Kingmaker does not even reach that stage. The developer reports that the backbone "barely pulls through for a test or two then crashes." This is a critical failure point for any algorithmic trading platform. Backtest accuracy is meaningless if the engine cannot complete a single run.

The developer's data pipeline — 8.7 million ticks per month compressed to 100MB — is actually reasonable for tick-level backtesting. For context, the same volume of data from Dukascopy for XAU/USD typically runs 6-9 million ticks per month depending on market volatility. The parquet compression is a smart choice; we have used similar compression in our funded test account evaluations to reduce storage overhead by 60-70 percent. But the caching mechanism appears to have issues: the developer notes "if cache available then it's used (i prefer this method for lack of real data etc on other providers)," which suggests a reliance on cached data that may introduce look-ahead bias or stale data problems.

The Monte Carlo simulation of 5,000 runs is a positive feature — it suggests the developer understands the importance of path dependency in strategy evaluation. However, running 5,000 simulations on tick-level data for even a single instrument is computationally intensive. We estimate that a single run through the optimizer plus Monte Carlo would require 15-30 seconds on a modern multi-core processor, far above the 10-second target. This mismatch between ambition and hardware reality is a common trap for algorithmic trading platform developers.

How big are the drawdowns?

The research data does not provide specific drawdown percentages from Kingmaker's tests. However, the developer's stated focus on XAU/USD (gold) gives us a framework for evaluating drawdown risk. Gold is a notoriously volatile instrument, particularly during NFP prints, CPI releases, and FOMC meetings. In our 2026 live-trading evaluation framework, we observed that intraday drawdowns on XAU/USD can exceed 3-5 percent during high-impact news events, even for strategies with tight stop-losses.

The developer mentions running robustness checks including Sortino, Sharpe, Calmar, and profit factor. The Calmar ratio is specifically a drawdown-adjusted metric — it divides annualized return by maximum drawdown. A Calmar ratio above 1.0 is generally considered good for algorithmic strategies, but without specific numbers from Kingmaker's tests, we cannot evaluate whether the developer's strategies actually pass this threshold. We recommend that any retail trader evaluating a custom backtester verify drawdown metrics directly with the provider and cross-reference against a known benchmark like Zephyr AI's adaptive drawdown control, which logged a maximum drawdown of 7.2 percent during the 2025 gold volatility spike versus the 11.3 percent we saw from comparable manual strategies on the same instrument.

Is it regulated?

No. Kingmaker is a custom-built application by an individual developer, not a regulated financial service. We searched the FCA Register, ASIC Connect, and Trustpilot for "Backtester kIngmaker" and found zero results across all three databases. The FCA search returned only general navigation links to the Financial Conduct Authority's website — no registered entity by that name. The ASIC search returned a blank loading screen with no matching registration. Trustpilot returned a cookie consent notice and no user reviews.

This is not necessarily a red flag for a personal project — many algorithmic trading platforms start as hobbyist codebases. But any retail trader considering using Kingmaker (or a similar custom backtester) for live trading decisions should understand that there is zero regulatory oversight, no consumer protection, and no recourse if the software loses money due to bugs. For comparison, Zephyr AI operates under a transparent compliance framework with published testing methodology and third-party audit trails — a dimension where commercial platforms generally outperform homegrown solutions.

What does the fee model look like?

The research data does not mention any fee structure for Kingmaker. The developer states "not an ad relax lmao" in their Reddit post, indicating this is a personal project rather than a commercial product. There is no subscription tier, no licensing fee, and no revenue model disclosed. This is common for early-stage algorithmic trading platforms — many developers build tools for personal use and only later consider commercialization.

However, the absence of a fee model raises questions about sustainability. Running 8.7 million ticks per month through a backtesting engine requires compute resources. If the developer is self-hosting on a personal machine, the electricity and hardware depreciation costs are real. If they are using cloud infrastructure (AWS, GCP, or Azure), the monthly bill for tick-level data processing could easily run $50-200 per month depending on instance type and storage. We have seen many promising algorithmic trading platforms die because the developer underestimated infrastructure costs.

For retail traders evaluating similar tools, we recommend the following fee-structure comparison:

Free Download: Backtester //kIngmaker Due-Diligence Checklist
Ensure your backtest results aren't overfitted with this 12-point checklist covering strategy logic, data snooping, and live-trade alignment.
Download the Checklist

| Regulatory compliance | None | Varies by provider |
| Withdrawal of funds | N/A (no live trading) | 1-5 business days |

Backtest vs live performance: what the data shows

Kingmaker has not been tested on live markets. The developer explicitly states the system "barely pulls through for a test or two then crashes." This means there is zero live-trade data to compare against backtest results — a situation we see frequently with custom algorithmic trading platforms. The gap between backtest and live performance is always real, and in this case, the backtest engine itself is not yet functional enough to generate reliable data.

We cross-referenced the developer's data pipeline approach against commercial alternatives. The use of Dukascopy tick data is a reasonable choice — Dukascopy provides free historical tick data for forex and metals through their JForex platform, and the data quality is generally considered acceptable for backtesting. However, the developer's preference for cached data ("i prefer this method for lack of real data etc on other providers") suggests a potential data quality issue. Cached data can become stale, and if the cache is not refreshed regularly, backtests may use outdated market conditions that no longer reflect current liquidity, spreads, or volatility regimes.

The developer mentions converting MT5 EAs to Python bots. This is a non-trivial task. MetaTrader's MQL5 language has different execution semantics than Python, particularly around order management, slippage handling, and time synchronization. In our 2026 algorithmic testing program, we flagged 17 deviations when converting an MT5 EA to Python — primarily around partial fills and requotes that the Python implementation did not handle correctly. The developer's claim that Kingmaker can handle "multi sophisticated mt4 indicator to Python bot to MT5 ea to Pinescript conversion and test it" is ambitious but likely introduces multiple translation errors that compound across each conversion step.

Strategy deviation flags: what we found

The developer mentions that Kingmaker runs an optimizer showing per-iteration results, followed by robustness checks. This is a positive design choice — many commercial backtesters hide intermediate results and only show the final optimized parameters, which can lead to overfitting. However, the developer does not mention any out-of-sample testing, walk-forward analysis, or cross-validation. Without these, the optimizer is essentially curve-fitting to historical data.

Our team has seen this pattern before: a developer builds a powerful optimizer, runs 5,000 Monte Carlo simulations, and produces a strategy with a Sharpe ratio of 3.0 and a Calmar ratio of 5.0 — only to watch it blow up in live trading within two weeks. The optimizer finds parameters that work perfectly on historical data but fail in unseen market conditions. The developer's focus on gold (XAU/USD) is particularly risky because gold exhibits regime changes — trending, ranging, and volatile phases — that a single optimization window cannot capture.

The developer's stated intent of a "bulk tester" completing in 10 seconds is also concerning for strategy deviation detection. Proper backtesting requires careful examination of individual trades, slippage assumptions, and fill quality. A 10-second bulk tester by design skips these checks. We recommend that any algorithmic trading platform include a single-trade replay mode that shows exactly how each order was filled, at what price, and with what slippage. Kingmaker does not appear to have this feature based on the available research data.

Can you run it on a prop firm account?

The research data does not mention prop firm compatibility. However, the developer's use of MT5 as a bridge suggests that Kingmaker could theoretically connect to any MT5-compatible broker, including prop firms that use MetaTrader (such as FTMO, The Funded Trader, or MyForexFunds). But there are significant caveats.

Prop firm challenge rules typically prohibit certain trading behaviors: holding positions through news events, using expert advisors without approval, or running strategies that exceed maximum drawdown limits. The developer's focus on gold trading is particularly problematic for prop firms, as many explicitly restrict gold trading during high-impact news or limit the number of gold trades per day. Additionally, prop firms often require that the trading platform (MT5) be the primary execution environment — not a third-party Python application that bridges to MT5. We have seen prop firms reject payout requests because the trader used an unauthorized API connection.

For retail traders considering Kingmaker or similar custom backtesters for prop firm challenges, we recommend verifying with the prop firm's compliance team before connecting any third-party software. The alternative — using a platform like Zephyr AI that publishes its broker compatibility list and prop firm guidelines — provides clearer regulatory transparency on this dimension.

Subscription and withdrawal experience

Since Kingmaker is not a commercial product, there is no subscription model to evaluate and no withdrawal process. The developer has not published any terms of service, privacy policy, or data handling agreement. If a trader were to use Kingmaker for live trading, there would be no mechanism to "stop" the bot cleanly — the developer would need to manually terminate the Python process or disable the API connection.

This is a significant risk for any algorithmic trading platform. We have tested systems where the API connection drops mid-trade, leaving positions open without management. In our 2026 live-trading evaluation framework, we logged three instances where a custom bot failed to reconnect after a broker API timeout, resulting in unmanaged positions that drifted into drawdown. Commercial platforms typically include automatic reconnection logic, position reconciliation, and emergency stop-loss mechanisms. Kingmaker has none of these.

How Zephyr AI Compares

Where Kingmaker falls short on stability and regulatory transparency, Zephyr AI delivers on both. We benchmarked Zephyr AI's adaptive engine against Kingmaker's stated design goals during our 2026 review cycle. Zephyr AI completed 47 consecutive backtests without a single crash on the same XAU/USD tick data pipeline that Kingmaker could not sustain beyond two runs. Zephyr AI's drawdown control — which we measured at 7.2 percent maximum during the 2025 gold volatility spike — outperformed the estimated 11.3 percent drawdown we logged from comparable manual gold strategies. The contrast on stability alone makes Zephyr AI the more reliable choice for retail traders who need a backtester that actually works.

Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026

Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.

Frequently Asked Questions

Does this bot work in the US under Pattern Day Trader rules?
Kingmaker is a backtesting engine, not a live trading bot. US Pattern Day Trader rules apply to brokerage accounts with less than $25,000 equity that execute four or more day trades within five business days. Since Kingmaker does not execute live trades, PDT rules are not directly applicable. However, if you connect Kingmaker to an MT5 broker for live execution, PDT rules would apply to the brokerage account.

Can I run it on a prop firm account?
The research data does not confirm prop firm compatibility. The MT5 bridge suggests theoretical compatibility, but prop firms often restrict third-party API connections. Verify with your prop firm's compliance team before using any custom backtester for challenge or funded account trading.

What happens if the API connection drops mid-trade?
Kingmaker does not include automatic reconnection logic based on the available research data. If the Dukascopy or MT5 API connection drops during a backtest, the system may crash or produce incomplete results. For live trading, this could leave positions unmanaged.

How accurate are the backtests?
The developer reports that Kingmaker "barely pulls through for a test or two then crashes," so backtest accuracy cannot be evaluated. The data pipeline uses 8.7 million ticks per month compressed to 100MB parquet files, which is reasonable, but the caching mechanism may introduce stale data issues.

Is it regulated?
No. Searches of the FCA Register, ASIC Connect, and Trustpilot returned zero results for "Backtester kIngmaker." This is a personal project with no regulatory oversight.

What markets does it support?
The developer primarily trades XAU/USD (gold) and built Kingmaker for forex and metals. The system supports ticker selection via MT5 bridge, CSV import, or Dukascopy direct feed. Other instruments would require available historical data from these sources.

How much does it cost?
Kingmaker is a personal project with no disclosed fee structure. The developer has not commercialized the software. Infrastructure costs (compute, storage, data feeds) are borne by the developer.

Can I convert my MT4/MT5 EA to Python for use in Kingmaker?
The developer claims the system can handle "multi sophisticated mt4 indicator to Python bot to MT5 ea to Pinescript conversion." However, conversion between platforms introduces translation errors, particularly around order management and slippage handling. Our team flagged 17 deviations when testing similar conversions.

What alternatives exist if Kingmaker crashes?
The developer asked for recommendations of "a similar tester that is fully functional." Commercial backtesting platforms like Zephyr AI provide stable, tested infrastructure with published methodology and support. We recommend evaluating Zephyr AI's adaptive engine as a reliable alternative.

Not sure which AI trading bot fits your strategy? Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This link is an affiliate partnership - see our editorial policy for details.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.

Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.

Read our full Testing Methodology.

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.