nexa-backtest is open source under the MIT license. You can use it freely in production without paying anything. The library is the real product.
These tiers exist for teams that want a direct line, faster fixes, and input on what gets built next.
Everything in the open-source library, plus:
- GitHub Issues for bug reports and feature requests
- GitHub Discussions for questions and community help
- All documentation, notebooks, and examples
- PyPI releases as they ship
This is the right choice for most users. The library is designed to work well without paid support.
For teams running nexa-backtest in production who need reliability guarantees.
- 24-hour response SLA on GitHub issues (business days)
- Private issue channel for your team (GitHub or email)
- Quarterly sync call to review your usage and upcoming needs
- Priority bug fixes - your issues move to the front of the queue
- Direct contact with the maintainer, not a support inbox
For teams that want to shape the roadmap.
- Everything in Priority Support
- Direct input on feature prioritisation - what you need gets built sooner
- Early access to new releases before they hit PyPI
- Review of your integration approach - architecture feedback, best practices
- Access to pre-release exchange adapters and data loaders
For teams building core trading infrastructure on nexa-backtest.
- Everything in Support + Feature Input
- Dedicated Slack or Teams channel with same-day response
- Custom development hours included (adapters, data formats, exchange quirks)
- On-call support during your go-live and migration periods
- Co-development on features specific to your workflows
All tiers are billed monthly. Annual billing is available at a 15% discount. No long-term commitment required - cancel anytime with 30 days notice.
If your organisation needs a formal procurement process, custom SLAs, or something that doesn't fit the tiers above, get in touch. Happy to structure something that works.
Email: tom.medhurst@bradyplc.com GitHub Discussions: https://github.com/phasenexa/nexa-backtest/discussions
If you're using nexa-backtest in production, I'd genuinely like to hear about it - even if you don't need paid support. Understanding what people are building helps me prioritise the right things.