Open source

All of it is public

The whole platform — strategies, risk gates, paper execution, backtests, the API, the dashboard, this site and the deployment — lives in one public repository under the MIT licence. Nothing on this site describes a closed component.

What is in the repository

One repository, one licence. The directories that matter, and why each is worth reading.

github.com/Arjuunb/nexus-trading-botMIT
  • automation-hub/

    The platform itself: strategies, the pre-trade risk gates, paper execution, the backtest harness with its cost model, the /v1 API, webhooks, the audit log and the key vault.

    A risk system you cannot inspect is one you take on faith. Every rule that can block a trade, and every cost a backtest charges, is in this directory with the tests that pin it down.

  • sdks/

    The Python, TypeScript, Go and Rust clients, each with its own tests.

    Client libraries live in your codebase, so they should be readable, forkable and patchable without waiting for anyone.

  • automation-hub-dashboard/ · tradexa-landing/

    The operator dashboard and this website.

    What the site says the platform does can be checked against the code that does it, in the same commit.

  • nginx/ · scripts/ · compose.yaml

    The deployment: reverse proxy, TLS, containers, backups and the deploy script.

    Self-hosting is a real option, not a sales conversation.

What is not in it

Your credentials and data

Exchange keys, API keys, the vault master key, databases and backups live on the server that runs the platform, never in the repository. The code that encrypts them is public; the secrets are not.

Published packages

The SDKs are not on PyPI, npm or crates.io yet. Until they are, install them from the repository as the SDK page shows.

Contributing

Small and specific beats large and speculative. A failing test that reproduces a bug is the most useful thing you can send.

get set up
git clone https://github.com/Arjuunb/nexus-trading-bot
cd nexus-trading-bot
python -m pip install -e ".[dev]" -r automation-hub/requirements.txt
(cd automation-hub && python -m pytest -q)   # the platform's test suite

Licence

Contributions are made under the repository's MIT licence. There is no CLA.

Review

The maintainer reviews every pull request, in public, and CI runs every test suite on every push.

Rules

CONTRIBUTING.md in the repository has the setup, the checks, and the changes that are not accepted — live order routing among them.

Where the code lives and what a good issue looks like is covered on the GitHub page. Security issues are the exception to all of this — never open a public issue for one; the disclosure route is on the security page.