How to choose a Solana volume bot
A five-stage selection method that starts with your own requirement rather than a feature list, and ends with a small paid test instead of a leap of faith.
01Criteria: what to measure in a volume bot
A criterion is only useful if you can check it. That single test removes most of what appears in a feature comparison and leaves nine properties that survive contact with a real purchase: who holds the keys, which venues are genuinely routed, what the whole price expression is, which parameters you control, what happens when a transaction fails, what you can export afterwards, how support behaves once you have paid, what the contract says, and whether the operation has any history at all.
This section defines those nine, explains how to check each one before money moves, and turns them into a shortlist filter rather than a rating. Nothing here scores a named product. The point is to leave you able to judge a tool this desk has never seen.
4 pieces in this section
The measurable properties of a volume tool: custody, venue coverage, control surface, failure reporting and the questions that expose each one.
The nine evaluation criteria
Nine properties you can actually check before paying, each with a scoring band, the evidence that satisfies it, and the answer that should end the conversation.
02Custodial vs non-custodial
Who holds the keys is the single largest structural difference between two tools that look identical in a screenshot. A custody model matrix and the questions that reveal it.
03Questions to ask a vendor
Thirty questions grouped by what they test, with the answer shape that passes, the answer shape that fails, and what a refusal to answer tells you.
04Where each criterion gets settled
Some criteria are settled by reading, some by asking, some only by running a small test. Knowing which is which stops you spending a test budget on a question a document could have answered.
| Code | Criterion | Settled by | Covered in |
|---|---|---|---|
| C1 | Custody model | Documentation plus an on-chain check | Custodial vs non-custodial |
| C2 | Venue coverage | A demonstration, then a test run | How to choose a Solana volume bot |
| C3 | Pricing structure | A written price expression | Pricing models compared |
| C4 | Control surface | The interface itself, before payment | Telegram bot vs web console |
| C5 | Failure reporting | A test run reconciled against the chain | Running a small controlled test |
| C6 | Observability | An export you actually download | Running a small controlled test |
| C7 | Support behaviour | The pre-sales conversation | Questions to ask a vendor |
| C8 | Contract terms | The written terms, read in full | Red flags before you pay |
| C9 | Operational maturity | Public history and change records | The nine evaluation criteria |
Where this section sits
Criteria tell you what to measure. The other two sections tell you how classes of tool differ once you start measuring, and what to do in the days between a shortlist and a payment.
Comparisons
Class-level comparisons rather than product rankings. Pricing structures, interface models and hosting models, each with the trade-off it hides.
COMBuying guide
What to do between shortlisting and paying: size a first budget, run a controlled test, and check the warning signs that predate most complaints.
BUY