Inferrex

/ insights

Featured thesis

Research

Essay · June 2026

The State Cannot See Itself

British government doesn’t have a technology problem — it has a comprehension problem, paid by the taxpayer department by department.

Aaron Gammon

Read the Manifesto

/ insights · newsletter

Get the next essay by email.

One note when a new Insights piece is published. No product drip, no sales sequence.

/ the rest of the argument

All essays

The same four fields before and after comprehension, each gaining a canonical concept, a confidence, a provenance and a version
Architecture

Essay · June 2026

Comprehension over connection.

The integration industry spent twenty years getting better at connecting systems. Connection scales linearly with effort and breaks on contact with change; comprehension compounds.

Aaron GammonRead
Six systems needing fifteen hand-built pairwise connectors, against the same six comprehended once
Research

Essay · June 2026

The N×N Problem

The connector catalogue is the integration industry’s proudest number and its quiet death sentence. Connections wanted grow as the square of the systems.

Aaron GammonRead
The corpus drawn as a map: the Inferrex platform at the centre, comprehended providers radiating outward
Research

Essay · June 2026

What's Actually Inside an API Schema Corpus

“We have a big corpus” is easy to say and easy to fake. What’s in it, how deep each entry goes, and why a corpus of fully-read schemas is hard to copy.

Aaron GammonRead
Many provider schemas collapsing into one canonical model, then back out as typed semantic concepts
Architecture

Essay · June 2026

What a Lingua Franca for Business Data Actually Means

A lingua franca isn’t a translator sitting between two systems. It’s a shared language that sits above all of them.

Aaron GammonRead
Point. Infer. Flow. — from an API URL to governed, flowing data with no configuration step
Architecture

Essay · June 2026

Inferring API Structure

The interesting capability isn’t connecting a known API — it’s reading an unknown one, and turning raw structure into business meaning.

Aaron GammonRead
Same rulebox, different cars: one shared specification, many implementations
Architecture

Essay · June 2026

Why Everyone Can Be Different

Most integration platforms quietly demand conformity. The model that survives reality adapts to difference instead of trying to abolish it.

Aaron GammonRead
Self-healing as an immune system: detect, understand, adapt
Architecture

Essay · June 2026

What Self-Healing Integration Actually Means

The phrase is about to be everywhere, attached to retries with a nicer dashboard. Here is the bar it should have to clear.

Aaron GammonRead
The inference pipeline: schema discovery through opportunity detection
AI & understanding

Essay · June 2026

Why We Built Our Own AI Layer

The easy path is to wire in a frontier model API and ship. Three dependencies you inherit the moment you do, and one wall you never get past.

Aaron GammonRead
The proprietary training stack — layers built, datasets in training, adapters promoted
AI & understanding

Essay · June 2026

Building a Self-Sovereign AI Training Loop

A closed improvement loop — fed only by your own corpus and human corrections, never by a frontier model.

Aaron GammonRead
Provider signals feeding a structural fingerprint that flags a meaningful change ahead of a downstream failure
Industry

Essay · June 2026

The Hidden Cost of Brittle Integrations

Everyone knows integrations break. Almost nobody adds up the bill — interrupted engineers, silent bad data, and roadmap time that evaporates.

Aaron GammonRead
One canonical layer above every provider dialect — bridging without replacing
Industry

Comparison · June 2026

Inferrex vs Traditional iPaaS

The honest comparison, capability for capability — including where the incumbents are genuinely stronger.

Aaron GammonRead
Every provider understood once benefits every customer afterwards
Industry

Essay · June 2026

Embedded Integration Infrastructure

Stripe didn’t sell payments to merchants one at a time. Integration is overdue the same move.

Aaron GammonRead
Cloud, Enterprise, Sovereign, Air-gapped — what leaves each environment
Industry

Essay · June 2026

Sovereign Integration Infrastructure

Where the integration layer runs is no longer an IT detail. It is a question about sovereignty and what you actually control.

Aaron GammonRead
The compliance pipeline: read the field, match the rules, flag the obligation, cite and log it
Industry

Framework · June 2026

Data Sovereignty for Regulated Industries

A practical framework: what it actually means, the five questions a regulated buyer must answer, and where the integration layer quietly creates the risk.

Aaron GammonRead
What crosses the deployment boundary, and what never does
Industry

Essay · June 2026

Air-Gapped Doesn't Mean Crippled

If you own your models and run them locally, air-gapping changes nothing — the capability survives the isolation.

Aaron GammonRead
Isolated credentials, TLS in transit, per-customer keys at rest, and an audit log of every access
Industry

Essay · June 2026

From AI SaaS to Critical National Infrastructure

A certain kind of software is crossing a line — from an application you can swap out to infrastructure a country depends on.

Aaron GammonRead
One declared manifest fanning out into services, schemas, routes, SDKs and deployment config
Founder & company

Essay · June 2026

How One Person Built Production-Grade Infrastructure

A salesperson by trade, who didn’t finish school, built a seventeen-service production-grade integration platform solo.

Aaron GammonRead

/ what we argue

Six standing positions.

The essays above are the working; these are the conclusions they keep arriving at.

Comprehension

What it means for software to understand a system rather than connect to one. Where inference works, where it does not, and how confidence should be published rather than hidden.

Infrastructure

Why comprehension is a layer beneath categories rather than a product inside one. What it means to build a business on infrastructure you did not build.

Intelligence

What an organisation can know about its own estate, what it currently cannot, and why the gap has persisted.

AI

Why grounded technology context beats a larger context window. What an agent needs before it can be trusted to act on an estate.

Sovereignty

Data residency, local inference and the difference between a deployment option and an architectural property. Why air-gapped operation constrains design rather than configuration.

Economics

Why pairwise integration scales linearly with effort and canonical comprehension compounds. What that does to the cost of coverage, and who currently captures the difference.

/ deeper material

The founder's account, and the longer argument.

Why this was built, and the philosophical case behind it, sit in Founder and the Manifesto rather than in the essays above. The same argument, posted on the networks we actually use, lives on Social.

The argument is only worth making if it survives contact.

Point Inferrex at a system you already run and judge the claim against something you know.