ORACLEOperator Kits

ORACLE // operator-grade planning kits

Plan the bot.
Run the ops.
Respect the risk.

ORACLE Operator Kits are spec-first digital planning packs for retail algo trading experiments, MetaTrader 5 EA builds, and VPS bot operations. No signals, no promised returns — just the documentation discipline that keeps an operator's automation accountable.

Browse kitsSystem statusClaim downloads

Operator kits

Live catalog served by the Shopify Storefront API.

Home page
Shopify product

Retail Algo Trader Starter Kit

£29

This kit is a set of working documents for running retail algo-trading experiments in an orderly way: write the strategy down first, test it on paper and on demo, keep a journal, and put hard limits around anything you automate. It does not tell you what to trade and it does not predict results. It gives you structure, which is the part most people skip. What's inside Strategy specification worksheet. Before any code, write the strategy as rules a stranger could follow: instrument, timeframe, entry conditions, exit conditions, position sizing, and the conditions under which you stop trading it. Backtest review template. For each backtest, record the data range, spread and commission assumptions, parameter values, trade count, drawdown and net result — plus an honest note on what you changed since the last run. Demo challenge tracker. Run the strategy on a demo account for a fixed period before any real money. Trading journal (template.csv). One row per trade: date, instrument, direction, entry, exit, size, planned risk, result, setup tag, and whether you followed the plan. Bot risk-control checklist. Hard limits, written down before the bot runs: maximum loss per day, maximum position size, maximum open positions, and the exact conditions under which you shut it off. Daily bot report. A short end-of-day record: did the bot run, what did it do, any errors, any manual interventions. Weekly review worksheet. A fixed set of questions to answer from the journal at the same time every week, process before results. Platform planning worksheets. Two planning worksheets — one for MT5 Expert Advisors, one for OANDA/Python bots — covering account setup, API access, environment, and what to verify before the first automated order. Prompt pack. Prompts for using an AI assistant to review your strategy spec, your backtest notes and your code. Who it's for Retail traders moving from manual trading to systematic and automated experiments. Not a fit if you want to be told what to trade. Every document in the kit is about process and record-keeping; the strategy and the work are yours to supply. What you download Seven files, delivered as a digital download after checkout: guide.md — the full written guide; opens in any text editor. printable.html — the checklist and worksheet, formatted for printing. checklist.csv — the working checklist as a spreadsheet. template.csv — trading journal: one row per trade. prompt_pack.md — prompts for having an AI assistant review your work. disclaimer.md — the disclaimer as a standalone file. cover.svg — the kit cover image. No broker or platform account is needed to use the documents, nothing physical ships, and there is no subscription. What this is not It is not a trading strategy, not software, and not advice. It will not tell you what to buy or sell. Disclaimer This kit is educational material: planning templates, checklists and worksheets for organising your own work. It is not financial advice, not a recommendation to trade any instrument, and not a prediction of results. Trading carries a substantial risk of loss, and running automated systems adds technical risk on top of market risk. Only use money you can afford to lose, and if you need advice, speak to a regulated professional. You are responsible for your own decisions.

Inspect kitCheckout ready
Shopify product

MT5 EA Builder Planning Pack

£24

This pack is a spec-first workflow for building MetaTrader 5 Expert Advisors: define the strategy on paper, plan entries, exits and risk handling before writing MQL5, then log optimization and walk-forward runs so you can tell a robust result from a curve-fit one. It is planning material, not a strategy and not code. What's inside EA strategy specification. A structured spec for the EA before any MQL5 exists: market, timeframe, signal logic in plain language, order types, and every input parameter with its allowed range. Entry/exit worksheet. Work through every path a trade can take: normal entry, normal exit, stop, partial close, end-of-session handling, and behaviour around news gaps or requotes. Risk management worksheet. Position sizing method, maximum exposure, per-trade and per-day loss limits, and how the EA behaves when a limit is hit. Optimization log (template.csv). One row per optimization or backtest run: parameter set, data range, cost model, trade count, drawdown, result and a verdict. Walk-forward tracker. Split your data, optimize on one segment, test on the next, and record both. Bug report template. A consistent format for EA defects: expected behaviour, actual behaviour, chart/timeframe/build, reproduction steps and severity. Release checklist. The steps between 'backtest looks fine' and 'running on a live account': demo period, error handling review, logging, VPS deployment, rollback plan. MQL5 prompt pack. Prompts for using an AI coding assistant on MQL5 work: translating your spec into a code skeleton, reviewing error handling, and hunting for code that only works in the Strategy Tester. Who it's for Traders and developers building or commissioning MetaTrader 5 Expert Advisors. Not a fit if you want to be told what to trade. Every document in the kit is about process and record-keeping; the strategy and the work are yours to supply. What you download Seven files, delivered as a digital download after checkout: guide.md — the full written guide; opens in any text editor. printable.html — the checklist and worksheet, formatted for printing. checklist.csv — the working checklist as a spreadsheet. template.csv — optimization log: one row per backtest or optimization run. prompt_pack.md — prompts for having an AI assistant review your work. disclaimer.md — the disclaimer as a standalone file. cover.svg — the kit cover image. No broker or platform account is needed to use the documents, nothing physical ships, and there is no subscription. What this is not It is not a trading strategy, not software, and not advice. It will not tell you what to buy or sell. Disclaimer This kit is educational material: planning templates, checklists and worksheets for organising your own work. It is not financial advice, not a recommendation to trade any instrument, and not a prediction of results. Trading carries a substantial risk of loss, and running automated systems adds technical risk on top of market risk. Only use money you can afford to lose, and if you need advice, speak to a regulated professional. You are responsible for your own decisions.

Inspect kitCheckout ready
Shopify product

VPS Bot Operator Kit

£19

This kit covers the unglamorous part of running trading bots: the server. Provisioning, hardening, monitoring, alerting, backups and incident response for a VPS that has to stay up while you're asleep. Nothing in it is about trading decisions — it's about not being the person whose bot died on Tuesday and who found out on Friday. What's inside Provisioning checklist. Choosing and setting up the VPS: region close to your broker, adequate RAM for your platform, a non-root user, SSH keys instead of passwords, and a written record of what you installed and why. Hardening checklist (UFW / fail2ban). Close everything you don't use. Uptime and process monitoring. Cron and systemd templates for watching the things that matter: is the bot process alive, is the platform connected, is the disk filling up. Alerting (Telegram templates). Message templates for the alerts worth waking up for — process down, connection lost, disk critical — and the ones that can wait for morning. Incident response sheet. A fill-in sheet for when something breaks: what you observed, when, what you did, what the root cause was, and what changes so it doesn't repeat. Backup checklist. What to back up (configs, bot code, logs, platform profiles), where to keep it (off the VPS), and — the part everyone skips — a scheduled test that the backup actually restores. Daily ops report (template.csv). One row per day: host up, processes up, disk, load, last backup, alerts fired, actions taken. Who it's for Anyone running trading bots or Expert Advisors 24/7 on a VPS. Not a fit if you want to be told what to trade. Every document in the kit is about process and record-keeping; the strategy and the work are yours to supply. What you download Seven files, delivered as a digital download after checkout: guide.md — the full written guide; opens in any text editor. printable.html — the checklist and worksheet, formatted for printing. checklist.csv — the working checklist as a spreadsheet. template.csv — daily ops report: one row per day. prompt_pack.md — prompts for having an AI assistant review your work. disclaimer.md — the disclaimer as a standalone file. cover.svg — the kit cover image. No broker or platform account is needed to use the documents, nothing physical ships, and there is no subscription. What this is not It is not a trading strategy, not software, and not advice. It will not tell you what to buy or sell. Disclaimer This kit is educational material: planning templates, checklists and worksheets for organising your own work. It is not financial advice, not a recommendation to trade any instrument, and not a prediction of results. Trading carries a substantial risk of loss, and running automated systems adds technical risk on top of market risk. Only use money you can afford to lose, and if you need advice, speak to a regulated professional. You are responsible for your own decisions.

Inspect kitCheckout ready

Why these kits exist

Most retail automation dies from missing process, not missing code. ORACLE kits package the unglamorous parts — specs, journals, checklists, incident plans — that keep an operator honest.

Spec before build

A strategy or EA that exists only in your head cannot be tested, reviewed, or killed cleanly. Every kit starts from a written specification so the idea is falsifiable before money or compute is committed.

Operations as a discipline

Bots fail at 3am, VPS hosts reboot, and brokers disconnect. Provisioning checklists, hardening steps, monitoring logs, and incident templates turn those events into procedure instead of panic.

Risk stays in frame

Kill criteria, drawdown limits, and review cadences are written down before the first order is placed. If a rule is not on paper, it does not exist when you need it.

Risk disclosure

ORACLE Operator Kits are educational planning materials only. Nothing on this site is financial advice, an investment recommendation, or a promise of returns. Trading and automated trading involve substantial risk, including the loss of all capital. Automation adds operational risk of its own — test on demo accounts and never run capital you cannot afford to lose.