Open-source volume bots: free to download, not free to run
Search for a Solana volume bot and public repositories come up first, which is a reasonable signal about what people actually want: the code, so they can see what it does. That instinct is correct. What the repositories do not give you is the operational layer, and that layer is where most of the cost and nearly all of the failure lives.
What a public repository gives you
The transparency argument is real and worth taking seriously. You can read exactly what the code does with keys, verify that nothing is exfiltrated, and change the trading logic to suit you. No hosted service offers that, including this one. For anyone technically capable and suspicious by default, which is a sensible way to be in this market, that is a strong position.
What follows is not an argument that the repositories are bad. It is an inventory of what running one actually requires, because the gap between a working script and a working campaign is the entire product.
What is missing from the repository
| Requirement | Why it matters | Cost if skipped |
|---|---|---|
| Compute limit tuning | Padding raises fees, undershooting causes failures | Direct fee waste |
| Retry logic | Dropped transactions are normal on Solana | Volume shortfall |
| RPC capacity | Public endpoints rate-limit under load | Campaign stalls |
| Key management | Thousands of keypairs to hold safely | Total loss risk |
| Landed-swap accounting | Attempts are not results | You cannot tell if it worked |
| Program upgrades | DEX interfaces change | Silent breakage |
The retry row is worth quantifying. In our most recent block sample, 27.9% of all Solana transactions failed while still paying their fee, and DEX programs failed at several times that rate. A script without proper retry and accounting logic does not just lose those transactions, it cannot tell you it lost them. Figures and method on the measurement page.
RPC capacity deserves a specific warning. Public endpoints are rate-limited and a campaign of any size will hit those limits, at which point transactions stop going out and the campaign quietly does nothing. Paid RPC access is a real recurring cost that no repository README includes in its zero-dollar price.
How to judge a repository before running it
A concrete checklist, in the order worth doing it:
- Trace the keys. Search for every network call and confirm none carries key material. This is the check that matters most, because the worst outcome is exfiltration rather than inefficiency.
- Look for hardcoded recipients. A wallet address embedded in the code that receives a share of trades is a fee you did not agree to. It happens.
- Check the history. A single initial commit with thousands of lines and no subsequent activity is a poor sign, both for trust and for whether it still works.
- Check for program-version assumptions. If the code targets a DEX program interface that has since changed, it will fail in ways that look like bad luck.
- Devnet first, always. Throwaway keys, no real funds, verify behaviour, then decide.
Doing this properly takes a few focused hours if you read code comfortably. If you do not, the honest assessment is that you cannot audit the repository, and running unaudited code that handles keys is a worse risk than any fee comparison.
When open source is the right call
Stated plainly, since this site sells the alternative: if you are technically capable and running more than one campaign, self-hosting is likely cheaper and gives you more control. The service fee exists to cover the operational layer, and if you are willing to build and maintain that layer yourself, you should keep the fee.
Where a hosted service is genuinely better value is a single campaign, or a team without the engineering time to own the maintenance. The break-even is not about capability, it is about how many times you intend to do this.
What neither option changes is the underlying economics: measured failure rates, priority fee bidding, tips and rent apply identically whether you run the code or pay someone to. Those are in the cost breakdown, and the honest costing of "free" is in free volume bots.
The hosted comparison, including exactly what a service fee covers, is on the pricing page. The network cost that applies to self-hosted and hosted campaigns alike is measured on the Solana volume bot overview.
Venue coverage is the other thing to check before adopting a repository. Most public scripts target one integration, usually Raydium AMM v4 or a Jupiter swap, and quietly break when a token sits on the Pump.fun bonding curve, migrates to PumpSwap, or has its depth in Meteora DLMM or Orca Whirlpools. Adding a venue is not a config change; it is a new program interface, new account layouts and a new failure profile to test against.