Cryptohopper Marketplace review
Marketplace plus automation, not one strategy
Public-source review updated 7 October 2026. We did not buy these plans, enter private rooms or audit subscriber accounts. Product descriptions are source-supported; the decision tests below are our analysis. The performance snapshot retained in the publisher profile was not refreshed to this source-check date.
The seller is the unit of review
The public marketplace lists free and paid signal sellers with exchange filters. Cryptohopper supplies the common software environment; a specific seller supplies the trading decisions. Compare a named listing, its current version, trading pair and intended exchange rather than transferring the platform's reputation to every strategy. A change of seller is a new experiment, not an extension of the previous track record.
Resolve the two-layer subscription
Before payment, separate the bot plan from any seller subscription. Save each renewal term and establish which settings the seller controls versus which settings your bot applies. In a hypothetical test, a buy alert arrives while the bot has already reached your position cap: a rejected entry belongs in the usability log, not in a rewritten seller win rate. Likewise, a sell alert and a locally configured stop can produce different exits.
Evidence still missing for an individual listing
Platform statistics can help locate candidates, but this desk review has not reconciled a seller's full message sequence to broker or exchange orders. Request the exact outcome convention, fees, cancellations and open positions. The marketplace's own disclaimer distinguishes community-generated material from platform advice and warns that displayed profits do not predict future results. Treat a leaderboard as a discovery aid, not completed due diligence.
Who should shortlist it
This route fits a reader who deliberately wants an exchange-connected workflow and can test one seller at a time. It is a poor match for someone seeking one universally audited Cryptohopper return. Establish a reversible paper or tightly controlled test, keep the configuration frozen and compare submitted, accepted and filled orders separately.
Primary sources
Compare spot, perpetual and bot workflows · All provider reviews
Compare one seller and one bot configuration
A useful marketplace review follows a named seller rather than the platform-wide list. Preserve listing identity, version, stated exchange and product, subscription period and the configuration that receives its events. A change of seller or risk setting creates a new comparison. The platform provides the environment, but that does not make every seller's rules, cadence or displayed history equivalent. A free listing also does not settle any separate bot-plan entitlement.
For an invented acceptance case, seller A sends three original buy events while the fictional receiving bot allows one open position. The first is accepted, the second is blocked by that declared cap, and the third refers to an unresolved instrument. The classroom usability record keeps all three and their meanings. One accepted request does not establish a fill, and the other two do not become realised losses. Do not call the receiver's result the seller's universally achievable win rate.
Inspect exits and settings that compete
An original seller exit, local bot stop, trailing configuration and manually initiated operation can conflict or describe different owners. Record which policy was active when a message arrived. Do not retrospectively choose whichever exit creates the attractive chart outcome. If the product documents particular precedence or settings, preserve the actual current reference; if unavailable, request clarification instead of inventing it from a demo screenshot.
The invented bot has a locally defined exit at one classroom condition while the seller later publishes another. The completed review preserves both intentions and leaves the account outcome unresolved without operation records. It can still reveal that the buyer needs to understand policy ownership. A successful software response does not authenticate the seller's full archive, and a marketplace ranking cannot resolve which exit policy a subscriber actually used.
Make the shortlist conditional on a concrete job
Investigate this category when you deliberately want to compare external sellers within a configurable execution environment. It is a weaker fit when you need one independently reconciled platform-wide result, cannot maintain exchange permissions, or cannot explain why the selected seller and bot settings match. The no-purchase alternative is to retain a paper observation packet first. Paper records can help expose mapping and configuration gaps without establishing live liquidity.
The review's completed decision packet asks for seller identity, exact product, receiving configuration, separate commitments and original event/operation links. The official marketplace supports discovery and describes its community-data limits. We have not bought the listing, inspected every private signal or connected an account. Treat those fields as remaining work before a stronger outcome claim; do not turn the quantity of listings into evidence that one selected seller has a durable edge.
Related research
Retained source references
References retain the original source trail; a link is not evidence that every private claim or account record was independently audited.