The company behind the matrix.
1 Companies House 15598218 · Cardiff CF10 · United Kingdom
Abstract
WebMatrix Systems is operated by Matrix Systems Innovations Ltd, a private company registered in England and Wales (15598218), incorporated 27 March 2024 in Cardiff. The team is small by design — the platform is large; the people who run it do not need to be. We describe the founding premise, the structure of the company, and the deliberately direct conditions under which we operate.
Why a web-infrastructure firm out of Cardiff, registered in March 2024.
For most of the last decade, web infrastructure has been a market with a clear taxonomy and a steadily diminishing set of new entrants. The big CDN vendors are old. The big WAF vendors are older. The big observability vendors are public companies whose roadmaps are set by quarterly bookings, not by what an SRE actually needs at 03:14 on a Saturday. We did not start this firm because the existing vendors are bad; many of them are good at what they do. We started it because what they each do, individually, no longer maps to what the operator's job actually is.
The WebMatrix premise is that the value is in the integration. MatrixEdge knows the route. MatrixObserve has the trace. MatrixGuard sees the request. When the three live in one control plane and one data model, an SRE at 03:14 sees one paragraph — not four dashboards. That paragraph is the product; everything else is engineering scaffolding underneath it.
The company was incorporated in Cardiff on the 27th of March 2024. The first edge PoP went live three months later. The first enterprise customer signed in late 2024. We are deliberately small — the engineering team is fewer than fifteen people — and we are deliberately direct: there is no sales team, no SDR layer, no qualification call before the technical conversation.
Three directors. One engineering team.
The company has three directors of record at Companies House. Each carries operational responsibility for a portion of the platform — the data model and the control plane, the edge and observability stacks, and the policy runtime and security posture respectively. The split is not by job title; it is by where the engineering work actually lands.
The engineering team is fewer than fifteen people, organised flat. There is no head of engineering whose job is to coordinate the people who do engineering. The team that ships a release is the team that holds the pager for that release for at least four weeks afterwards; this is policy, not convention.
| Function | Headcount | What they own |
|---|---|---|
| Engineering · edge | 4 – 5 | PoPs, routing, TLS, auto-tune loop |
| Engineering · observability | 3 – 4 | Graph, inference, monthly eval |
| Engineering · policy | 3 | Spec language, compiler, simulator, runtime |
| Engineering · control plane | 2 | Data model, API, deprecation discipline |
| Operations and customer engineering | 2 | Pager, customer briefings, post-mortems |
Table 1 Functional breakdown at Q1 2026. Numbers add to < 15. The company has no marketing function and no sales function.
Small, specialised, and on-call.
The deliberately small structure is the part of the company that the trade press finds least interesting and that the customers find most important. The engineer who briefs you on MatrixEdge is the engineer who maintains MatrixEdge. The engineer who answers your post-mortem question on MatrixObserve was on the pager for the incident in question. There is no enablement layer between the customer and the work.
The trade-off is that we cannot serve every enterprise. We currently operate against fewer than forty enterprise customers; we have a long-standing position that until we double engineering — which we have no immediate intention to do — we will not double the customer book. The customers we have signed have, at our request, agreed to that constraint in writing. They are the better for it; so are we.
What we will not do
- We will not sell our customers' traffic data, aggregated or otherwise.
- We will not run a multi-tenant model that lets one customer's noisy neighbour degrade another's edge performance. Isolation is at the kernel.
- We will not publish customer logos without explicit, written, recently re-confirmed permission.
- We will not ship features that overlap with what an existing partner vendor does well.
- We will not double the customer book without doubling engineering.
Engineering call or correspondence?
If you need to see WebMatrix in front of your origin, request an engineering call. If you need to write to the company about something else — press, partnership, regulatory query, supplier diligence — write directly; the inbox is monitored and the registered office is real. Companies House →