How i26g's domains map to its repositories: separate repositories for the main site and forge configuration, and a monorepo for the platform, learning material, and documentation.
Badges
Badges come from GitHub once the author claims this feed.
Recent posts
every link opens the author’s post-
Mapping i26g's Domains to Its Repositories
-
i26g Data Adapters
A versioned set of adapters, in early development, through which the i26g Application ingests market data — live and historical — from your data sources, each one tested against the same conformance tests and recorded sample data.
-
i26g Control Plane
Being developed to validate, release, deploy, operate, and retire versions of the i26g Application, and to manage its VMs, networks, and volumes within a boundary the infrastructure owner defines — reconciled from Git, with trading-aware health checks.
-
i26g Infrastructure Adapters
A versioned set of adapters, in early development, through which the i26g Control Plane creates VMs, networks, storage, and DNS on your infrastructure — each one tested against the same conformance tests.
-
i26g Broker Adapters
A versioned set of adapters, in early development, through which the i26g Application places, tracks, and reconciles orders and positions with your broker — each one tested against the same conformance tests, on paper-trading accounts, never on real money.
-
i26g Application
The components that together cover the complete chain required to trade — data ingestion, research and backtesting, strategy runtime, execution, risk, and the human interface — as one self-hosted system you deploy and operate on infrastructure you control.
-
i26g Learning
Helping independent systematic traders understand the choices involved in building and running a trading operation — the alternatives, what each requires, and how to evaluate the trade-offs.
-
i26g Platform
A self-hosted platform for independent systematic trading: the application that covers the trading chain, the control plane that runs it, and the adapters that connect it to your broker, data sources, and infrastructure.
-
The Interface Between i26g and Your Infrastructure
How the i26g Control Plane creates VMs, networks, storage, and DNS inside its boundary: a small, published interface with an adapter per provider, built from OpenTofu modules — rather than a facade service standing between the platform and your infrastructure.
-
One Pattern for Every Integration
Why every external dependency of i26g — infrastructure, brokers, and data sources — goes through the same adapter pattern: a published interface, conformance tests, versioned sets, and versions you pin — with stricter rules where failure costs more.
-
Why i26g Runs on VMs, Not Kubernetes
Why the i26g Platform uses virtual machines as its infrastructure primitive rather than a Kubernetes cluster — from someone who has designed Kubernetes platforms, and chose not to build on one here.
-
Handing the Trading Platform a Boundary
Why the i26g Control Plane does not take its foundation on trust: you give it a bounded environment and boot one VM, and from there it verifies its preconditions and manages everything inside — VMs, networks, and the platform itself — while your infrastructure stays yours.
-
From RST to i26g
Why Retail Systematic Trading became i26g, Independent Systematic Trading: the word that was wrong, the alternatives I weighed, the numeronym, the domains, and what changed with the name.
-
Engineering Manager
Steady leadership for your engineers.
-
My Laptop as Infrastructure Control Plane and Client
Why my laptop owns the infrastructure but not the workloads: it bootstraps the foundation, hands day-to-day operations to a Git-driven Application Control Plane, and connects to remote VMs that keep working when the lid is closed.
-
Code Isolation: Choosing a Development Setup
Comparing isolation and hosting options for development, choosing server-hosted VMs, and defining what each environment can access.
-
Room to Experiment, Confidence to Release
A change-management hypothesis for data and analytics: realistic experimentation in isolated, production-derived environments, validation alongside the latest accepted changes, and a controlled path to production.