Docs / Signal Engine / Engine Builder

Building a custom trading engine

Signal Engine · Trader tier · 8 min read

The default signal engine is one opinion about how momentum, structure, volume, funding and macro bias should be weighted. The Engine Builder lets you write your own -- and once saved, it runs as a fully automated custom bot through Auto-Trade.

AEON Engine Builder panel showing a custom weighted checklist with gates and total weight
A custom engine mid-build: checks weighted, one marked as a required gate

Why build a custom engine

AEON's default signal engine blends momentum, structure, volume, funding and macro (DXY) bias into a single conviction score using its own internal weighting. That's a reasonable general-purpose default -- but it's still one opinion. If you trade a specific style -- pure momentum breakouts, mean-reversion only, structure-first with everything else as confirmation -- a custom engine lets you rebuild the scoring logic around what you actually trade, instead of working around a one-size-fits-all default.

This is, functionally, building your own custom trading bot: define the logic once, save it, and let Auto-Trade execute it without you re-checking every setup by hand.

Two engine types: Confluence and Pattern

Confluence

A weighted checklist. Every check contributes a weight toward total conviction, and any check can be flagged as a required gate -- a condition that must pass regardless of overall score before a signal fires at all.

Pattern

A leg/state-based sequence a market has to move through (think: a structural pattern unfolding over several swings) rather than a static snapshot. Once detected, the same weighted checklist grades the setup's quality.

Most traders start with Confluence -- it's the more direct translation of "here's what I look for and how much each thing matters." Pattern is for setups defined by sequence and structure rather than a single-point checklist.

Checks, gates and weights

Each check in the builder -- individually or grouped into a family like Bias or Timeframe Alignment -- has three controls: an on/off toggle, a weight (how much it contributes to the total conviction score), and a gate switch. A gated check isn't just weighted in -- if it fails, the engine won't fire a signal at all, no matter how high everything else scores. This is how you encode a hard rule ("never signal against higher-timeframe trend") rather than a soft preference.

The footer tracks three running totals as you build: how many checks are currently active, how many are set as required gates, and the combined total weight -- so you can see at a glance whether your engine leans on a couple of hard rules or a broad, evenly-weighted blend.

Custom trade management (optional)

Beyond the checklist, you can define your own entry, take-profit, stop-loss and trailing-stop formulas -- each with a separate version for long and short. This is entirely optional: leave it blank and the engine falls back to AEON's default ATR-based stop and target logic. Define it and your custom bot manages exits exactly the way you specify, not just the way it decides to enter.

Running your engine as a custom bot

Once an engine is saved, it appears as a selectable option in Auto-Trade alongside the built-in presets. Switching to it hands execution over to your own weighted logic and trade-management rules end to end -- Auto-Trade watches the market, evaluates your custom checklist, and executes entries and exits according to your engine rather than the default signal score. That's the whole point of building one: a custom bot that trades your rules, unattended.

Exporting, importing and sharing engines

Any saved engine can be exported as a single JSON file -- or you can export every saved engine at once as a bundle. Import an engine file someone else shares with you the same way, in seconds, without rebuilding it check by check. Custom engines can also be listed on AEON's Engine Market, where other users can pick up ready-made bot configurations instead of starting from a blank builder.

Not sure where to start weighting checks? Read how the default signal score works first -- it's the baseline every custom engine is built to improve on for your specific style.

A custom engine only encodes the rules you give it. Backtest and paper-trade any new configuration before connecting it to live Auto-Trade execution, and revisit weights periodically -- market conditions that justified a given weighting can shift.