Overview
Getting started as a developer
Developer Overview
Finterion gives quantitative developers one place to build, validate, research, version, and publish algorithmic trading strategies. You keep your strategy code in your own development workflow while Finterion provides the infrastructure for reproducible validation, backtest analysis, releases, and marketplace distribution.
Get Started
Choose the interface that fits your workflow. The SDK, CLI, and Developer Dashboard work with the same organizations, algorithms, and research data, so you can move between them at any time.
pip install finterion
Features overview
Finterion connects strategy development, research, releases, and deployments in one auditable workflow.
- IAF strategy projects
- Source validation
- Immutable versions
- Backtest bundles
- Performance and risk analysis
- Parameter comparisons
- Named releases
- Presets and parameters
- Organization deployments
- Developer Dashboard, CLI, and Python SDK
- Organization and team access
- Auditable source, research, and release lineage
Code and release management
Manage, validate, and promote strategy code throughout the development lifecycle.
- Get started with your first algorithm and source version
- Validate, version, and promote strategy code through immutable releases
- Configure deployments and track every lifecycle change in Finterion
What you can build
Finterion algorithms are Python projects built with the Investing Algorithm Framework (IAF). An algorithm can define its trading logic, supported markets, configurable parameters, and dependencies. Each validated upload becomes an immutable version, so research results and releases can always be traced back to the exact source that produced them.
Use the Developer Dashboard to:
- Create and organize algorithms within an organization
- Upload source from a folder, ZIP archive, CLI workflow, or connected GitHub repository
- Validate strategy structure, dependencies, and IAF integration
- Run and compare backtests across parameters, markets, and time windows
- Register immutable versions and promote them through releases
- Prepare a validated strategy for marketplace publication
The development workflow
A typical algorithm moves through six stages.
| Stage | What happens |
|---|---|
| Build | Develop an IAF strategy locally and declare its dependencies and configurable parameters. |
| Validate | Check the project entry point, strategy metadata, dependencies, and runtime compatibility. |
| Version | Upload the source and register an immutable version of the validated project. |
| Research | Run backtests and inspect performance, risk, trades, and parameter comparisons. |
| Release | Select a validated version and its artifacts as a release candidate. |
| Publish | Submit the strategy and its verified evidence for review and marketplace distribution. |
This separation keeps source, research, and published releases auditable. A new upload does not silently change an existing release or the backtests attached to it.
Core concepts
Organizations
An organization owns algorithms, versions, backtest bundles, releases, and team access. Choose the organization carefully when creating or uploading resources, especially when you belong to more than one.
Algorithms and versions
An algorithm is the long-lived strategy record in Finterion. A version is an immutable snapshot of validated source code and extracted metadata. Upload a new version whenever the strategy logic, dependencies, or exposed parameters change.
Backtest bundles
A backtest bundle groups one or more .obtf research results for comparison. Bundles can be linked to an algorithm and tagged by experiment, strategy family, or release candidate. Keeping related runs together makes parameter and performance comparisons easier to audit.
Releases
A release connects a specific algorithm version with the artifacts and configuration intended for deployment or publication. Because the source version is immutable, reviewers and investors can trace reported results to a defined implementation.
Before you start
You will need:
- A Finterion account with developer access
- An organization for your algorithms and research
- Python and an IAF strategy project
- Either the Finterion CLI or Python SDK
- Backtest data appropriate for the markets and periods you intend to evaluate
Never commit or upload exchange credentials, API keys, private keys, or .env files with strategy source. Manage runtime credentials through Finterion connections.
Recommended first path
- Create or select an organization in the Developer Dashboard.
- Create an algorithm to hold your source versions and research.
- Install the CLI and authenticate.
- Build an IAF project with an
app.pyentry point. - Upload and validate your strategy code.
- Run representative backtests across multiple market conditions.
- Upload the resulting backtest bundle.
- Review performance and risk before creating a release.
Next steps
- Set up your developer account and create your first organization.
- Learn how to upload and version strategy code.
- Set up backtest uploads from the CLI or from Python.