Passivbot vs Vesper: compare the strategy before the interface

SypherScore operates Vesper. This is a disclosed vendor comparison, not an independent recommendation or an audited performance benchmark. We have not run a matched, version-controlled profitability trial between these products.

The official Passivbot repository, checked 26 September 2026, describes a Python-and-Rust perpetual trading bot with backtesting and optimisation. Its current documentation names trailing_martingale as the default engine, also documents ema_anchor, and treats trailing_grid_v7 as a compatibility path. The repository uses the Unlicense.

That version context matters. Do not reduce every Passivbot setup to one historic grid description or treat an old backtest as evidence for a newer engine. Record the exact release, configuration and data before making comparisons.

The documented default trailing_martingale approach can add exposure after adverse price movement, subject to its configured limits. That is a strategy choice with inventory and drawdown implications, not evidence that every configuration must fail. Consult the engine documentation for the version you actually use.

For Vesper, read the selected mode's guide rather than assuming a single portfolio policy applies to every strategy. EXITE is an Entropy mode whose entry gate can leave it waiting between opportunities. Waiting is not a promise of lower loss, and an intended short holding period is not a guaranteed exit deadline.

Ask the same concrete questions of either system: can exposure increase after an adverse move, what bounds total inventory, how is a partial fill handled, and what happens if an exit is rejected? A limit order that never fills is not protection against every market move.

An open-source deployment is useful when you want to inspect, change and version the strategy yourself. A hosted desk is useful when the offered mode fits and you do not want to operate that deployment. Neither choice removes the need for monitoring or understanding leveraged positions.

A free software licence is only one part of the bill. Include maker and taker charges, rebates, funding, execution PnL and operating costs. If a strategy adds inventory during a move, the resulting capital requirement also affects the comparison.

Read the selected mode’s guide and review the actual wallet authorization before signing. Venue fees, funding and trading risks depend on your account and market.

Report costs on a consistent turnover basis. Closing and reopening repeatedly can change total fees even when the final position is identical. Use cost per million alongside net PnL, open exposure, drawdown and the observation period.

Use comparable markets and periods, and disclose different leverage or exposure limits. Preserve the full sample instead of removing the worst cycles after seeing the result. Historical optimisation can overfit; reserve unseen periods and check whether fill assumptions resemble the live order book.

Write down the stop procedure before starting. A stopped process does not by itself prove that orders were cancelled or positions closed. Read the mode documentation and verify the venue's position and order state independently when ending a run.

Both products can lose money. Neither this page nor a fast-looking interface demonstrates immunity to liquidation, outages, extreme drawdowns or exchange failures. The right choice is the strategy and operating responsibility you can understand and evaluate.