•
4 min read

i26g Custom Development

Table of Contents

What It Is

This service extends an existing i26g deployment when the standard tooling does not cover a specific requirement. Work can sit in the i26g Application, the i26g Control Plane, or their adapters.

The i26g tooling is in early development, so the service is offered to early deployments as they appear, with the scope and terms agreed for each engagement.

What the Work Covers

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

Broker and data adapters β€” connecting the brokers and data sources your operation actually uses, built to pass the same conformance tests as the i26g Broker Adapters and i26g Data Adapters.

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 deployment: environments, promotion rules, and the checks that guard them.

Infrastructure integration β€” fitting the i26g Control Plane to the infrastructure you run it on, including writing an adapter for a provider it does not support yet, built to pass the same conformance tests as the i26g Infrastructure Adapters.

Your deployment remains on infrastructure you control, with source code and the rights granted by the applicable licences. The work includes the source code, documentation, and handover needed for you or another developer to maintain it.

For commissioned work, who holds the copyright and which licence you receive it under are agreed before work begins.

The licence’s obligations. The tooling is licensed under the AGPL. Its obligations apply in specific situations β€” chiefly when a modified version is distributed, or offered to users over a network β€” rather than requiring every change to be published to everyone.

My default delivery policy. Separately from what the licence requires, my default is to publish custom changes under the project’s open-source licence, contributing generally useful changes upstream. That policy is agreed before work begins.

A commercial licence, where needed. If the default does not fit β€” for example, for an integration you need to keep private in a way the AGPL would not allow β€” a separate commercial licence for eligible i26g code is available, with its scope agreed for each engagement. It covers only code I have authority to license on those terms; other code remains subject to its applicable licences. It is available on its own too, without engaging me for the development.

A Good Fit If

You are running an early i26g deployment, it covers the operation but not a specific requirement, and you would rather extend it than wait for a generic feature or switch systems.


πŸ“ž

If you are running i26g and need something it does not cover yet, get in touch β€” early work also shapes where the tooling goes next.