Pionex and Tradevo: fewer parties, or fewer things one party controls
Pionex takes an approach worth taking seriously: instead of connecting an outside bot to your exchange account, the bots live inside the exchange. There is no API key to issue, no third-party service holding a credential, and nothing to configure between two systems.
That genuinely removes a party from the chain. It is also the strongest argument for looking closely at what the remaining party can do, because it is now doing everything.
We build Tradevo, so read accordingly. This page compares custody and control, and says where Pionex is the better choice.
How each one is wired
Pionex is a centralised exchange with automation built in. You deposit, pick from its set of built-in bots — grid, dollar-cost averaging, rebalancing and others — set parameters, and it runs on your balance inside the venue. No outside service is involved, because the venue is the service. Your assets are held by Pionex, as they are on any centralised exchange.
Tradevo separates those roles. The wallet is yours — you hold the keys — and it sits on Base, a network nobody in this comparison operates. What we hold is a scoped signing authorisation: a delegated session signer attached to your embedded wallet, governed by a policy we define, with a single job — swapping allowlisted assets within your allocation. It does not transfer, does not withdraw, and does not reach anything you did not allocate — limits kept by our executor rather than by the chain or by the signing provider, whose policy cannot restrict the method this flow signs with. There is no per-swap commission on the free tier and gas is sponsored, so the wallet never has to hold the network's native token; Pro is $14.99 a month.
The trade is not "fewer parties is safer"
Counting parties is a useful habit, but the count alone does not tell you much. What matters is how much each one controls.
Connecting a third-party bot to an exchange gives you two parties: the venue holds the assets, and the operator holds a key that can trade them. The operator's power is bounded by what you granted, and you can withdraw that grant yourself.
Putting the bots inside the exchange collapses that to one party — and that party holds the assets, runs the automation, operates the matching engine, and sets the prices your bot trades at. There is no separation between the entity holding your balance and the entity deciding what happens to it. Nothing about that is an accusation; it is the structure, and it is the structure of every exchange with built-in automation.
The on-chain model makes a different trade. There is still one party, but it does not hold the assets, cannot move them anywhere except a swap you authorised, and executes on a venue it does not operate. Fewer powers concentrated, rather than fewer names in the list.
Side by side
| Pionex | Tradevo | |
|---|---|---|
| Where the assets sit | Held by Pionex | A wallet whose keys you hold |
| Who runs the automation | Pionex | Us |
| Who operates the venue | Pionex | Base, which nobody here operates |
| Parties in the chain | One, holding everything | One, holding a scoped authorisation |
| What that party cannot do | It is the custodian — the limits are its own | Withdraw, transfer, or touch unallocated funds |
| Bots available | A set of built-in bots, no coding | A curated list with a published admission bar |
| Cost of automation | Bots are free to use; trading fees apply | No commission per swap on the free tier, gas sponsored |
| Stopping it | Stop the bot; withdraw to leave entirely | Cancel; execution halts and Tradevo removes its signer, best-effort |
| Verifying execution | The venue's own records | Public transactions on Base |
Pionex details are from its own published descriptions, linked below. Check the current specifics yourself — fee schedules and bot line-ups change.
The part that is genuinely hard to beat
Pionex's built-in bots are free to use and require no setup between systems. For someone who wants scheduled buying or a grid running without learning anything about keys, permissions or wallets, that is a real advantage and no amount of architecture argument makes it go away. Simplicity is a feature, and most automation failures are configuration failures.
It is also worth saying plainly that a venue running your bot on its own book is not inherently worse than a third party running it over an API. It is a different distribution of trust, not a larger amount of it.
When Pionex is the better choice
You want the simplest possible setup. One account, no keys, no wallet, no bridge between two systems. If that is what you are optimising for, this is the shortest path and we are not it.
You want to trade what a centralised venue lists. Pairs with no meaningful on-chain market are out of reach for an on-chain executor. Architecture does not create liquidity.
You want to leave in one action. Withdrawing from an exchange ends the relationship without needing anyone's cooperation. Cancelling stops the strategy immediately; our signer is then removed by us, best-effort, rather than by something you trigger. You can export your wallet at any time, which leaves us zero residual access — but that is an exit, not an off-switch — so if a unilateral exit is your priority, note the difference. We think an account-level permission a user can disable on-chain without the operator is where this ought to end up. It is not where we are today.
You want order types that need a matching engine. Resting limit orders deep in the book and complex conditionals belong where the book is.
You already keep assets on an exchange deliberately. If that is a considered decision, adding self-custody purely for the automation layer buys less than it costs in complexity.
When the on-chain model fits better
You object to the venue holding the assets at all. This is the case it exists for, and no bot design inside an exchange addresses it.
You want the automation's powers bounded in writing. An allowlist and a cap are narrower than "this account". They are applied by our executor before anything is signed, which is a narrower promise than an unbounded key — but it is still our promise, not the chain's enforcement. They are not enforced by the chain itself.
You want to audit execution independently. Every swap is a public transaction you can check without asking us or anyone else for a record.
You want a published admission bar. Validated strategies — the ones that show backtest results — are listed only after multi-year backtests, out-of-sample windows and walk-forward analysis; a small set of experimental strategies is listed with a clear NOT BACKTESTED label and no performance history. Once tracked, a strategy's forward record is written daily against real prices from the date tracking began and is never edited.
Check for yourself: Pionex · Tradevo's method
Tradevo Technologies builds evidence infrastructure for systematic trading. Nothing on this page is investment advice, and no part of it describes how any strategy performed. Crypto assets are volatile and you can lose your entire allocation.