Bybit native bots vs running my own through their api(3 month writeup)
u/unratec ·
Reddit — r/algotrading
· May 04, 2026 at 19:48
· ⬆ 15 pts
· 💬 10 comments
| View on Reddit ↗
AI Summary
Summary
The author compares Bybit’s native trading bots (grid, DCA) with custom strategies run via Bybit’s API over 90 days.
Thesis: Native bots are convenient but deliver mediocre returns (+2.8%), while custom strategies (mean reversion, funding rate harvesting) outperform (+6.1% and +3.4%), but require dev work.
Quality assessment: Decent personal DD with quantified results and honest discussion of risks (patch errors, native bot limitations); not speculative, but limited to one exchange and small capital ($10k).
Score15
Comments10
Upvote %100%
▶ Full Post Text
Spent the last quarter running bybit's native bots (grid, dca, futures) on one side and my own custom strategies through the api on the other.
Figured i'd share since every "bot review" on this sub is either obvious marketing or someone who deployed once and ragequit after their first grid took a loss.
Setup was simple. Split 10k in half.
5k went to native bots, 3 grids and a dca, all picked from defaults with light tweaking on ranges. Other 5k went to two strategies i'd backtested earlier, a mean reversion on liquid alts and a funding rate harvest thing. Ran both sides 90 days, mostly through that nasty chop in march and the trend in early april.
Native side first.
Grids did what grids do.
Made a little when price stayed in range, gave it back on breakouts. Net +2.8% across all three over 90 days. Nothing to write home about. The dca bot actually underperformed manual dca because the auto rebalance kicked in during a brief dip and locked me into a worse entry than i'd have done by hand. Shaved off 0.4%.
Annoying but small.
Setup was genuinely zero friction tho. Pick pair, set range, set grid count, deploy. No code, no infra, no problem. For someone who can't or won't write code that's a real product.
Custom side.
Mean reversion bot pulled +6.1%. Funding harvest got +3.4%, would've been more if i hadn't fucked up the position sizing logic in week 4 and had to patch it live, lost a few bps to that.
Both ran through bybit's api and tbh it surprised me how stable it was. Ws connection dropped twice in 90 days, reconnect logic caught it both times no issues.
Rest rate limits felt generous. Never came close to throttling even with both bots polling concurrently. Compared to binance api where the rate limits are tighter and the maintenance windows kill ws connections more often, bybit was the smoother dev experience by a noticeable margin.
So what.
The native bots aren't where alpha is. They're a product for people who want algo-style exposure without doing the dev work. As that they're fine.
If you're on this sub you're probably better off running your own through the api where you can build edges that aren't already commoditized into the native bot defaults.
Bybit's just decent infra for that.
Anyone here actually pushing real size through their api?
curious how it holds up when the load is higher than what my hobby setup is putting on it.