PRODUCT PREVIEW — LIVE AT LAUNCH

The bot that trades
the exact signal you saw.

No interpretation gap, no missed fills at 3am. Autopilot mirrors the published signal one-to-one, so the public ledger and your results are the same numbers. This page is a preview of how it will be configured and constrained.

// not yet available — Autopilot ships after the engine passes validation and the genesis run
◈ Product preview — live at launch. The panels below are non-interactive mock-ups. No bot is running, no exchange is connected, and no execution statistics exist yet. Configuration values are shown to illustrate the controls you will have, not to report anything that has happened.
Safety first

The constraints matter more than the strategy.

Handing an automated system access to your exchange account is a serious decision, and most of the engineering here goes into limiting what the bot is capable of doing rather than expanding it. Every control below is enforced, not advisory.

Trade-only API keysWithdrawal permission is disabled at the exchange, not by us. Even a total compromise of our systems cannot move your funds off the exchange.
Kill switchOne tap flattens every open position and halts the bot immediately. It is the largest control on the screen, deliberately.
Paper modeRun the whole system against a simulated balance for as long as you like. There is no time limit and no nudging you towards live.
Semi-auto modeEvery trade waits for your one-tap confirmation. You keep automation of the tedious parts without surrendering the decision.
Hard position capThe bot cannot exceed your configured maximum concurrent positions, regardless of how many signals fire.
Leverage ceilingA cap you set that the bot cannot override, even when a signal specifies a higher maximum.
Pair blacklistName pairs the bot must never touch. Blacklist entries are checked before every order and cannot be bypassed by a signal.
Grade filterAccept only the signal grades you want. If you only want full-consensus setups, the bot ignores everything else.
Revoke at any timeThe key is yours. Delete it at the exchange and the bot loses all access instantly, with no involvement from us.
Defined risk per tradePosition size is derived from the distance to the published invalidation stop, so a wider stop means a smaller position, never a bigger loss.
Execution modes

Three settings. Start at the cautious end.

Most people should begin in paper mode, move to semi-auto once the behaviour is familiar, and only then consider full auto. Nothing in the product pushes you up this ladder faster than you want to go.

MODE 01 / PAPER

Simulated, indefinitely

The bot receives real signals and executes them against a simulated balance. You see exactly what it would have done, with no money at risk and no expiry on the trial.

MODE 02 / SEMI-AUTO

You confirm each trade

The bot prepares the complete order — size, stop, targets — and waits. Nothing is placed until you approve it. Automation handles the execution, you keep the judgement.

MODE 03 / FULL AUTO

Hands off, inside your limits

The bot runs the full lifecycle 24/7 within every constraint you configured. It can act without you, but it can never act outside the boundaries you set.

Configuration

Everything the bot may do, in one screen.

These are the controls, shown with example values. There is no hidden configuration and no setting that only support can change.

EXECUTION · LIMITS◈ PREVIEW
ModePaper / Semi-auto / Full auto
Risk per trade1.0 %
Max concurrent positions4
Leverage cap
Signal grades acceptedA + B
Pair blacklistyour list
LIFECYCLE · AUTOMATION◈ PREVIEW
Ladder entries across zone
Scale out at each target
Stop to breakeven at TP1
Trail stop after TP2
Exit on thesis-break alert
Weekend risk reduction
The lifecycle

What the bot actually does, in order.

Signal received and checked

Grade, pair and current exposure are validated against your limits. Anything outside them is skipped and logged with the reason, rather than silently dropped.

Position sized from the stop

Size is computed from your risk percentage and the distance to the published invalidation level — never from a fixed notional, which is how people accidentally take enormous risk on tight-stopped trades.

Entry laddered across the zone

Orders are placed across the published entry range rather than chasing a single price, which reduces the impact of a fast fill or a brief wick.

Risk removed early

The stop moves to breakeven once the first target is reached, converting an open risk into a free position. After the second target it trails.

Thesis-break exit

If the engine’s reason for the trade stops being true before the stop is hit, the bot can exit early rather than waiting to be stopped out on a setup that has already failed.

Everything logged

Order by order, with timestamps, fill prices and the signal each action belongs to. The log is yours to audit against the public ledger.

// execution log format — preview
TIME      SIGNAL      ACTION            STATUS
--:--:--  sig_…0044   BUY ladder 1/4    FILLED
--:--:--  sig_…0044   BUY ladder 2/4    FILLED
--:--:--  sig_…0044   SELL 25% @ TP1    FILLED
--:--:--  sig_…0044   MOVE STOP -> BE   CONFIRMED
--:--:--  sig_…0044   SELL 25% @ TP2    FILLED
--:--:--  sig_…0044   MOVE STOP -> trail CONFIRMED
--:--:--  —           HEARTBEAT · queue empty  OK

// timestamps blank: no bot has run
Execution fidelity

Your fills, measured against the public record.

A signal service can publish an excellent ledger while its subscribers get materially worse fills. Autopilot reports the gap rather than hoping you do not measure it — your realised prices are compared to the published plan on every trade.

◈ Sample layout — no execution data exists yet
—.–%
Fills matching ledger
within a stated price tolerance
—.–%
Average slippage
versus published entry
Signals executed
of those your filters accepted
Skipped, with reason
every skip logged, never silent

// deliberately blank — publishing an invented fidelity figure would defeat the point of the whole project

Connections

Where it will run.

EXCHANGES · AT LAUNCH● PLANNED
Major centralised venuestrade-only keys
Autopilot tier1 account
Desk tier3 accounts
Additional account$29/mo
Self-hosted executorDesk, or $499 add-on
ROADMAP · NOT BUILT◈ INTENTION ONLY
Non-custodial executionplanned
Wallet portfolio syncplanned
On-chain ledger anchoringplanned
DeFi data layerplanned

// roadmap items are stated intentions, not commitments, and are not included in any price

Autopilot FAQ

The things worth worrying about.

Can the bot withdraw my funds?

No. It uses trade-only API keys with withdrawal permission disabled at the exchange level. That restriction is enforced by your exchange, not by our code, which is what makes it worth relying on. You can revoke the key yourself at any time.

What happens if your servers go down mid-trade?

Stops and targets are resting orders at the exchange, not instructions held on our side waiting to be sent. If we disappear entirely, your risk is still defined and your exits are still in place.

Can I use my own bot instead?

Yes. The Operator tier delivers every signal as structured JSON via webhook plus Cornix-compatible formatting, so you can route signals into 3Commas, Cornix, or your own stack. Autopilot is only worth paying for if you want the execution handled.

Does the bot trade differently from the published signal?

No — that is the entire design constraint. It executes the published plan one-to-one, which is what makes comparing your fills to the public ledger meaningful. A bot allowed to improvise would make the ledger unfalsifiable.

Can I run it on my own server?

Yes, on the Desk tier or as an add-on. The self-hosted executor runs on your machine and your API keys never leave it.

When can I actually use this?

After the engine passes its validation gate and completes the public genesis run. We are not selling automated execution of a strategy that has not proven itself in the open first.

Risk disclosure: Automated trading carries substantial risk of loss, including risks specific to automation such as connectivity failure, exchange downtime, and unexpected market conditions. Autopilot executes only within configurations you control, and you remain responsible for those settings. This page is a product preview; no bot is currently available.
© 2026 Nen Algo · nenalgo.com Home · Terms · Privacy · Methodology · Verify · Ledger