1 Matrix Systems Innovations Ltd, Cardiff CF10
Every WebMatrix release is announced on the public changelog with a release note that names the surface, the change, the calibration window the change passed, and any operator-visible behaviour shift. There is no marketing post for every release; there is a release note. The three releases below are the three we want enterprise customers to read in full.
The MatrixGuard specification language, the deterministic compiler, the 30-day simulator and the runtime that emits an English explanation per block. With fifteen months of production traffic at a Cardiff retailer that moved from regex to specifications and what the rewrite cost and saved.
Released 03 Mar 2026 · MatrixGuard · spec v1.0 · 7 commits · simulator passedHow MatrixObserve takes a P1 — twelve services, four regions, two upstream dependencies — and produces a one-paragraph explanation in the time it took the on-call to pour coffee. With the eval set and rubric, the public monthly eval result, and the two material misses MatrixObserve has had in the last six months.
Released 17 Feb 2026 · MatrixObserve · MTTE 28 → 6 min (median, n = 14)The reinforcement loop that decides per-route, per-hour, per-region TTLs from observed traffic and downstream cost under an operator-declared constraint set. How it is calibrated, why the dashboard is public, and what the loop will not do for you no matter how confidently you ask.
Released 03 Feb 2026 · MatrixEdge · auto-tune v2 · calibration 28dEvery WebMatrix configuration record is now signed against the release tag with a hardware-key-backed ed25519 signature. Promotion of an unsigned record is no longer possible. Migration tooling shipped; deprecation window closes 30 June 2026.
Released 20 Jan 2026 · control plane · deprecation window 12 monthsThe RUM beacon now ships as a signed script tag with subresource integrity. The signed bundle is published on the public artifact registry; the SRI hash is rotated per release. Legacy beacon continues to function for 12 months.
Released 15 Dec 2025 · RUM · SRI · 12-month parallelTwo new PoPs join the EU region for a total of fourteen sites across three regions. Anycast topology revalidated; calibration windows reopened for the EU region for two weeks; auto-tune loop in observe-only mode on new PoPs for the duration.
Released 22 Nov 2025 · MatrixEdge · 14 PoPs · 3 regionsSynthetic check results now join structurally to the trace graph by route and region. The join lets the inference layer cite synthetic evidence in incident paragraphs without a heuristic correlation pass. Monthly eval passed; one regression on long-running checks documented and fixed in 2510.0004.
Released 05 Oct 2025 · MatrixObserve · graph joinThe release cadence is fortnightly, on Tuesdays. Each release ships with a release note (this page), a calibration window record (where applicable), and a public eval result on the first Tuesday of the following month. The release tag is the signature object for every configuration record promoted under it. The deprecation window between adjacent versions is twelve months of parallel availability.
The fortnightly cadence is the maximum rate at which we can run the discipline — author note, simulator, calibration window, public eval — to the standard the customer base expects. We have, in two years of operation, missed two scheduled releases, both for reasons documented at the time. Neither resulted in an unannounced breaking change.