Skip to main content

dxcore

dxcore is the backbone for data processing, networking and core structures for dx libraries.

Mainly a toolkit for pulling market data, tracking portfolios, serving networks/meshes of strategies, and talking between services.

Main Idea

For now, the more interesting modules are:

  • Market data: let's you fetch historical bars and live account updates from external interfaces, such as Interactive Brokers (TWS/Gateway), and get results back. We plan to keep expanding this to other brokers and data sources in the future.
  • Portfolios & accounts: keep track of instruments, positions, and account metrics in one place.
  • Strategies: run simple strategy logic (like SMA crossovers) and factor models over your data. Also let you define your strategy code in other languages (such as OCaml and Python), and then run in a performant env backbone. For full strategy development and reusable strategy code, look at cadlag.
  • Services: register and talk between services with a small request/response layer for now only a built-in HTTP server). This is where the service discovery pieces that used to live in dxforge ended up.
  • Python bindings: the same core functionality is exposed to Python via the dxcore-pyo3 crate

and more in the future!

Getting Started

This is a Rust workspace with two crates: crates/core is the Rust code for the library itself, while crates/pybindings are the Python bindings

Build everything with:

cargo build

Some functionality is behind feature flags (ibkr for Interactive Brokers, strategies for the strategy module). Enable them if you need them:

cargo build --features ibkr,strategies

Examples

A few runnable examples live in crates/core/examples:

cargo run --example strategy --features strategies

In the Ecosystem

dxcore works alongside the other Divergex components: dxforge handles orchestration and containerized deployments, while [cadlag](https://github.com/divergex/cadlag] has the actual code for strategies.

License

This project is licensed under the MIT License. See the LICENSE file for details.

Metadata

Release files for dxcore 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dxcore 0.1.1
File Size Uploaded
dxcore-0.1.1.tar.gz 76.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dxcore 0.1.1
File Interpreter ABI Platform
dxcore-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.9 abi3 Linux glibc 2.17+ x86-64 Details

Total release size: 7.9 MB

Release files / dxcore-0.1.1.tar.gz

Download URL dxcore-0.1.1.tar.gz
Size 76.1 kB
Tags Source
SHA-256 checksum
How to use checksums
0b34cf613b2206032a42fb0a4b884f9e446d7069ce7116908b3c8f8a43c72eeb
BLAKE2b-256 checksum
How to use checksums
9d3927d5932b0f529374abcf87dcc9a384766859e6a57454ab4fc4bc3eb2d35a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.

Transparency log

Release files / dxcore-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL dxcore-0.1.1-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 7.8 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
a4dc960c1f6c9a21defd311636c57067f00a59f0e5a6d387d6c0a1e89cebbcc7
BLAKE2b-256 checksum
How to use checksums
12cdf17421d3f7e497521ce3e4586a9e04f32da1a1a042ef324b2bbdaf11422f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page