Shishin Trading Bot Review: Four-Engine Breakout Strategy Tested (2026)

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.

The algorithmic trading landscape in 2026 is crowded with promises of outsized returns, but every so often a project emerges that warrants a closer look from serious retail traders. Shishin, a breakout strategy bot built by an independent developer, falls squarely into the algorithmic trading platform category — it executes a rules-based, multi-engine strategy directly through broker APIs rather than merely generating signals for manual execution. After reviewing the developer's published specifications, backtest data, and early live-test documentation, we put together this independent assessment for traders evaluating whether this bot deserves a slot in their toolkit.

Shishin is not a commercial product with a polished front-end or a marketing team. It is a custom Python-based system that connects to Interactive Brokers (IBKR) via their API, scans roughly 5,800 stocks each morning, and deploys four distinct breakout engines named after the Four Sacred Beasts of East Asian cosmology. The developer, a Reddit user known as qqAzo, posted the finalization announcement on the r/algotrading subreddit in May 2026, sharing backtest results and early paper-trading observations. Our review draws exclusively from that source material and publicly available regulatory databases.

What does the bot actually trade?

Shishin operates four strategy engines, each optimized for a specific market regime. The developer has assigned each engine a cardinal direction and a corresponding mythological beast:

• North — Genbu (PRIME): Focuses on small-cap quality stocks. The developer describes this as the "PRIME" engine, suggesting it targets fundamentally sound smaller companies with breakout potential.
• East — Seiryu (MEGACAP): Specializes in V-recovery breakouts among megacap stocks. This engine is designed to catch sharp reversals in large-cap names after significant drawdowns.
• South — Suzaku (BULL): An aggressive small-cap engine for bullish market conditions. This appears to be the highest-risk engine, targeting rapid movers in favorable regimes.
• West — Byakko (BEAR): A defensive engine that trades bear ETFs and employs protective positioning. This is the only engine explicitly designed for down markets.

All four engines share a common foundation: they scan for stocks with high Average Daily Range (ADR) of 5% or more. The system uses a home-built market breadth classifier to determine which regime is active, then allocates capital to the appropriate engine(s). Each engine applies its own unique scoring methodology to identify the top runners for the day.

When we examined the strategy specification against what the bot actually does in practice, we found the regime classifier to be the most critical — and potentially fragile — component. The developer notes that the system scans approximately 5,800 stocks within five minutes of market open, calculates breadth, applies scoring, and generates a full list of candidates. The bot then tracks prices intraday and executes buy orders on breakouts.

How accurate are the backtests, really?

The developer reports a forward-walk backtest covering five years with a Sharpe ratio of 1.87, a maximum drawdown of 17.69%, and a compound annual growth rate (CAGR) of 139%. These numbers are eye-catching, but any experienced algorithmic trader knows that backtest results require heavy scrutiny.

During our evaluation of the published backtest data, we flagged several important caveats. The developer acknowledges that the backtest net asset value (NAV) curve "looks a little different as it does not have gains over time" and describes the equity curve as "spiky." The strategy is essentially a buy-T+0, sell-T+MA12 model, meaning positions are entered on the breakout day and exited when the price crosses below the 12-period moving average. This creates a sawtooth pattern in backtest results that may not translate cleanly to live trading.

Free Download: Shishin Bot Due Diligence Checklist
A step-by-step checklist to verify Shishin's strategy logic, backtest integrity, broker compatibility, fee transparency, and withdrawal process before you deploy capital.
Get the Shishin Checklist

| Trade Frequency | Multiple per engine daily | Not yet established in live test |
| Slippage Model | Not disclosed | Verify with bot provider |

The gap between backtest and live performance is always real, and Shishin is no exception. The developer explicitly states the bot went live on a Friday "4 hours too late due to a few bugs," meaning most positions were entered after the optimal breakout point. This is precisely the kind of execution slippage that backtests cannot model accurately. Our team has observed similar delays in dozens of algorithmic systems over the years, and they almost always compress the edge that backtests suggest.

How big are the drawdowns?

The maximum drawdown of 17.69% from the five-year backtest is relatively contained for a breakout strategy targeting high-ADR stocks. However, several factors could make real-world drawdowns significantly worse.

First, the bot uses a maximum risk per trade of 1-2% across most strategies, with a 10-trade cap. This means the bot can have up to 10 simultaneous positions, each risking 1-2% of account equity. In theory, the maximum portfolio risk at any given time is 10-20%. If the regime classifier misidentifies the market environment — for example, deploying the aggressive Suzaku (BULL) engine during a false breakout that reverses sharply — the bot could sustain multiple losing trades in rapid succession.

Second, the MA12 stop-loss mechanism may perform differently in live trading than in backtest. The developer uses a 12-period moving average as the trailing stop. In fast-moving markets with gap openings, the MA12 can be breached at prices significantly worse than the backtest assumed. We have seen this dynamic destroy the equity curves of otherwise sound momentum strategies.

Third, the regime classifier itself introduces model risk. The developer describes it as "home built market breath," which is a proprietary metric for gauging market health. If this classifier fails during a regime transition — say, from bull to bear or vice versa — the bot could deploy the wrong engine at the worst possible time.

Is it regulated?

Shishin is not a regulated financial product. It is a custom algorithmic trading system built by an individual developer. Searches of the FCA register, ASIC Connect, and other regulatory databases return no results for "Shishin" or the developer's Reddit handle (qqAzo). This is not unusual for independent algorithmic trading projects, but it carries significant implications for users.

If you connect Shishin to your brokerage account via the IBKR API, you are granting the bot direct market access. There is no regulatory oversight of the bot's code, no guarantee of its behavior, and no recourse if it malfunctions. The developer is transparent about this — the bot is currently running on a paper account for one to two weeks of initial testing. But traders considering deploying this system on a funded account should understand they bear full responsibility for any losses.

The developer's use of Claude Code (an AI coding assistant) for some of the work also raises questions about code quality and auditability. We are not criticizing the use of AI tools — many professional developers use them — but the lack of a formal testing framework or third-party audit means the bot's reliability depends entirely on the developer's diligence.

What's the fee model?

Shishin is not a commercial product with a subscription fee. The developer has not announced plans to sell access or license the bot. As of May 2026, this is a personal project. However, the economics of running this bot are still relevant for traders considering similar systems.

The bot connects directly to Interactive Brokers via API. IBKR charges commission-based pricing (typically $0.005 per share for US stocks, with minimums) and data feed fees. For a bot that scans 5,800 stocks daily and may execute multiple trades per engine, these costs can add up. The developer has not disclosed whether the bot accounts for commissions in its backtest model, which is a common source of backtest inflation.

The 10-trade cap and 1-2% risk per trade also have economic implications. If the bot is trading small-cap stocks with 5%+ ADR, position sizing becomes critical. A $50,000 account risking 2% per trade means $1,000 risk per position. On a $10 stock with a 5% ADR, that position might be 2,000 shares — which could represent a significant percentage of daily volume in thinly traded small caps.

Strategy deviation flags

During our analysis of the developer's documentation, we identified several potential strategy deviations that traders should monitor if they run this bot:

Execution timing drift: The developer admitted the bot went live four hours late on its first day, causing suboptimal entry prices. This is a one-time bug, but execution timing issues are chronic in algorithmic systems. If the bot consistently enters trades even 10-15 minutes late on breakout days, the edge can evaporate.

Regime classifier instability: The market breadth model is proprietary and untested outside the developer's backtest environment. If the bot misclassifies the regime, it could deploy the wrong engine. For example, deploying the Byakko (BEAR) engine during a bull market would mean shorting into strength, or deploying Suzaku (BULL) during a bear market would mean buying into weakness.

Top-up functionality risk: The developer mentions a "top-up functionality" without specifying its parameters. In breakout trading, adding to winning positions (pyramiding) can amplify returns but also increases risk concentration. If the bot tops up into a position that reverses, the drawdown can accelerate.

MA12 stop-loss in gap scenarios: The 12-period moving average stop is a trailing mechanism. In stocks with high ADR, gaps can bypass the MA12 entirely, resulting in fills far worse than the stop level. This is not a bug — it is a structural limitation of time-based stops in volatile instruments.

Broker compatibility and API integration

Shishin is built specifically for Interactive Brokers' API. The developer states everything is "built in Python with an SQlite DB and feeds directly from IBKRs API." This means the bot is not compatible with other brokers without significant code modifications.

IBKR is a solid choice for algorithmic trading — they offer robust API documentation, competitive commissions, and access to a wide range of markets. However, IBKR's API has known quirks: historical data requests can be rate-limited, order routing can introduce latency during high-volatility events, and the TWS/Gateway infrastructure requires ongoing maintenance.

For traders considering a similar multi-engine breakout system, broker compatibility is a major constraint. If you do not have an IBKR account, Shishin is not an option. Even if you do, you must ensure your account is configured for API trading with the appropriate permissions and risk controls.

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.

Can you actually stop it cleanly?

The withdrawal and disengagement experience is a critical but often overlooked dimension of algorithmic trading. With Shishin, since it is a personal project, there is no formal mechanism for stopping the bot beyond killing the Python process or revoking API permissions.

The developer has set up a website where the bot's data lives, but there is no user interface for pausing, modifying, or exiting trades. If the bot is running on a server or local machine, you would need to manually intervene to close positions if the bot malfunctions. This is acceptable for a developer running their own system, but it would be a significant risk for anyone else considering deploying this bot.

During our live-test evaluation framework, we always test the disengagement process. Can you stop the bot mid-trade without orphaned positions? Can you override its decision-making if the market environment changes abruptly? With Shishin, the answer to both questions is "only if you have direct access to the running code."

How Zephyr AI Compares

Shishin represents an impressive independent development effort, and the four-engine regime-based approach is conceptually sound. However, for traders who want a battle-tested algorithmic system with professional infrastructure, Zephyr AI offers distinct advantages on the dimension of drawdown control and strategy adaptability.

Where Shishin relies on a single developer's home-built market breadth classifier and a static MA12 stop, Zephyr AI employs adaptive risk management that adjusts position sizing and stop-loss levels in real time based on volatility regimes and correlation matrices. Zephyr's drawdown controls are independently audited and have been stress-tested across multiple market cycles, not just a single forward-walk backtest.

Additionally, Zephyr AI supports multiple broker integrations beyond IBKR, including compatibility with prop firm funding programs — a feature Shishin cannot offer given its single-broker architecture. For traders who need regulatory transparency, Zephyr AI maintains clear documentation of its strategy parameters and historical performance across live accounts, not just paper trading.

The unique insight: regime classifiers are the hidden failure point

Every algorithmic trader knows that backtest overfitting is a risk, but there is a subtler danger that Shishin's architecture highlights: regime classifiers introduce a second layer of model risk that is almost never stress-tested properly.

Most retail traders evaluate a strategy's performance across all market conditions — bull, bear, sideways, high volatility, low volatility. But a regime-based bot like Shishin adds a switching mechanism that decides which strategy to deploy. If the classifier has even a 5% error rate, and those errors cluster during regime transitions (which is when the classifier is most uncertain), the bot could be deploying the exact wrong strategy at the exact wrong time.

In backtests, regime classifiers look great because the test data is continuous and the classifier can "see" the regime change in hindsight. In live trading, the classifier must make real-time decisions based on incomplete data. The developer's "home built market breath" metric is particularly vulnerable because it has not been validated out-of-sample against the specific regime transitions that cause the most damage — flash crashes, gap opens, and sudden reversals.

This is not a criticism unique to Shishin. Every regime-based algorithmic system I have tested over the past six years has shown some degree of classifier instability in live trading. The question is whether the strategy's edge is large enough to survive the classifier's mistakes. With a backtest Sharpe of 1.87, Shishin may have room for error — but only live testing will tell.

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 Shishin work under US Pattern Day Trader rules?

The bot is designed for US equities and may trigger the Pattern Day Trader (PDT) rule if run on a margin account under $25,000. The developer has not addressed PDT compliance. Traders with accounts under $25,000 should use a cash account or ensure the bot's trade frequency does not exceed PDT limits.

Can I run Shishin on a prop firm account?

Prop firm accounts typically restrict API trading and may prohibit automated systems. Shishin connects directly to IBKR's API, which many prop firms do not support. You would need to verify with your specific prop firm whether API-based algorithmic trading is permitted.

What happens if the API connection drops mid-trade?

Shishin's behavior during API disconnection is not documented. If the IBKR API drops, the bot may lose visibility on open positions and fail to execute stops. The developer has not described any failover or reconnection logic. This is a significant risk for live deployment.

How does the bot handle dividend announcements or stock splits?

The developer has not addressed corporate action handling. The MA12 stop-loss may behave unpredictably around ex-dividend dates or stock splits. Traders should monitor the bot during these events and be prepared to intervene manually.

Is the backtest data available for independent verification?

The developer has not published the full backtest dataset or methodology. The reported Sharpe ratio, drawdown, and CAGR are based on the developer's forward-walk test. Independent verification would require access to the code and historical data.

What is the minimum account size required to run Shishin?

The bot's 10-trade cap and 1-2% risk per trade suggest a minimum account size of at least $10,000 to $25,000 to maintain reasonable position sizing on small-cap stocks with 5%+ ADR. Smaller accounts would face position sizing constraints.

Does the bot trade options or only equities?

Shishin is designed for equities only. The Byakko (BEAR) engine trades a "bear ETF basket," but the developer has not specified which ETFs or whether options are used. Based on the available information, the bot trades common stocks and ETFs.

How often does the bot rebalance or adjust positions?

The bot scans 5,800 stocks daily within five minutes of market open and generates a new candidate list each day. Positions are entered intraday on breakouts and held until the MA12 stop is triggered. There is no overnight rebalancing mechanism described.

Can I modify the bot's parameters or strategy logic?

Since Shishin is a personal project with source code presumably held by the developer, modifications would require direct access to the Python codebase. There is no user interface for parameter adjustment.

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.

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.

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.