# dgbit

> dgbit is a professional algorithmic trading framework for Bybit. It is a Python package and a multi-service stack (FastAPI REST API, NNG service bus, Vue 3 dashboard) for backtesting, building, and executing crypto trading strategies on Bybit spot markets. MIT licensed.

dgbit is exchange-specific by design: the data fetcher, position model, and built-in strategies are written against the Bybit API directly rather than abstracted across many exchanges. The package is distributed on PyPI as `pip install dgbit` and as a Docker image at `cryptuon/dgbit`. Custom strategies subclass `BaseStrategy` and register with `strategy_registry`.

## Docs

- [Home](https://dgbit.cryptuon.com/): Overview, capabilities, architecture, first backtest, FAQ, and links into every section
- [Features](https://dgbit.cryptuon.com/features/): Backtester, built-in strategies, live execution, NNG service bus, FastAPI + WebSocket API, docker-compose deployment
- [Quickstart](https://dgbit.cryptuon.com/quickstart/): pip install → fetch klines → run a backtest → read metrics → go live on testnet
- [How it works](https://dgbit.cryptuon.com/how-it-works/): The four-layer stack — Vue 3 dashboard, FastAPI REST API, NNG worker bus, and the shared trading core
- [Use cases](https://dgbit.cryptuon.com/use-cases/): Quant developers, automation and agent builders, and researchers building on Bybit
- [FAQ](https://dgbit.cryptuon.com/faq/): Exchange support, library vs service, included strategies, backtests, live trading, deployment, fidelity, and license
- [About](https://dgbit.cryptuon.com/about/): Project philosophy, the case for an exchange-specific framework, design choices, and maintainers
- [Contact](https://dgbit.cryptuon.com/contact/): Get in touch with the dgbit team at Cryptuon

## Blog

- [Blog index](https://dgbit.cryptuon.com/blog/): Engineering notes on backtesting fidelity, strategy authoring, and the service bus
- [Why Bybit-specific matters for backtesting fidelity](https://dgbit.cryptuon.com/blog/why-bybit-specific-matters-for-backtesting-fidelity/): Why binding the data fetcher, fee model, and execution layer to one exchange produces more honest backtest numbers than a multi-exchange abstraction
- [How to wire a custom strategy module in dgbit](https://dgbit.cryptuon.com/blog/wiring-a-custom-strategy-module/): A walk-through of the BaseStrategy / StrategyMetadata / generate_signal / strategy_registry pattern and the notebook-to-live lifecycle
- [Why dgbit uses an NNG service bus, not HTTP between workers](https://dgbit.cryptuon.com/blog/why-an-nng-service-bus/): The architectural choice to use NNG IPC between the API and worker services, the command/event split, and its operational implications

## Compare

- [All comparisons](https://dgbit.cryptuon.com/compare/): Index of head-to-head comparisons against other frameworks
- [dgbit vs Freqtrade](https://dgbit.cryptuon.com/compare/freqtrade/): Breadth vs precision — Freqtrade's multi-exchange CCXT support and hyperopt against dgbit's Bybit-specific data, fees, and execution
- [dgbit vs Hummingbot](https://dgbit.cryptuon.com/compare/hummingbot/): Market making and arbitrage across many venues vs signal-based backtesting and execution on Bybit

## Optional

- [RSS](https://dgbit.cryptuon.com/rss.xml): Blog feed
- [GitHub](https://github.com/cryptuon/dgbit): Source code
- [PyPI](https://pypi.org/project/dgbit/): Python package
- [Documentation](https://docs.cryptuon.com/dgbit): Full reference docs