Useful capabilities, with meaningful limitations to understand.
Passivbot is a specialized technical tool, not a managed SaaS bot. Its current code, releases, exchange adapters and optimizer are public, and credentials remain on user infrastructure. Those strengths do not reduce the strategy's substantial averaging, leverage and liquidation risks or substitute for a security audit.
Local credentials and public code are positive; host hardening and audit responsibility remain with the user.
Code, license, releases, configuration and strategy logic are public.
A long public development record supports maturity without proving trading outcomes.
Specialized futures grids, trailing logic, backtesting and optimization are deep but narrow.
Installation, configuration and risk calibration require technical expertise.
The software is free with clear user-borne operating costs.
Repository issues and community channels replace contracted support.
Optimization tooling cannot establish future live profitability.
What this score means It evaluates the product and available evidence. It does not predict returns or eliminate trading risk.
Trust profile
Thirteen disclosed factors create the calculated Trust Score.
The maintainer and contribution history are public.
Factor score: 72/100A corporate registration is not structurally required for this community project.
Factor score: 70/100Maintainers and contributors are attributable through GitHub.
Factor score: 72/100Repository and releases show sustained development.
Factor score: 94/100The Unlicense software is free.
Factor score: 98/100Source is inspectable; no comprehensive independent audit was found.
Factor score: 70/100Local configuration and exchange connectors are documented.
Factor score: 88/100The bot needs trading authority, not withdrawal access; actual scopes remain user-controlled.
Factor score: 86/100Setup, configuration, optimization and release records are public.
Factor score: 86/100No independently assured live-return record exists.
Factor score: 38/100Community support exists without service levels.
Factor score: 62/100No project-wide incident was identified; local compromises may never be centralized.
Factor score: 58/100The project distributes software rather than brokerage or managed investment services.
Factor score: 68/100Red flags & concerns
Context that should inform—not replace—your own assessment.
Recursive grid and trailing strategies on perpetual futures can compound leverage and liquidation risk.
Credential files, processes, network access and dependencies live on the user's host.
What we verified
Checks completed during the latest research cycle.
Passivbot product and safety research
Company, product, permission and regulatory evidence reviewed separately.
Is Passivbot legit?
Long repository history, named maintainership, current releases and inspectable code establish the project. A conventional corporate operator is not applicable.
The maintainer-led project has a traceable technical history but no conventional SaaS operator, corporate support agreement or service-level commitment.
Operator and legal sources: Passivbot license (Primary)
Is Passivbot safe?
Local control limits shared-provider credential exposure, but users must secure files, hosts and updates. Recursive averaging in perpetual markets can magnify loss and liquidation risk.
How Passivbot works
Users install dependencies, configure exchange keys and strategy bounds, run historical optimization or backtests, and operate the local live-trading process.
Trading bots and automation features
Version 8 combines Python configuration with Rust execution components, recursive grid and trailing behavior, backtesting and multi-objective optimization for perpetual futures.
Supported exchanges
Binance, Bybit, Bitget, OKX, Gate.io, KuCoin, Hyperliquid
Pricing
Pricing last checked on 2026-08-20. Check the provider's current pricing before purchase.
There is no license fee. Users pay for compute, data where applicable, trading fees and perpetual funding.
Pricing source: no dedicated source in the current evidence set; see the full source list and stated limitations below.
Custody model
Funds remain at exchanges; the runtime and credentials remain on user-controlled infrastructure.
Security
Passivbot's public code and local credential boundary improve inspectability, but users remain responsible for secure files, dependencies, host access and exchange permissions.
Use a dedicated account, no-withdrawal keys, strict file permissions, process isolation and conservative leverage. Recheck connector changes at each release.
API and withdrawal permissions
Users place exchange credentials in a local configuration file and control host access and key scopes. Withdrawal status: Not required; use trading permissions without withdrawals.
Security and permission sources: Passivbot repository (Primary) · Passivbot releases (Primary) · Passivbot optimization documentation (Primary)
Regulatory information
Passivbot distributes software; derivatives eligibility and automated-trading obligations depend on the user and venue.
Regulatory and service-scope sources: Passivbot license (Primary)
Performance evidence
Optimization tooling cannot establish future live profitability.
Claim verification
Source, claim type, evidence, status and analyst note are shown separately.
“Minimal intervention market making”
- Company source
- Open original claim
- Checked
- August 20, 2026
- What we found
- The software automates entries and exits, but position limits, exchange changes and adverse trends still require monitoring.
- Analyst conclusion
- Automation is verified; low-maintenance outcomes are not.
“Supports seven perpetual-futures venues”
- Company source
- Open original claim
- Checked
- August 20, 2026
- What we found
- Current repository documentation lists Binance, Bybit, Bitget, OKX, Gate.io, KuCoin and Hyperliquid.
- Analyst conclusion
- Connector capabilities can differ by venue.
Security incident history
Documented events and bounded public-source checks, with entity scope preserved.
Public incident-record check
No qualifying product-wide credential or asset-loss incident was identified in the reviewed primary records.
- Provider response / research note
- This is not proof that no user-level incident occurred; users should still monitor releases, credentials and provider notices.
Strengths & limitations
Strengths
Current public source and permissive license
Local credentials
Deep futures optimization
Long development history
Limitations
–High technical burden
–Specialized derivatives scope
–Averaging and liquidation risk
–No independent return assurance
Who may find it useful
Experienced quantitative futures users
Operators comfortable with Python, Rust and servers
Users who can bound leverage and exposure
Who should look elsewhere
–You need a managed cloud interface
–You are new to perpetual futures
–You cannot monitor self-hosted software
Passivbot alternatives and comparisons
Alternatives are selected for overlapping workflows, with the main distinction shown.
Frequently asked questions
Is Passivbot a cloud service?+
No. It is self-hosted software whose runtime and credentials remain on the user's infrastructure.
What markets does Passivbot target?+
Its current documentation focuses on perpetual futures and recursive grid or trailing position management.
Is Passivbot safe because it is open source?+
No. Public code improves inspectability but does not replace secure operation, risk limits or an audit.
Sources & evidence
Company-provided information is labeled and not treated as independent validation. Research coverage: 8/9; evidence confidence: High.
- [01]Primary · DocumentationPassivbot repository
enarjord and contributors · Accessed August 20, 2026 · Last checked 2026-08-20
- [02]Primary · DocumentationPassivbot releases
enarjord and contributors · Accessed August 20, 2026 · Last checked 2026-08-20
- [03]Primary · DocumentationPassivbot optimization documentation
Passivbot project · Accessed August 20, 2026 · Last checked 2026-08-20
- [04]Primary · TermsPassivbot license
Passivbot project · Accessed August 20, 2026 · Last checked 2026-08-20
Research changelog
Conclusions may change when new evidence appears.
Reviewed current status, architecture, security, pricing, operator evidence, documentation and material claims.
Passivbot: 72/100
Passivbot is a specialized technical tool, not a managed SaaS bot. Its current code, releases, exchange adapters and optimizer are public, and credentials remain on user infrastructure. Those strengths do not reduce the strategy's substantial averaging, leverage and liquidation risks or substitute for a security audit.
Research disclaimer This review is informational and not financial, investment, legal or security advice. Scores evaluate disclosed product qualities and evidence—not profitability, solvency or safety. Features, prices and eligibility can change.
No active affiliate relationships or compensated outbound links are configured. Any future commercial relationship will be disclosed and will not affect scores or conclusions. Read our policy.