i26g Custom Development

For Traders Already Running the Tooling

This is not a general development service — it is for someone who has already deployed the i26g tooling, is running it, has hit a specific edge it was not built to cover, and does not want to or cannot build it themselves. If that is not where you are yet, start with the tooling itself; most operations do not need this.

Where you have, the edge is the part nobody else can build for you generically. Custom development is hands-on work on your deployment, at whichever layer the need sits:

• the i26g Platform, for the strategies, integrations, and operational pieces your specific operation needs;
• the i26g Control Plane, for how your platform is released, operated, and changed, on the infrastructure you run it on.

What the Work Covers

Strategy implementation — turning a rule set you have already reasoned about into tested, executable code on the platform, with the backtest and risk bounds around it.

Broker and data integrations — connecting the venues and data sources your operation actually uses, rather than the ones a commercial platform decided to support.

Operational pieces — the monitoring, alerting, and reporting that let you see what the system is doing without sitting in front of it.

Life cycle and operations — adapting the i26g Control Plane to how you release, operate, and change your platform: environments, promotion rules, and the checks that guard them.

Deployment — fitting the i26g Control Plane to the infrastructure you run it on: your own hardware and virtualization, or your cloud resources and the services around them.

Extension where the foundation stops — building the parts the tooling does not cover yet, composed into it rather than bolted alongside.

Ownership and the License

The tooling is self-hosted and yours outright, and that does not change because I worked on it. The deployment stays on your infrastructure, the code stays legible, and nothing here introduces a dependency on me continuing to be involved. If you outgrow the foundation, it is designed to be replaced piece by piece.

The tooling’s source is licensed under the AGPL, which means changes to it are expected to be published — upstreamed into the tooling itself if they are generically useful, or released under the same license if they are not. That is the default, not a courtesy. If you need to keep specific custom work proprietary — an integration or strategy piece you do not want published — that is available as a separate commercial license exempting that work from the AGPL’s publication requirement, priced accordingly. The exemption license is available on its own, too — if you build the change yourself, you do not need to engage me for the development to get it.

A Good Fit If

You are already running the i26g tooling, it covers the operation but not the specific edge you are trying to capture, and you would rather extend what you own than wait for a generic feature or switch systems entirely.