Why It Exists
Some independent traders want to operate systematically: rules they can test, execution they can trust, and an operation they can keep improving. The i26g Handbook describes that discipline; the i26g Application is what makes it runnable.
Independent systematic traders often face a choice between accepting a platform’s constraints and assembling their own stack. Existing tools can cover much of the workflow, but integrating them into an operation the trader can inspect, control, and extend takes substantial work — time that would otherwise go into developing strategies. The i26g Application is meant to be that integrated foundation, so the work goes into the edge rather than the system around it.
What It Contains
The application is not one program but a set of components designed to cover the complete chain required to trade. They are in development and not yet public:
| Component | Responsibility |
|---|---|
| Data | Ingesting, storing, and correcting market and reference data, with its freshness known |
| Research and backtesting | Exploring ideas and testing strategies against stored data, using the same strategy logic and risk rules intended for live trading |
| Strategy runtime | Running strategies during a session, on current data, under the trader’s rules |
| Execution | Turning strategy decisions into orders, and tracking them to fills |
| Risk | Enforcing the trader’s limits before and after orders, and stopping trading when they are breached |
| Human interface | Seeing what the operation is doing, and intervening when needed |
The design is deliberately scoped: a single trader running a focused set of strategies, not a multi-user platform or a fund-grade system.
How It Is Built
The application builds on established open-source tools, with file-first persistence and no infrastructure the workload does not yet justify. What i26g develops is the composition: how the components fit together, and the behaviour at the joints between them, where integration failures can disrupt trading.
Development is guided by a real trading operation. Practical use determines priorities; testing and validation determine whether changes are ready to run. The specifics — each component and the decisions behind it — are documented in the writings as the build progresses.
How It Fits
- The i26g Control Plane takes the application through its life cycle — releasing, operating, and changing it — on infrastructure you control, on premises or in the cloud.
- The i26g Broker Adapters and i26g Data Adapters connect it to your broker and your data sources, following the same model as the i26g Infrastructure Adapters: a published interface, conformance tests every adapter must pass, and versions you pin.
- i26g Custom Development extends it with the strategies, integrations, and operational pieces a specific trading operation needs.
This application is being built in the open. If you want to trade systematically on a system you control — and want to follow along or contribute to the direction — follow via RSS as the build progresses, or get in touch directly.